To submit job streams from your mobile, even if you do not have any experience with Tivoli Workload Scheduler.
Launch the Self-Service Catalog from your mobile device by connecting to the following URL:
where host_name and port_number are the host name and port number of the Dynamic Workload Console you are connecting to.
Self-service Catalog is a solution to automate routine business tasks and run them from mobile devices without having to install and learn about the whole Tivoli Workload Scheduler product. By using the Self-service Catalog you can use your mobile device to submit service requests to Tivoli Workload Scheduler without knowing anything about engines,jobs, or job streams.
By launching Self-service Catalog application from your device, for example, you can see the available services, which basically are Tivoli Workload Scheduler job streams. You can open a catalog, view the services that it contains, and submit a service request very simply and easily from your mobile device.
Even though the Self-service Catalog has been primarily envisioned to be used from mobile device, you can efficiently use it also from your computer connected to a web browser. To submit a job stream from your mobile, an administrator must have previously created a service by associating it to a Tivoli Workload Scheduler job stream and engine. The service is linked to a job stream that runs on a Tivoli Workload Scheduler engine. By simply launching the service, you can submit the job stream. You define jobs and job streams using the Dynamic Workload Console to automate tasks that users perform routinely. You use the Self-service Catalog interface from your mobile device to start the job streams when needed.
Optionally, you can also use Self-service Catalog taking advantage of High Availability configuration so as to have multiple console instances working at the same time without reducing performance. If the Self-service Catalog you are using is connected to a Dynamic Workload Console in High Availability configuration, all the user settings, including the Self-service Catalog data, are stored in a DB2 repository. If you are connected to a Dynamic Workload Console in High Availability configuration using a load balancer, when you launch the Self-service Catalog, you are not connecting to a specific Dynamic Workload Console, but to a node in the High Availability configuration. Therefore, for example, if a node fails, new user sessions are directed to other active nodes in the configuration and this change is completely transparent to users.