(imported comment written by F47Y_venkat_avirneni)
HI Fernando
We are configuring TEM to load data into TAMIT, I have followed the below given steps from IBM. We are struck at step 9, we couldn’t see TAMIT Integration properties. TAMIT Integration properties are not showing up at step 9. What could have caused this issue. How to debug the issue
- Subscribe to the TAMIT site:
a. Obtain the TAMIT site masthead file, which is installed with Integration
Composer and located at:
Integration Composer_dir/data/dataschema/tem_sua_1.3/TEM DPA
Integration.efxm (Find the attachment)
b. Open the Tivoli Endpoint Manager console using a Master Operator
account, and select:
Tools > Add External Site Masthead
c. Navigate to the masthead file, TEM DPA Integration.efxm, and click OK.
- In the left pane of the console, from the All Content view, select the TAMIT
Integration folder.
- In the right pane, select All computers and click Save Changes to subscribe
all computers to the site.
- In the left pane of the console, from the All Content view, select:
Sites > TAMIT Integration > Analyses.
- In the right pane, select all the analyses records, then right click and select
Activate. Each of the analyses records should display Activated Globally. If
they display Activated Locally, deactivate them and use a Master Operator
account to reactivate them.
After activation, you can select any of the analyses and see the data coming in
from the field computers on the Results tab.
To use the new analyses properties, you must first add them to the Software
Use Analysis inventory database, as described in the next steps.
-
Open the Software Usage Analysis interface and log in.
-
http://For Software Use Analysis 1.3.1 (or later) users only
Run an import (or wait
for a scheduled import to run) to get your new properties to appear in the
system. To run an import on demand (rather than waiting):
a. Open the Software Usage Analysis Control Panel and on the left pane
select Import Options.
b. On the right pane, in the Run Now section, clear the Perform full import
check box and click Run.
Depending on the size of your deployment, the import might take a while to
run. You can monitor progress by clicking on one of the other items in the
Control Panel items list, which will redirect you to the log viewer.
Note: If you are using BigFix DSS SAM or Software Use Analysis 1.3.0 (or
earlier), you do not need to run an import until step 11.
- Add the properties to the system.
a. From the Software Usage Analysis Control Panel, left pane, select
Computer Properties.
b. In the right pane, bottom left corner, click the + (plus) button to add a
property.
- In the Create Computer Properties window, select TAMIT Integration >
TAMIT::72::Audio devices > TAMIT::72::Audio information. When you select
TAMIT::72::Audio information, the Name field above the folder should
update to TAMIT::72::Audio information. Do not modify this name, because
the integration depends on the name being correct.
- Repeat step 9 for each of the other properties in the TAMIT Integration folder
that start with TAMIT::72. When you are finished, the data structures are
available in Software Use Analysis, but they are not populated with computer
data yet.
- Import the actual property data into the inventory database (or wait for a
scheduled import to run). To run an import on demand (rather than waiting):
a. Open the Software Usage Analysis Control Panel and on the left pane
select Import Options.
b. On the left pane, in the Run Now section, clear the Perform full import
check box and click Run.
Depending on the size of your deployment, the import might take a while to
run. You can monitor progress by clicking on one of the other items in the
Control Panel items list, which will redirect you to the log viewer.
- Configure Software Use Analysis to import text values longer than 255
characters:
a. Find DSS\rails\tmp\schema.ini in the Tivoli Endpoint Manager for
Software Use Analysis installation folder.
b. Open the schema.ini file and locate the section for properties.csv.
c. Change the Column 4 definition to: Col4=value LongChar and save the file