So I just learned that I can’t use the Object Migration tool to migrate record data between two TRIRIGA environments. For example, I have two environments on different servers on the same application and platform version. If I try to use OM to migrate the Record Data only, for instance, the Building Equipment records, not all of the associated records will get migrated and certain smart sections do not get properly migrated either.
What are some other options that I could use to quickly migrate this data? I was thinking the Data Integrator (DI) method, but that would be tedious because I have over 100,000 records.
Ideally, DI should be used for the initial load. If the data is available somewhere else, you can look into Integration Object or DataConnect. You can populate staging tables and then run the integration. In your workflow, you can have logic to create any dependent records (such as organizations or contacts) based on the staging table data.
[Admin: To see other related posts, use the Integration tag or DataConnect tag.]
I added new fields to a BO, and went to Object Migration to package the BO for export. I noticed that when I search for the changes to that BO, it sometimes list the module as a possible selection. Do I need to include the module as a selected object in the OM package? I usually ignore the module from the OM package, but wondering I’m if there will be a problem down the road by doing so.
If the module was imported previously to the target environment, then no, you do not need to import it again when you bring in the changes from the BO.
[Admin: To see other related posts, use the Object Migration tag.]
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.]
I recently set up a new environment in which I need to migrate the classifications (not just the record data) from the existing system. What is the fastest way to do this and ensure that the classifications are set up properly in the new system?
I migrated the BOs and forms. I checked the Include association for the BO to itself and with the classification BO. The form has been added to the “Includes/Forms” tab of itself as well as the classification form. But I still don’t see this BO added under the classification hierarchy when I click on “New” to create the root record.
[Admin: This post is related to the 03.29.17 post about creating a classification. To see other related posts, use the Classifications tag or Object Migration tag.]
We are working on a DB2-to-Oracle migration for TRIRIGA 3.5.2/10.5.2 by using SQL*Loader. The TRI_REORG_ANALYSIS table recently caught our eye. This table exists in DB2, but does not exist in Oracle. But today, after we generated a new DB2 backup, this table is no longer there.
My question is: Is this a temporary table used for calculation or cache purposes?
Can you change operating systems? That is, start with Linux and migrate to Windows. Currently, we’re on TRIRIGA 3.3.1 and upgrading to the latest platform, and in the process, we would like to move to Windows Server. A related but hypothetical question: Can you run TRIRIGA with the app server on Linux and the process server on Windows?
TRIRIGA is OS agnostic. You can run a Linux app server and Windows database server, and vice versa. You could even throw AIX in the mix and have that run the process server, or any mix there of. In the lab, we have OS X MacBook Pros with a mixture of Windows and Linux VMs. Personally, I think Linux+Intel is a more stable server platform that has far fewer up-time issues versus Wintel (Windows+Intel). These days, most shops are migrating from Windows to Linux.
Is it possible to migrate documents from one TRIRIGA environment to another?
Yes, documents can be migrated from one environment to another, but I would recommend that you focus on “system” documents like BIRT reports, or Excel sheets used for offline processes. I would not use object migration (OM) to migrate documents in large quantities…
[Admin: This post is related to the 12.02.16 post about integrating with CMIS or ECM solutions, the 06.09.16 post about using an ECM solution instead of Document Manager, and the 04.13.16 post about uploading 6500 locations with several attachments each.]
We are in a process of implementing Capital Projects and were wondering if we can get some timelines from any of your previous data migration experiences. We have a system setup based on the Performance Best Practices document, advanced infrastructure, with a total of 4 GB JVM. So, approximately how long will it take for me to migrate the following into TRIRIGA?
- (a) 3000 Capital Projects with 200+ cost codes per project, multiple bids per project, change orders.
- (b) 500 Projects with 200+ cost codes per project, multiple bids per project, change orders.
I understand it’s difficult to gauge, but we’d like just a ballpark timeline. Any number or timelines will be of great help.
Planning for a new installation or migration of an existing IBM TRIRIGA installation can be a complicated endeavor, because there are so many different possible configurations for the IBM TRIRIGA n-tier architecture. Here are some links that will help you with your planning:
This is a lot of information to go through, but taking the time to review this information during your planning phase of your installation or migration will allow you to make informed decisions based on your intended use of the IBM TRIRIGA product, and to plan accordingly.
[Admin: The same article is also posted in the Watson IoT Support blog.]
Steps to replicate:
- 1. Create a new security group. I set Read, Update, Create, and Delete on the triBudget module only. Everything else was left as Inherit, etc.
- 2. Assign this security group to a test user.
- 3. Login as test user, and security will be fine.
- 4. Export OM for security group.
- 5. Import OM security group back into environment.
- 6. Login as test user, and queries, etc., will be broken.
A record of a completely different type has the same name as “Organizations” and “Geographies”. A patch helper, workflow, and query will be made available to rename the as-delivered records that have the same name. The query will help to find security groups that have the Geo or Org set to the incorrect record type.
[Admin: A similar article is posted in the Application Platform forum about an issue with security groups and object migration.]