HCL Workload Automation, Version 9.4

Accessing the services

Access the web services by invoking a proxy.

About this task

The web services are accessed by invoking a proxy which contains the path that your application will use to access the web services wsdl files at the following location:
Distributed (not z/OS®) environment
http(s)://<localhost>:port_number/PlanServicesWeb/services/<service_name>
z/OS environment
http(s)://<localhost>:port_number/zPlanServicesWeb/services/<service_name>
where:
localhost
The hostname of the master domain manager
port_number
The port numbers for http or https are defined in your WebSphere Application Server installation in:
HCL Workload Automation
<WAS_profile_path>/config/cells/ TWSNodeCell/nodes/TWSNode/servers/
server1/server.xml
where the default value of <WAS_profile_path> is <TWA_home>/WAS/TWSprofile
Dynamic Workload Console
<JazzSM_profile_dir>/config/cells/JazzSMNode01Cell/nodes/
JazzSMNode01/servers/server1/ 
where, the default value of < JazzSM_profile_dir> is:
On Windows operating systems
C:\Program Files\HCL\JazzSM\profile
On UNIX operating systems
/opt/HCL/JazzSM/profile
under:
  • WC_defaulthost for http
  • WC_defaulthost_secure for https
service_name
The name of the service you invoke: SchedulingFactory, JobService, or JobStreamService.
An example of accessing the web services in the z/OS environment is as follows:
SchedulingFactoryProxy proxy = new SchedulingFactoryProxy("http://111.222.333.444:
                               31126/zPlanServicesWeb/services/SchedulingFactory");

String[] jstreams = proxy.submitJobStreamWithVarSub(
                    ENGINE_NAME, 
                    JOB_STREAM_KEY, 
                    schedTime, 
                    deadlineTime, 
                    null, 
                    null, 
                    null, 
                    null, 
                    null, 
                    null, 
                    null, 
                    variablesToBeSubstituted);