You are currently browsing the tag archive for the ‘Remote’ tag.
Working with a WebSphere Application Server-based solution that is deployed remotely on a Linux platform, such as in the cloud, with the Rational Application Developer-based tooling, is a popular requirement. In my case, the remote server was the WebSphere Dynamic Process Edition (WebSphere Process Server with a set of products including WebSphere Business Monitor) on RHEL, and WebSphere Integration Developer (WID).
It worked bearing in mind the following points:
1. if the remote server is shown as “Stopped” even though it is started, and the remote server is on a Linux platform, apply RAD/WID patch included in PMR 59591,L6Q,000 (as of 7.0.1.1 this patch is still needed), substitute the jar of same name with PMR’s attached jar, and rename this jar to be the same as the substituted one;
2. confirm that the server isn’t ND (Network Deployment) as this is not supported for remote uses from the RAD/WID;
(reference: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14253319)
3. deployment will fail if host name returned from remote server is not recognised by RAD/WID machine, look at what host name is used by the server by checking <WAS_HOME>\profiles\<PROFILENAME>\config\cells\<CELLNAME>\nodes\<NODENAME>\serverindex.xm – and adding the host name to hosts file on RAD/WID machine with the IP address of the server, for example – the host name in serverindex.xml in my case was “pear”, so I added “123.45.67.89 pear” (123.45.67.89 is the IP address of the server) to the hosts file.
(reference: https://www.ibm.com/developerworks/forums/thread.jspa?messageID=13926131�)
I had a set of applications deployed on a Process Server however they would not start as a remote server – a MQ server – was behind a firewall and was inaccessible. This firewall allowed the SSH port (23) however, so, naturally, I employed SSH tunnelling.
I used a technique to avoid having to modify the applications to use localhost as the hostname in order to direct traffic to go via SSH tunnel instead of directly to the firewalled MQ server. In /etc/hosts, I added “vm123.developer.ihost.com” (the MQ server) to the “127.0.0.1″ line. This would trick the applications into using 127.0.0.1 for the MQ server. The SSH tunnel command needed changing however to use IP address instead of the host name, for example:
ssh -f bjfletcher@vm123.developer.ihost.com -L 1414:vm123.developer.ihost.com:1414 -N
to:
ssh -f bjfletcher@123.45.67.89 -L 1414:123.45.67.89:1414 -N
This was to use the actual MQ server through the IP address for the SSH tunnel whereas the applications would use the SSH tunnel itself through the host name. Nice and easy huh? 
