27
WPS server move
Posted by | Posted in Websphere Process Server / Integration Developer | Posted on 27-01-2009
Tagged Under : WebSphere, WebSphere Process Server, WPS
WPS server move
We are moving our WebSphere Process Server instance from one machine to another. The biggest challenge in this WPS server move or migration is to keep the existing business processes and human tasks. Our current WPS instance has a lot of long running processes and completed tasks.
I feel the above scenario is very common and can happen to almost every company that has WPS running. However when I checked, there is no IBM supported solution to move a WPS instance from one server to another (At least in Infocenter). Starting from WPS 6.2 they have added support to WPS server moves, but versions prior to 6.2 there is no support. (I don’t know what IBM was thinking about their product? Do they think that only short running processes should be installed in a WPS machine? Or once installed you cannot change the server forever?)
Anyways we have found a workaround to keep the existing processes and tasks even after migrating to the new server. Our strategy is very simple. We have installed the new server and deployed all our applications. Now the new WPS server will have all our applications running except the old processes and human tasks. Now we took a dump of our old database and imported into the new server. It worked! All our old processes and tasks were there in the new instance too. If somebody is planning to follow the same approach remember to install all the old applications before importing the database. Else all your tasks and processes will be marked as invalid and deleted. Anyways we haven’t tried this approach in our production instance yet.
We have opened a PMR with IBM to see whether there is some IBM supported solutions for server move before actually implementing our work around in production server.
If some one else has a better approach for WPS server move than mine, please let me know.
Update: We got an update from IBM and they do not support the server move. Their solution was to migrate to 6.2 first and then move the server.
Hi,
Can you please explain the database backup. Which DB (BPEDB…) you are backing up and how you are importing into the new WPS server?
Hi,
Can you please explain how you are taking the backup & import it into the new server?
Also please tell us which DB you are exporting & importing (BPEDB…).
Thanks
Sivaraman
Also I am wondering how do you manage the following issues.
In the assembly diagram, when you are creating an export of a component with the webservice binding, the webservice URL gets automatically created. Now when you open the webservice from the module, you will be able to change the endpoints. But whenyou change the same and deploy it, you wont be able to get the “Hi ! this is a webservice” message in your browser for that URL.
Can you suggest me how do you change the endpoints URI to make it more meaningful?
Also there is a situation where I have the deploy the code into different servers from the WID. But the port numbers change across the servers.
Now once I create a build/EAR export of the project for one server, I have to manually change the port numbers of all the webservices and then create the build/ear file for deoplying to the other server.
Is there a better way of doing it?
You help & guidance is very much appreciated.
Thanks,
Sivaraman
1. We have imported BPEDB for this purpose. Database import is actually done by our DBA. So I am not sure about the steps involved in that.
2. You cannot change the end point url just by editing the biding information in properties window. You need to change your export name by refactoring it. However the end point url will be in a pre defined format. ie, it will be like http://servername:port/contextname/sca/export name. Still if you want a better name you may need to change the context name to more meaningful.
3. I will make a post on how to add a dynamic end point soon.
A new post explaining how to change the endpoint url for a web service import from admin console is available at
http://www.albeesonline.com/blog/2009/03/04/dynamically-assign-web-service-endpoint-urls/
Can you share more of what you got from IBM saying the move is not supported? Is there a link on the WebSphere Support site that indicates this? I am in a similar situation, where I am begin asked to install with the WPRCSDB on one DB2 server. And then, after deploy, I am to switch WPRCSDB to a different instance on a different server.
The IBM response was in the form of an email. They have not given us any link or any other material stating its not possible.
Btw, The latest update from IBM :- Its possible
. An architect from IBM Germany has suggested a solution to make it working. I have not received the details of how to make it happen. I will share you the details.
Hello Albin, I installed WPS 6.2 on windows (2003 server). The BPEDB was placed on Apache Derby DB (i think this is the default setting during installation). I now want to move it to DB2 due to serious implications when the assembly is under load.
Any idea on how to generate scripts for DB2 installation?
Regards,
Ashwin
What you need is to migrate Apache Derby to DB2. I think the following link will help you in that migration. http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.datatools.derbymigration.doc/topics/tmigrate_database.html
Worked like a charm! Thank you very much.
Hi Albin
to migrate Apache Derby to DB2 i gone through the link but i am not able to find migrate database wizard in any perspective .please help me in finding that
I have not worked with DB2 Developer workbench. So I do not know which perspective this wizard is. Ashwin said that its working for him. Let me see if he can help.
I used WID not DB2 Developer workbench for migrating the database. Read thru page 5 of the PDF provided in the URL below. It has details about navigating to the WID “database explorer” view and in particular, how to connect to a Derby database.
http://www.ibm.com/developerworks/forums/servlet/JiveServlet/download/820-204851-14082706-321856/How_to_see_WPS_data_in_a_Derby_DB.pdf
Note: You can connect to Derby without specifying the username and password.
Once done, create a new connection to the database you want to migrate to.
Then, right click on Derby database and select the migrate option.
Hi Ashwin
when i right click on derby database i am not abel to find migrate option
Which version of WID are you using and what options are you able to see?
I’m not even sure how you’re supposed to do it in 6.2. Anybody got any idea?
thx
Please follow the below link you will get some idea.
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/index.jsp?topic=/com.ibm.websphere.wps.620.doc/doc/tmig_vtv_remote.html
Hi Ashwin
when i right click on derby database i am not able to find a migrate option. Using WID 6.2.