The SSH tunnel command needed changing however to use IP address instead of the host name, for example: ssh -f [email protected] 1414:vm123.developer.ihost.com:1414 -N to: ssh -f [email protected] -L 1414:1.14 -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. 🙂 In my current engagement, a question sometimes comes up regarding data in the mashup database (e.g., of the catalog that Business Space for Web Sphere uses).
There is a nice spreadsheet that explains in detail the database schema used, which is titled “Lotus Mashup Schema Data Dictionary (Basis: v2.0.0) and is located dbscripts/Business Space/lotus_mashup_db_in the Web Sphere Process Dynamic Edition installation media.
I had a requirement for Web Sphere Portal 6.1.5 on Web Sphere Process Server 7 (a common scenario) and so I tried this on 64-bit Ubuntu 9.10. The following should help for a quick non-supervisor development environment with no need to perform platform tweaking.
Usr src updating
Problem When a Human Task is brought up, for example, in the Task Information widget, a 404 error will show – that the form could not be found.
The problem here is that the web projects are deployed as part of their enterprise applications on the Process Server, rather than on the Portal. Get the WAR files Bring up Web Sphere Integration Developer (or a JEE-based tooling), switch to the “Web” perspective, and the web projects should appear in the “Enterprise Explorer” list – usually their names end with “web”.
In the “Deployment Descriptor” of the enterprise application, switch to the “Module” tab from “Overview”, under “Modules” list, select the web module that we’ve exported, and on the right, there is the “Context root” field, which we would want to take note of. and, with the common standalone Portal deployment, don’t forget to change from server1 to Web Sphere_Portal in the “Map modules to servers” step of the WAR installation process. confirm that the server isn’t ND (Network Deployment) as this is not supported for remote uses from the RAD/WID; (reference: 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 \– 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 in my case was “pear”, so I added “1.89 pear” (1.89 is the IP address of the server) to the hosts file.
(reference: https://com/developerworks/forums/thread.jspa? message ID=13926131) April 3, 2010 in IBM Web Sphere Application Server, IBM Web Sphere Process Server | Tags: Cloud, Deployment, firewalls, IBM Web Sphere MQ, Remote, SSH, tunnelling, Web Sphere Application Server | Leave a comment 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.
The complaint went and Web Sphere Integration Developer was updated with 124 MB worth of downloads to 188.8.131.52. Any views here are my own and don’t necessarily represent IBM’s positions, strategies or opinions.