About Me

About Me
Working with SOA technologies , implementing solution using IBM BPM , IBM Integration Designer,IBM WODM and IBM DataPower

About me

View Mahesh Dondeti's profile on LinkedIn

upcoming posts on IBM Bluemix,Devops,Worklight,Node js.

Saturday, 13 October 2012

Publishing failed when connecting from WID to remote WPS server

In case you wanted to publish your applications directly from WebSphere Integration Developer to the remote WebSphere Process Server you might have come across the situation where you are able to add a remote server in your WID environment but when you try publishing your projects to the server, you receive the following error: “Failure uploading archive to server”.



It is a simple issue but it can take a lot of time to solve it if you don’t know where to look and I must say that the above message isn’t the most informative one I’ve ever seen. However, I have discovered that this happens if your server is not a member of domain at the time of installation and WID is unable to recognize the hostname, written in the configuration file. To change this hostname, carry out the following procedure on the server-hosting machine:
1.       Open serverindex.xml file in text editor. You will find this file in folder <WAS_HOME>\profiles\<PROFILE_NAME>\config\cells\<CELL_NAME>\nodes\<NODE_NAME>\serverindex.xml
2.       ServerIndex element has an attribute called hostName, which might have an invalid value (requires a valid domain name or IP address). In our case we correct this value from
<serverindex:ServerIndex xmi:version=”2.0″ xmlns:xmi=”http://www.omg.org/XMI” xmlns:serverindex=”http://www.ibm.com/websphere/appserver/schemas/5.0/serverindex.xmi” xmi:id=”ServerIndex_1″ hostName=”orange“>
to
<serverindex:ServerIndex xmi:version=”2.0″ xmlns:xmi=”http://www.omg.org/XMI” xmlns:serverindex=”http://www.ibm.com/websphere/appserver/schemas/5.0/serverindex.xmi” xmi:id=”ServerIndex_1″ hostName=”orange.cloud.si“>
3.       Restart the server.
4.       Try publishing your project to the server once again, this time it should work!