Import process for Asset Discovery for z/OS data
The cron task instance that imports catalog data from Asset Discovery for z/OS® performs several tasks to retrieve and process data. Understanding these steps is useful when planning customizations or troubleshooting problems.
Figure 1 illustrates the steps in the import process. The process steps are explained following the figure.
Step 1: Retrieve the software catalog data file
The administrator saves the file exported from Asset Discovery for z/OS in the working directory that was specified in the TEMPDIR cron task parameter. The file must have exactly the same name that was specified in the TEMPFILE cron task parameter, and the file must not be compressed.
Step 2: Perform XSL transformations
The data file is run through several XSL transformations, which produce the following additional files in the temporary directory.
- Tad4zManufacturers.xml
- Tad4zSoftware.xml
- Tad4zSwRel.xml
- Tad4zSwVariant.xml
- Tad4zSwCatalog.xml
- Tad4zSwPartNumber.xml
Each time the cron task is run, all files in the directory are overwritten. If the file is not refreshed, there is a problem with the transformations. To diagnose these problems, run the cron task with DEBUG logging enabled and send the log to customer support.
Step 3: Load files into Enterprise Services
Each file is loaded using the Enterprise Services configured to the TAMITEXTSYS External System. There is an endpoint configured to the external system, but it is not actually used in the loading of the files. You can test these loads by using the Data Import feature to process the files individually.
Step 4: Integration framework processing
The integration framework retrieves messages that are loaded into the JMS queues and processes them individually against the business objects in the software catalog application to make sure that the data conforms correctly to the latest business rules. This step is not controlled directly by the cron task instance for software catalog imports.