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 (18.104.22.168) 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.]
Is there a way to disable the CI auto-sync on login? I know you can uncheck the box in the CI options menu, but for certain drawings, it continues to sync on login.
You should be able to open the drawing, go to Drawing > Properties, and clear the option to sync when the drawing opens. Save the drawing, and it should obey this setting the next time you open it.
[Admin: To see other related posts, use the Integrator 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.]
We would like to use hatch patterns instead of solid fills in our graphics. There is a TRIRIGA wiki page “Graphics Section Hatching” that outlines how this can be done, but it isn’t working.
We needed to perform a server-only change. We needed to verify the uploaded image files in the CI hatch pattern record, and see the pattern rendered in the graphics section. Moving forward, we resolved an issue where assigning hatch records to the record results in the graphics section reports did not actually render the hatch images as expected.
[Admin: This post is related to the 06.03.15 post about displaying hatch patterns in graphics sections. To see other related posts, use the Hatch 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 22.214.171.124: Troubleshooting CAD Integrator V.12 – Resolving No CAD Types Found on installation
- Make sure you know that 126.96.36.199 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.]
This wiki is meant to help you troubleshoot and provide a workaround for the following publish error in MicroStation. It has primarily been seen in Select Series 4, but could happen in earlier versions of MicroStation. When publishing, the publish will fail. When you look at the server log, if you see the following error, then this issue is involved (the ACDSDATA, in particular):
com.tririga.platform.error.PlatformRuntimeException: Error processing DXF - last line read: 23500. Error: com.tririga.platform.graphics.vector.dxf.processor.UnexpectedGroupDataException: DXF contained an unexpected section type: Group-code:2 Value:'ACDSDATA' Source line:23499...
This error occurs due to the way in which MicroStation creates its DXF file for publishing for TRIRIGA, depending on its settings. The fix below is used to update MicroStation’s DXF output options to output using the “2010/2011/2012” format…
[Admin: This post is related to the 10.20.16 post about CI failing to publish. To see other related posts, use the MicroStation 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.]