Blogs

About this blog

Welcome to the Process Automation Blog, where you can read the perspectives from BSM experts. This Blog provides insights into the Process Automation solution, as well as technical details about specific IBM products.

Links

Recent tweets

Do you have in your workload environment
standard procedure to apply for managing some jobs and/or jobstreams?

Would you like to have a button from Tivoli Dynamic Workload Console to automatically associate that documented procedure to the job/jobstream
instance?

If your answer is yes, you are reading the
correct Tivoli Dynamic Workload Console TIP.

With Tivoli Dynamic Workload Console 8.5.1 FP1, it was introduced a
so called "Global Settings" that allows you to quickly associate an
URL to a Job, or a Jobstream. Let's see how we can leverage this feature to
associate documents to a Job.

Step
1: Understanding Global Settings

Tivoli Dynamic Workload Console Global Settings are a set of global
overridable properties allowing the TDWC administrator to change the behavior
of the console. Properties contained into an XML file, called
TdwcGlobalSettings.xml. Into these file settings have the form:

will reduce to 500 the value for the
property "planViewMaxJobstreams" for the users logged ad operators (note that is allowed only one "settings" tag per role).

The TdwcGlobalSettings.xml it is not
present on the installed files of the TDWC. Let’s see how we can enable and use
it into the dynamic console.

Step
2: Enable the TdwcGlobalSettings.xml

You can find a template in the TDWC image
(into the DVD or electronic image), under the "utils" folder. To
enable the overriding of the global setting, you will need to copy this file on
the installed files. So copy the template file into the directory:

If
you have TDWC 8.6: <TWA_HOME>/eWas/profiles/TIPProfile/registry

If
you have TDWC 8.5.1:<TWA_HOME>/eWas/profiles/twaprofile/registry

Now edit the file, and replace the entire
content with this one:

<?xml version="1.0"?>

<tdwc>

<settings>

<twsObjectDoc>

<property

name="jobUrlTemplate"

value="http://localhost/docs/jobs/${job_name_w}" />

</twsObjectDoc>

</settings>

</tdwc>

We have almost done. Now, if you login
(eventually logout if you are already logged in) into the Tivoli Dynamic Workload Console you can already
see that there is a new action in the job actions menu called “Open
documentation”. If you click on it, you will see that a new browser window will
open with almost the same link that we have provided in the configuration file
(.. “http://localhost/docs/jobs/” ) with except that the job name
was replaced at the last part of the URL.

Now, if you already have URLs to associate
for jobs, you will need only to customize the URL to launch, and consider some
other variables that you can use into the template e.g.

job_wkst_w: Workstation

job_jsname_w: Job stream name

job_number_w: Job number (only for z/OS environment)

There are several other variables that can
be used for this template, for a full list you can see the product
documentation, on the section “Dynamic Workload Console global settings”,
accessing it directly on your product instance. You can also customize the
label that appears on the console action menu. For doing that, you will need to
add another custom setting:

<property
name="customActionLabel" value="Custom Action" />

So your TdwcGlobalSettings.xml file will
look like:

<?xml version="1.0"?>

<tdwc>

<settings>

<twsObjectDoc>

<property

name="jobUrlTemplate"

value="http://localhost/docs/jobs/${job_name_w}" />

<property name="customActionLabel" value="Custom Action" />

</twsObjectDoc>

</settings>

</tdwc>

Now, if you now what you can do with a URL
it’s ok. If you have a web server, you can use it as your documents repository
(in this case, you may also use this feature to make a different action, not
necessary open a document). But what if you have only a set of files?
Consider that you cannot use local file (file:// beginning URL) for using this feature,
so it is not feasible to share a directory between all users of the console.

If you don’t have the URL, but only a set of
file to associate, stay tuned and leave a comment. We will introduce a way for sharing your
documents directly via the TDWC web server on a future post.