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 (184.108.40.206) 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.]
When I run the CAD Integrator (CI) 12.1.1 installer, I get the window: “No supported version of AutoCAD or MicroStation were found on your computer.” On the next screen, I am able to manually select AutoCAD 2013 and 2014, and the install completes normally. The CI menu does not appear in the menu bar, so I have to manually add it by using the menu load process and navigating to the TrgaAcad_en.cuix file. However, it doesn’t stay loaded and I have to reload it every time I open AutoCAD 2014.
Also, once loaded, none of the functions in the IBM TRIRIGA CI work. For example, I keep getting: “Unknown command “TRGA_PREFERENCES”. I tried to use the APPLOAD process to try and load, but I don’t know the name of the CAD Integrator ARX file. Regardless, the install doesn’t appear to work properly. I tried to uninstall and reinstall 4-5 times, rebooted, re-downloaded the install file, etc. The menu won’t stay loaded, and I need the name of the ARX file to try the APPLOAD.
Here are a few notes:
- Loading the menu does not load the plugin. If the plugin loads properly, then it will automatically load the menu if not loaded already.
- Since the plugin is not actually loaded, none of the commands will work, hence the unknown command.
- There is no ARX file. It’s a .NET assembly that requires netloading of the correct DLL.
- Question: Are you using a 32-bit JVM instead of 64-bit? This is a known issue. We have an installer check for this now, but I am not sure it’s in 220.127.116.11: Troubleshooting CAD Integrator V.12 – Resolving No CAD Types Found on installation
- Make sure you know that 18.104.22.168 does not support Java 8. That might be an issue.
- If that’s not the problem, it might be some sort of security issue where the installer does not have permission to read or write to the registry in order to install CI. You can try installing with Admin privileges. We also have a wiki about it: Troubleshooting – AutoCAD – Unknown command after CI Install
- The “No supported version…” message is there, so the installer cannot install anything. The fact that you can select AutoCAD just means it will deploy the necessary files, but will not actually install it. Refer to: Manually Loading CI using Netload
[Admin: This post is related to the 09.04.16 post about adding the menu in the menu bar. To see other related posts, use the Integrator tag.]
There may also be an issue where the menu does not load, unless you use the CUILOAD command directly to load the TrgaAcad_en.cuix directly from the install directory. Then, attempting to login results in a _TRGA_LOGIN Unknown command “TRGA_LOGIN” message. The cause of this issue is that the CAD Integrator/Publisher (CI) is not initializing correctly…
Assuming NETLOAD works, the main issue is that probably the CI installer does not have permission to update the registry. CI actually uses the JVM and the command line to update the registry, so on certain secure systems, it may not be allowed to update the registry as needed to tell AutoCAD to load CAD Integrator…
The main issue is a permission issue where the CI installer cannot update the Windows registry to enable automatic loading, which is outside the control of the CI installer. If the CI installer cannot update the registry, then see the workaround…
[Admin: To see other related posts, use the Integrator tag or AutoCAD tag.]
How do you run the MS SQL “SetVarcharColsToNumeric_MSSS.sql” and “SetVarcharColsToNumeric_MSSS_Publish_BO.sql” scripts after upgrading to TRIRIGA 22.214.171.124? According to the TRIRIGA 10.5.2 and 3.5.2 release notes:
- “There are two scripts for MS SQL, SetVarcharColsToNumeric_MSSS.sql and SetVarcharColsToNumeric_MSSS_Publish_BO.sql. Run SetVarcharColsToNumeric_MSSS.sql first. When it completes, run SetVarcharColsToNumeric_MSSS_Publish_BO.sql.”
- “Run the script PRIOR to installation of IBM TRIRIGA Application Platform version 3.5.0. NEVER run the script after upgrading to 3.5.0.”
Our application is 10.4 and platform is 126.96.36.199. How can the SQL script be applied to update the system fields with the sub-attribute type of CreatedDateTime to CreatedDateTime (Number) and ModifiedDateTime to ModifiedDateTime (Number)?
I found this technote on the minimum required database permissions for TRIRIGA:
Following are the minimum permissions.
Anything else is untested and unsupported.
ALTER USER $dbuser$ QUOTA UNLIMITED ON $data_tblspace$;
ALTER USER $dbuser$ QUOTA UNLIMITED ON $index_tblspace$;
GRANT ANALYZE ANY TO $dbuser$;
GRANT CREATE VIEW TO $dbuser$;
GRANT CREATE TABLE TO $dbuser$;
GRANT ALTER SESSION TO $dbuser$;
GRANT CREATE SESSION TO $dbuser$;
GRANT CREATE SYNONYM TO $dbuser$;
GRANT CREATE TRIGGER TO $dbuser$;
GRANT CREATE SEQUENCE TO $dbuser$;
GRANT CREATE PROCEDURE TO $dbuser$;
GRANT DROP PUBLIC SYNONYM TO $dbuser$;
GRANT CREATE PUBLIC SYNONYM TO $dbuser$;
GRANT CONNECT TO $dbuser$;
ALTER USER $dbuser$ DEFAULT ROLE CONNECT;
But the following permissions are restricted for our customer:
DROP PUBLIC SYNONYM
CREATE PUBLIC SYNONYM
Can you tell me if these permissions are only needed for installation? Or are they also required for runtime?
The IBM TRIRIGA product team does not test nor validate lower permissions than what is documented. All permissions granted to the user are required for the support of TRIRIGA, and removing permissions can lead to unexpected behavior, performance problems, and possibly data corruption.
During TRIRIGA install, what SQL GRANT statements are executed for the install to be successful? Are there specific object names that you can grant access to TRIDATA on those objects other than granting to PUBLIC?
Granting PUBLIC access to database objects goes against security policy. The problem is that you don’t know which objects TRIRIGA might need. You need to get specific object names so that you can potentially grant access to TRIDATA on those objects, rather than granting to PUBLIC.
You might have tried to revoke public access to a database object which caused an ERROR on com.tririga.architecture.security.dataaccess.AuthenticationDAO and caused TRIRIGA to freeze while restarting TRIRIGA.
The following SQL GRANT statements are executed during TRIRIGA install…
I am installing TRIRIGA 3.5.0/10.5.0 on my local machine with WebLogic and Oracle 12c. But I am getting the following error:
[java] Connecting to system@jdbc:oracle:thin:@localhost:1521:orcl
[java] Exception encountered! java.sql.SQLException: ORA-65048: error encountered when processing the current DDL statement in pluggable database PDBORCL
[java] ORA-00959: tablespace 'TRIDATA_DATA' does not exist...
Installing to a pluggable database (PDB) or container database (CDB) is not supported in TRIRIGA 3.5.0. To resolve this, you will need to use the 3.5.2 platform installer or higher. Here is the 3.5.2 release note:
Installation: The installation of TRIRIGA Platform now supports connecting to Oracle via Service Name. This will allow you to use a RAC URL, or PDB installations. The installer will prompt for connecting via the older SID, or the Service Name as a section choice. (Tri-213951)
[Admin: This post is related to the 07.07.16 post and 01.26.16 post about getting an Oracle 12c error during install.]