An enterprise service is a pipeline for querying system
data and importing data into Control Desk from
an external system. Six enterprise services are configured for the
software catalog imports.
You define enterprise services in the Enterprises Services application.
Enterprise services can send data to an external system (outbound)
and receive data from an external system (inbound). You can configure
enterprise services to process data synchronously (without a queue)
or asynchronously (with a queue). Enterprise services can use multiple
protocols, such as Web services and HTTP.
An enterprise service has data processing layers that transform
data and apply business processing rules to data before it reaches
the system objects. These processing layers include:
- Processing rules – The integration framework provides a rule engine
where you can filter and transform the XML message.
- User exit – The user exit specifies a Java™ class that you can use to filter, transform
data, and implement business logic. You can use this class as part
of an installation-customization.
- Data processing class – The processing class specifies a Java class that you can use to filter,
transform data, and implement business logic.
- XSL map – The XSL map specifies an XSLT style sheet that you can
use to transform data and map the XML data message to another format.
When the inbound data message reaches the object structure layer,
the XML data message must be in the format of the object structure
schema. The system then can process the data successfully.
For importing software catalog data into
Control Desk,
external services are configured that use inbound asynchronous communication.
Control Desk provides
an XSLT transform for each object structure defined. The following
tables summarize the enterprise services defined for
Asset Management for IT.
The following parameters are the same for all six enterprise services.
- Operation – Sync (synchronize objects)
- Adapter – TLOAM (the adapter defined for software catalog imports)
- Use External Schema – check box is selected
Table 1. Enterprise service for manufacturers| Enterprise service parameter |
Value for the enterprise service used to import
software catalogs |
|---|
| Enterprise service name |
TAMITINTMF |
| Description |
Manufacturers |
| XSL map |
TloamManufacturers.xsl |
Table 2. Enterprise service for software| Enterprise service parameter |
Value for the enterprise service used to import
software catalogs |
|---|
| Enterprise service name |
TAMITINTSW |
| Description |
Software catalog |
| XSL map |
TloamSoftware.xsl |
Table 3. Enterprise service for software hierarchy| Enterprise service parameter |
Value for the enterprise service used to import
software catalogs |
|---|
| Enterprise service name |
TAMITINTSWVAR |
| Description |
Identity links to variants |
| XSL map |
TloamSwVariant.xsl |
Table 4. Enterprise service for software relationships| Enterprise service parameter |
Value for the enterprise service used to import
software catalogs |
|---|
| Enterprise service name |
TAMITINTSWREL |
| Description |
Software relationship |
| XSL map |
TloamSwRel.xsl |
Table 5. Enterprise service for software catalog| Enterprise service parameter |
Value for the enterprise service used to import
software catalogs |
|---|
| Enterprise service name |
TAMITINTSWCAT |
| Description |
Software knowledge base identity |
| XSL map |
TloamSwCatalog.xsl |
Table 6. Enterprise service for part number| Enterprise service parameter |
Value for the enterprise service used to import
software catalogs |
|---|
| Enterprise service name |
TAMITINTSWPRTNUM |
| Description |
Part numbers |
| XSL map |
TloamSWPartNumber.xsl |