PI18898: JOBLAUNCHMANAGER TOOL THROWS "COULD NOT CONNECT TO SERVICE" ERROR WHEN USING WEBSPHERE

APAR status

• Closed as program error.

Error description

• When trying to run the JobLaunchManager tool, it throws "could
  not connect to service" error, even though all property files
  are configured correctly. Looking at the log file, the tool
  tries to connect to localhost:7009, no matter what is specified
  in all the property files.
  
  The Administration Guide mentions that if host and port options
  are not supplied, they will be retrieved from the appropriate
  properties file.
  
  Prerequisites:
  
  Baseline Openpages 7.0 installation on Websphere
  
  Steps to Reproduce:
  
  1. Open a cmd prompt on the app server
  2. Change directory to /openpages/bin
  3. Run the command:
  
  Joblaunchmanager ?ConfigurationFile JobLaunchConfigFile.txt
  -Username OpenPagesAdministrator -Password
  OpenPagesAdministrator
  
  Expected Results:
  
  The JobLaunchManager tool should connect to the correct server
  based on the property file settings.
  
  Actual Results:
  The JobLaunchManager tool always attempts to connect to
  localhost:7009 if no host/port is specified, rather than
  determining the host/port from property files
  
  Error Message:
  
  An exception occurred:  OP-00004: Could not connect to service
  [R5Z7XL93HY7M]
  

Local fix

• When running the JobLaunchManager tool, specify the host and
  port as an option.
  Eg. joblaunchmanager.sh -Username OpenPagesAdministrator
  -Password OpenPagesAdministrator -Host testserver -Port 10108
  

Problem summary

• ***************************************************************
  * USERS AFFECTED: OpenPages Administrator
  ***************************************************************
  * PROBLEM DESCRIPTION: JobLaunchManager connection issues
  ***************************************************************
  * RECOMMENDATION: Customers should download OpenPages 7.1
  * from Passport Advantage. See the following document for
  * details on obtaining 7.1.
  * http://www.ibm.com/support/docview.wss?uid=swg24039170
  ***************************************************************
  

Problem conclusion

• Code change
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• 999
  

Fix information

• Fixed component name

  OPENPAGES ORM

• Fixed component ID

  5725D51OR

Applicable component levels

• R710 PSY

     UP