What is the “Integration” check box for in the workflow Start task?
Assuming you are referring to the Start task of an asynchronous workflow, when this property is selected, the workflow is used to migrate data from staging tables in IBM TRIRIGA records. This type of workflow is used extensively in IBM TRIRIGA DataConnect.
Check out this IBM Knowledge Center topic about DataConnect that describes the “Integration” check box: Workflow task settings.
[Admin: The same question is also posted in the main Application Platform forum. To see other related posts, use the Staging tag or DataConnect tag.]
You can configure TRIRIGA to use Tivoli Directory Integrator as its ETL runtime engine to run ETLJobItems from within TRIRIGA.
Before you begin
Install Tivoli Directory Integrator, if not already installed, on all the TRIRIGA systems that could run a TDI ETL Job Item. During the TDI install:
- Make note of the installation directory you enter on the Destination panel. You will enter this value later in TRIRIGAWEB.properties.
- Select either installation type. TRIRIGA requires only the TDI Server component.
- When prompted for the location of the Solution Directory, you can select any option. TRIRIGA specifies its own solution directory at runtime. However selecting the option “Use Install Directory” may simplify troubleshooting.
- Make note of the value you enter in the Server Port field on the Server Port Values Panel. You will enter this value later in TRIRIGAWEB.properties.
- Clear the “Start the Configuration Editor” check box on the Install Complete panel.
- Note: This step is very important for TDI/TRIRIGA integration to work. After you have installed Tivoli Directory Integrator, update it with the recommended fix packs (per TRIRIGA support matrix). TDI must be at least at FP04 (188.8.131.52) or it will not automatically start the TririgiaETLDispatch.xml assembly line which will result in ETL job items failing to run successfully.
- Edit TRIRIGAWEB.properties file to enable TRIRIGA to manage TDI server. Set the following properties…
- Install a JDBC driver library so that Tivoli Directory Integrator can use it to access TRIRIGA database…
- Edit TDI global.properties file to allow TRIRIGA to check and stop the TDI server from localhost without requiring authentication and authorization certificates. Set the api.remote.ssl.on property to false to tell TDI to trust requests from localhost…
- Start Tivoli Directory Integrator Agent from TRIRIGA Admin Console and verify that it starts successfully…
[Admin: This post is related to the 08.03.16 post about installing, upgrading, or uninstalling TRIRIGA TDI, and the 05.01.16 post about documentation on developing TDI with TRIRIGA. To see other related posts, use the TDI tag.]
What is the best way to implement a mobile app that will record the time spent in maintenance? Is the OSLC integration the best way to do this connection?
[Admin: To see other related posts, use the Mobile tag or OSLC tag.]
Conference: November 29, 2017, 8AM (ET) to November 30, 2017, 4PM (ET)
Crystal City Gateway Marriott
1700 Jefferson Davis Hwy
Arlington, VA 22202
TRIRIGA Mobility Solution (MobilD)
Do you need to improve your work efficiency for your TRIRIGA users but fear mobility has a steep learning curve? Are you looking for an out-of-the-box TRIRIGA mobility solution with simple role-based buttons and menus? Then you are not alone. Kiel Schmitz, a former St. Paul Information Systems leader, shares a customer’s perspective on selecting and implementing the ValuD MobilD solution.
- Challenges and objectives for a TRIRIGA Mobility project
- Targeted roles and tasks including service requests and inspections
- Project results and benefits
- Lessons learned
Join the ValuD Session
Join the session to learn more about how MobilD delivers a role-based user experience on any device with mobile access such as phones or tablets whether connected or offline. Requester, technician, or supervisor users only see information that is directly relevant to their role and their work process, which drives timely service requests, quicker assignments, higher user adoption, and better data collection. The MobilD solution was tailored to St. Paul’s TRIRIGA customizations, within a short time-frame, extending TRIRIGA on Mobile.
[Admin: To see other related posts, use the ValuD tag or MobilD tag.]
Watson Analytics is an intuitive, cloud-based analytics tool that will help TRIRIGA users explore their data for insights and display findings as dashboards and infographics for easy sharing. All without having to become a data scientist.
Watson Analytics guides data discovery and predictive analytics by using automatic visualizations and enables dashboard creation so that you can get insights and make informed decisions. Pairing Watson Analytics with data from TRIRIGA enables you to explore your integrated workplace management processes and obtain new insights on your day to day operations. The IBM Watson Analytics service will allow you to discover patterns and meanings in your data.
The TRIRIGA Connector for Watson Analytics gives you the ability to export your TRIRIGA data into Watson Analytics. With Watson Analytics, you can tune data, discover insights to help solve your business problems, and display your findings…
[Admin: To see other related posts, use the Watson tag or Analytics tag.]
Sometimes when using TRIRIGA CAD Integrator “Smart Attach”, some of the spaces are not being uploaded. There were 3D shapes around some spaces. There were values greater than 0 on z= dimension.
TRIRIGA does not support 3D polylines. You may have shapes with a value greater than zero on the z= dimension. You can find these using the AutoCAD PLIST command. To resolve this issue, it is necessary to use the AutoCAD “Flatten” command to force all polylines to be 2-dimensional. Other things to check: (1) The polylines are closed, (2) The shape and labels are on the layer you are selecting during the Smart Attach process, (3) The label is within the polyline boundary.
[Admin: To see other related posts, use the Smart Attach tag.]
I would like to see an example of running an ETL job item, because simply running the process fails. When users see the activated record, they assume they can click “Run Process” and get results. But you need to enter a set of restraining data to get results.
Every ETL job item is different. You must fill in the record information to get the results necessary for the transformation or processing. More information can be found at the following link: IBM TRIRIGA – Running ETL transforms. This blog entry will describe a sample run of a Survey Fact ETL job item.
- First, from the menu, click on Tools > Job Scheduling > ETL Job Item.
- Then search for “Survey Fact” and open the record. It’s recommended that you click on More > Copy to create a copy that you can modify, test, and play with.
- After that, change the name to an friendly name and enter at least these mandatory fields: Date, Start Date, Fiscal Period, and End Date.
- For the Date field, take notice of the “Quarter” and “Month” to enter the other subsequent Start Date, Fiscal Period, and End Date.
- See the example for “Q2/2017 – June”. After all of the fields are entered, click Save. Then you can click Run Process.
- The record window will close. Then you can see “Processing” for the status of the record.
- After that, you can open it again and it should show “Completed” as the status. You can also click on the Workflow Instance tab to see the completed workflows.
[Admin: To see other related posts, use the ETL tag.]