Tuesday, 13 August 2013

Doh - Problem with Process Designer NOT connecting to Process Center

More fun with IBM BPM Standard 7.5.1.1.

This time, Process Designer was failing to connect to my Process Center.

PD is on one machine ( Windows ) and PC is on another ( Linux ).

This is what I see: -



This happened regardless of whether I used HTTP: -

-Dcom.ibm.bpm.processcenter.url=http://rhel6.uk.ibm.com:9082

or HTTPS in eclipse.ini: -

-Dcom.ibm.bpm.processcenter.url=https://rhel6.uk.ibm.com:9445

Having faffed around for a while, I dug back through an internal IBM BPM forum ( hosted, of course, on IBM Connections ) and found: -

<snip>
I found the culprit.  The client had used "localhost" for the Linux host name.  Once I changed it to something reasonable, created a new profile for the PC, it worked first time.
</snip>

When I checked 99Local.xml : -

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/localhostCell01/nodes/localhostNode01/servers/ProcessCenter.AppTarget.localhostNode01.0/process-center/config/system/99Local.xml

guess what I found ???

Yep, you guessed it: -

        <images-prefix>http://localhost:9082/teamworks</images-prefix>
        <portal-prefix>http://localhost:9082/portal</portal-prefix>                
        <repository-prefix>http://localhost:9082/ProcessCenter</repository-prefix>
        <servlet-prefix>http://localhost:9082/teamworks</servlet-prefix>
        <webapi-prefix>http://localhost:9082/webapi</webapi-prefix>
        <process-help-wiki-url-view>http://localhost:9082/processhelp/en/%TITLE%?teamworksTitle=%TEAMWORKS_TITLE%</process-help-wiki-url-view>
        <process-help-wiki-url-edit>http://localhost:9082/processhelp/en/Special:Edit?topic=%TITLE%&amp;teamworksTitle=%TEAMWORKS_TITLE%</process-help-wiki-url-edit>
        <portal-prefix>http://localhost:9082/portal</portal-prefix>
        <process-admin-prefix>http://localhost:9082/ProcessAdmin</process-admin-prefix>
        <teamworks-webapp-prefix>http://localhost:9082/teamworks</teamworks-webapp-prefix>
            <base-url>http://localhost:9082/teamworks/webservices</base-url>
            <default-namespace-uri>http://localhost:9082/schema/</default-namespace-uri>
        <coach-designer-xsl-url>http://localhost:9082/teamworks/coachdesigner/transform/CoachDesigner.xsl</coach-designer-xsl-url>
                <client-link>http://localhost:9082/teamworks</client-link>
        <repository-server-url>http://localhost:9082/ProcessCenter</repository-server-url>


Can you say "Doh!" ???

Now I need to override those settings in 100Custom.xml, resync my WAS cell, restart Process Center ( the AppTarget cluster, specifically ) and I should be good to go.

By the way, the reason that this is an issue ?

Process Designer uses HTTP/HTTPS to get to the bootstrap port of the AppTarget cluster member, gets the required info from BPM ( via 99Local / 100Custom ) and then connects via JMS to the Messaging Engine cluster.

Watch this space ….

No comments: