TWS Integration Workbench V8.6. - How to customize your automation environment by creating a custom Job Type plug-in
Tivoli Workload Scheduler version 8.6 introduced the new Job Type plug-in.
The main feature of this type of job is that everyone can create a new job type that suits various business needs, from the integration with an advanced reporting suite to a file copy. This is possible through the integration of Java and IBM Tivoli Workload Scheduler Integration Workbench V8.6. This, combined with the multiple capacities of scheduling of Tivoli Workload Scheduler, allows end users to extend, integrate and maximize their automation environments. Available tasks for automation include not only advanced software suites but also user's daily tasks.
In the document below we will describe how to create a Job Type Plug-in that meets your automation needs.
PamDenny 270000BXV7 Tags:  analysis qbr ad report utilization upgrade data bilog hoc ibmpa custom 9,393 Views
How many custom reports do you have? Do you have 25, 50 – or is your number in the range of 100 to 250 custom reports? Or are you in the category where you don’t know how many custom reports you have because your users are creating their own uncontrolled reports in tools like Microsoft Access or Microsoft Excel?
The topic of custom reports leads to a myriad of questions including –
- Is each custom report utilized?
- What determines if a custom report is approved, and then developed?
- Should super users be given database and report development access?
- What mechanisms are in place to insure that correct data is being returned in the custom reports?
- How much do custom reports cost -- in terms of design, development, test, administration, maintenance dollars and resources?
As John Heywood told us back in the 16th century that ‘Rome was not built in one day’. … my thoughts in the 21st century are that we can’t answer all those questions in today’s BiLog. However, we can start a plan to give you ideas on how you can reduce your number of custom reports.
One of the first and directly actionable means to reduce your custom reports is to begin using V7’s Ad Hoc Reporting feature, QBR. By using QBR within any V7 application, you and/or your users can quickly create reports that can include complex where clauses, filters, sorting, grouping, and parameters.
QBR functionality enables key features including -
· - Enabling users to quickly create their own reports for their unique business needs
· - Does not require technical, development skills, like Java, or database knowledge to create the report
· - Does not consume development hours in creating and maintaining large numbers of unique reports, which may only be used by a very small number of users
The cornerstone of QBR functionality are Report Object Structures, ROS. ROS enable users to select fields from multiple categories (objects) for their ad hoc reports. ROS are designed to enable users to quickly visualize their hierarchies and parent/child relationships. They are created in the Object Structure application of V7, and in the next BiLog, we’ll discuss their key attributes and how to extend them.
LeandroCassa 270002840B Tags:  things application tiny add select custom action menu adding little useful 5 Comments 27,820 Views
Welcome to Useful Tiny Little Things, a series of topics that I will publish in the Process Automation blog. My name is Leandro Cassa and I work at IBM as the CCMDB Level 3 support team leader. The purpose of this series is to provide useful simple things that we sometimes have no idea exist. These tips apply to CCMDB, Tivoli Asset Management for IT, Service Request Manager, and other products based on Tivoli's process automation engine.
This week I'll explain how to create your own entry on a select action menu and apply an action to it.
Ok, ready to go. Open your TPAE based system, click on Go To > System Configuration > Platform Configuration > Application Designer (you must have permissions to do the next actions).
As usual lets use the Work Order Tracking application as a sample. Search for WOTRACK and enter the Work Order Tracking.
At this point a editable version of the application shows up, but we want to click on the Select Action and select Add/Modify Signature Options.
Next step is to click on new row, and edit the as follows (don't forget to expand the Advanced Signature Options; there are changes there as well):
Of course you can use another name and description for your Signature Option. Signature options specify privileges for using applications, menu options, and toolbar items.
Notice that the Advanced Signature Options has "This is an action that must be invoked by user in the UI" which is essential for this tip to work, so don't forget selecting the right option here.
Once again, click on Select Action, but this time select Add/Modify Select Action Menu. It is time to create your entry on the Application (on this example Work Order Tracking) Select Action menu.
Notice that I'm using the Element Type OPTION. This means it is an option on the Select Action menu.
Also the Key Value is CALLACTION. The Key Value field relates to the signature option ID that is associated with this menu item, which we just created.
I used the Position 1 and Subposition 1 to put our Select Action option as the first entry. But feel free to play around with this; the position and subposition are responsible for the order and subitem definition. If you want the menu item to appear under a header menu, enter a numerical value in the Subposition field, to indicate its position within the header menu.
Last but not least, in the Tabs field define where you want your entry to be available (to be visible), and MAIN in this scenario is the right one.
Very good! We are all done with the Application Designer. Now the most interesting piece of this post: The action!
Move to Go To > System Configuration > Platform Configuration > Actions. Create a new Action.
Name your new Action CALLACTION (otherwise TPAE won't be able to find it when you select the item on the Select Action), also choose the WORKORDER Object in this scenario because we did changes for the Work Order Track application, if yours differ select the appropriate Object.
In my case I'm selecting the Type as Application Action, which means I'm going to call an existing action from the Work Order Application, but there are other options you can use. Refer to the Infocenter for more on that right here. Since I chose Application Action, the Values are restricted to the application actions. I selected CREATECHANGE, which means every time I click on the Select Action created, a new related Change record is created.
The screenshot here shows what I selected to sample this feature, but you can select whatever is useful for you.
All set, now save the action and restart the MXServer (restart only the MAXIMO application works fine as well) to apply the changes.
As soon as your MXServer is back, Go To > Work Orders > Work Order Tracking, click on new.
Save the record.
Now click on the Select Action, confirm you have your new entry there and click on Call Custom Action.
And check the Related Records tab (Depending on the action you set, you might need to save the record again to refresh the MBO and see the changes made).
And here it is:
That's it for this week. Hope this helps.