PeopleSoft IT Asset Management 9.1 PeopleBook

Working with the IT Asset Inventory Tool

This chapter provides an overview of the IT Asset Inventory Tool and the load process and discusses how to:

Set up the third-party integration.
Request third-party inventory data.
Implement Agnostic Integration.

Understanding the IT Asset Inventory Tool

To manage your IT assets effectively, you need an accurate and comprehensive inventory of your hardware and software environments.

PeopleSoft IT Asset Management uses third-party software to discover and track hardware information and installed software packages. In addition to managing discoverable assets, the inventory tool, in conjunction with the PeopleSoft IT Asset Management solution, helps identify assets that are non-reporting (or non-discovered).

The information that the third-party software provides is the cornerstone of the asset management solution. PeopleSoft IT Asset Management takes the information and validates it against the asset repository, providing a high level of accuracy and authenticity to the repository. The reconciliation process enables you to synchronize your asset records with what actually exists on your network.

The third-party software collects inventory and usage data while the asset repository stores asset relationships. PeopleSoft IT Asset Management gives you the ability to reconcile and verify the relationships between your assets and users, locations, departments, cost centers, and associated contracts.

This diagram illustrates the process flow from the third-party software to the PeopleSoft IT Asset Management asset repository.

Asset discovery process flow

Understanding Data Integration

PeopleSoft IT Asset Management is set up to communicate with the third-party inventory database using XML messages. The XML messages are handled through Integration Broker. The process flow for requesting third party inventory data consists of the following steps:

PeopleSoft IT Asset Management sends an XML message to the third-party software requesting inventory data.
The third-party software returns an XML response message indicating that the request was received or if there was a problem processing the request in the third-party system.
The third-party software returns the requested data in an XML file formatted for PeopleSoft IT Asset Management.
Once that response is received, an application engine Load process, IT_LOAD_PROC, is initiated to process the data that is returned from the third party. The Load process validates the data and interprets the actual values converting them into meaningful values that the Asset Repository can understand.

There are alternatives to this Request/Response model to integrate data from third-party discovery applications into PeopleSoft ITAM. The Agnostic Integration model provides alternatives to integrate inventory data without employing the Request/Response model. Agnostic Integration is designed to leverage open interface tables called pre-staging tables. This eliminates the need to build a tightly-coupled XML connector, which is required for the Request/Response model. Agnostic Integration provides efficiency for those organizations that are implementing ITAM as well as flexibility for those who rely on a third party's connector. The data still needs to be integrated into a delivered web service or directly into the pre-staging tables.

See Implementing Agnostic Integration.

The following diagram illustrates the process flow for requesting third party inventory data:

Third Party Inventory Process Flow

Understanding the Load Process

Once all the requested data (Message GET_DISCOVERYDATA_ACK) has been received, the View Request Status page displays "Success". All of the data from the XML has been received and written to application staging tables during subscription. An Application Engine process (IT_LOAD_PROC) is automatically submitted and uses the staging tables as input to produce translated data in the cache and error tables.

This cache data is then used by the compare process.

Note. You can view the results of the data integration via PeopleSoft Integration Broker Message Details. Check the status of the following Messages: GET_DISCOVERYDATA, GET_DISCOVERYDATA_STATUS_ACK, GET_DISCOVERYDATA_ACK.

The Load Process validates and translates the third-party data, consisting of. Serial Number, Manufacturer, Computer Type (IT Resource), Model, Primary User, Primary User Domain, Machine Name, IP Address, Date of Last Inventory, Software Titles, and Total Run Time. The Load Process translates the data from the third-party into data that is familiar to the asset repository (for example, Primary User + Domain = Employee ID). When this translation is successful, data is inserted into the cache table. Errors occurring during these translation edits will prohibit the IT device or software title from being inserted into the cache tables. Instead errors encountered will be inserted into the error tables with the applicable error code as well as a table that preserves the original third-party values. This is done to allow later processing of the data either by the comparison process or again by Load once a valid translation for the data has been created.

You can view the errors produced by the load process for the latest discovery request from a high level pagelet and drill down to the details on the View Integration Data Load Errors page.

This table lists the order of processing the translation edits:

Application Engine: IT_LOAD_PROC	IT_ERR_CODE	Comment	Reference
Checks for Duplicate Serial Numbers	010	Duplicate Serial ID Error	ASSET
Checks for the existence of a mapping of the primary user and domain to an employee ID	050	Unmapped Primary User/Domain - Empl ID	IT_LDAP
Retrieves Department and HR business unit for an Empl ID from the PS_JOB table for Employees "Primary Job".		HCM Integrated data	JOB
Retrieves the mapped GL Business Unit value for the HR Business Unit		HCM to GL Business Unit	BUS_UNIT_TBL_HR
Checks for unmapped/blank GL Business Unit value for the HR Business Unit	070	No GL BU Mapped to HR BU	BUS_UNIT_TBL_HR
Check for no HR Business Unit value in PS_JOB table	070	No GL BU Mapped to HR BU	BUS_UNIT_TBL_HR
Retrieves the max AM Business Unit value in the BU_BOOK_TBL table for the GL Business Unit			BU_BOOK_TBL
Retrieves the setIDs for Asset Subtype (AM_SUBTYPE), Manufacturer (MANUFACTURER), Location (LOCATION_TBL) where there is a MFG_ID			SET_CNTRL_REC
Retrieves the setIDs for Asset Subtype (AM_SUBTYPE), Manufacturer (MANUFACTURER), Location (LOCATION_TBL) where MFG_ID is blank.			SET_CNTRL_REC
Retrieves the Manufacturer when provided. Error if provided value is not in mappings.	040	Unmapped Manufacturer Error	IT_MAP_CD
Retrieves the IT_SUBTYPE and AM_SUBTYPE from the 3rd party value. Error if no mapping.	060	Unmapped Asset Subtype	AM_SUBTYPE, IT_SUBTYPE_LN
Retrieves the Location for IP Addresses that are not VPN. Error if not in mapping.	030	Unmapped IP Address Error	IT_IP_ADDR, IT_IP_ADDR_MAP

When no MFG_ID is returned from the third-party application , PeopleSoft IT Asset Management stores a blank MFG_ID to the IT_HRDWR_CACHE table.

Once completed, the system sets the "Last Request Date" to the current date for the IT Subtypes and reprocesses errors from prior requests unless more current data comes from the third-party application.

Setting Up the Third-Party Integration

This section discusses how to set up the integration between the third-party inventory software and PeopleSoft IT Asset Management.

Using the Data Discovery Integration Point

PeopleSoft IT Asset Management supports the Data Discovery integration point (GET_DISCOVERYDATA), an application message that is used to request information about discovered IT hardware and IT software in an organization's network.

When implemented, the GET_DISCOVERYDATA application messages send IT Subtypes and Software Titles to the third-party software when the Request Discovery Data process is submitted. IT subtypes are synonymous with the network devices, and represent items such as laptops, desktops, and servers. The Subtypes are mapped to values that exist in the third-party inventory database. For example, depending on the manufacturer of the device, the inventory information may indicate that the laptop is officially a "notebook". Therefore a laptop subtype could be defined to have third-party values of laptop, notebook, or portable.

Using the Discovery Data Status Integration Point

PeopleSoft IT Asset Management supports the Discovery Data Status integration point (GET_DISCOVERYDATA_STATUS_ACK), an application message that is used to monitor and display the status of the discovery request. The status can be viewed in the View Request Status page.

This table illustrates the steps in the process and the status displayed:

Steps	Status
Request is sent to the third-party system.	When the request is sent to the third-party system, the discovery request monitor displays the request with a status of Request Sent.
The third-party system returns a status acknowledgement of the request.	Once the acknowledgement is received, the request status is updated to Request received or Third party error. If the error code is returned, the error is displayed.
The third-party system processes the request and returns inventory data.	The file size is specified in the sending request (the file size can be changed in People Tools Options page. The Navigation is: PeopleTools > Utilities > Administration > PeopleTools Options). If the size of the xml response is greater than the value of the file size node in the xml Request, the inventory data is to be chunked and returned in one or more files. The FILE_CNT Node in the Response contains information regarding the total file count that is to be received for the request. While the files are being returned, the discovery request monitor displays a status of Receiving. The monitor updates the date and time to reflect when the last file was received. If the files are not transmitted, the status is updated to Error in Transmission after a user specified time period has elapsed. If the last file is received before all the other files are received, the request errors out. The monitor shows the status of Error in Transmission and the stage table is cleared. If the last file is received successfully, the status is updated to Success.

Using the Discovery Data Acknowledgement Integration Point

PeopleSoft IT Asset Management supports the Discovery Data Acknowledgement integration point (GET_DISCOVERYDATA_ACK), an application message that is used to receive the inventory data that you requested. The message consists of IT Hardware and IT Software data elements that are stored in the third-party database.

Requesting Third Party Inventory Data

This section discusses how to:

Define PeopleSoft IT Asset Management options for discovery requests.
Request discovery data.
Monitor discovery data requests.
View Integration Data Load Errors.

Use the Request Discovery Data (IT_DISCO_RUN) component to request third-party inventory data.

Pages Used to Request Discovery Data

Page Name	Definition Name	Navigation	Usage
Installation Options — Asset Management	INSTALLATION_AM	Setup Financials/Supply Chain, Install, Installation Options Click the Asset Management link.	Define the timeout period for discovery requests.
Request Discovery Data	IT_DISCO_RUN	IT Asset Management, Asset Discovery and Validation, Request Discovery Data, Request Discovery Data	Set run control options to publish XML requests for inventory data.
View Request Status	IT_RQST_STATUS	IT Asset Management, Asset Discovery and Validation, View Request Status, View Request Status	View the status of the request made to the third-party application.
View Integration Data Load Errors	IT_LOAD_ERRORS	IT Asset Management, Asset Discovery and Validation, View Integration Data Errors, View Integration Data Load Errors	View the errors produced by the load process for the latest discovery request.

Defining IT Asset Management Options

Access the Installation Options — Asset Management page (Setup Financials/Supply Chain, Install, Installation Options).

See Defining Asset Management Installation Options.

Solutions

IT Asset Management Installed	Select if you have installed IT Asset Management. The ITAM Options group box is displayed.
Discovery Request Timeout (Sec)	Enter the number of seconds that processing will wait for a response from a request for inventory data from the third party. This interval applies to both the first response as well as subsequent responses in a single message transaction, in the case where the message contains more than one message file.
Batch Limit	Used for Manage Exceptions. See Setting the Batch Limit.
Source Device Groups from ARM	This option is used as a default for the Software Device Groups page. Newly created Device Groups will use this as the value for the Source From ARM field.

Requesting Discovery Data

Access the Request Discovery Data page (IT Asset Management, Asset Discovery and Validation, Request Discovery Data, Request Discovery Data).

Streamline Batch Process

Select to run Compare Asset Repository automatically after the third-party data is processed. If you select Streamline Batch Process, and a Run Control for Compare Asset Repository does not exist, a dialog gives you the choice of having the run controls created automatically or manually. If you choose to create the run controls manually, respond by clicking the Cancel button. This deselects the check box so that you can save the page. You can then navigate to the other Run Control pages to manually create them. Both run control pages can be accessed by using the links at the bottom of the page.

When run controls are created automatically for the Compare Asset Repositories and Metrics processes, they are created with same Run Control ID. In the example above, the run controls will be created with Run Control ID of ABC. Conversely, if the user wants to create the run controls manually but wishes to streamline batch processes, the user needs to manually create two run controls with the same Run Control ID. Streamline Batch Process will not be implemented with run controls that have different Run Control IDs.

Note. When the Compare Assets process is run, it may also perform actions to correct the exceptions. Business Rules can be defined to automatically execute actions. In this way, the Streamline Batch Process option can truly be a completely automated process without user intervention.

Third Party Value

Third Party Hardware displays all IT subtypes that have the Discover/Reconcile flag selected on the IT Subtypes page.

Third Party Software displays all software titles with Track Requisition or Permission Required selected on the Define Software Title page.

Last Request Date

Displays the date of the last asset inventory data request for each third-party value.

Compare Asset Repositories Run Control

Click to view, create, or edit the Compare Asset Repositories run control.

Metrics Run Control

Click to view, create, or edit the Metrics run control.

Note. Remember to check Integration Broker for message details.

Viewing Request Status

Access the View Request Status page (IT Asset Management, Asset Discovery and Validation, View Request Status, View Request Status).

The View Request Status page displays the status of requests for inventory data from the third-party system. All fields in the grid are display only.

Viewing Integration Data Load Errors

Access the View Integration Data Errors page (IT Asset Management, Asset Discovery and Validation, View Integration Data Errors, View Integration Data Load Errors).

The View Integration Data Load Errors page can be accessed directly or from links on the Integration Data Load Errors portal pagelet. This page displays errors detected from the latest successful completion of the ITAM Data Load process (IT_LOAD_PROC Application Engine).

See Using PeopleSoft Asset Lifecycle Management (ALM) Portal Pack.

See Using Pagelets Enabled by PeopleSoft IT Asset Management.

Implementing Agnostic Integration

This section provides an overview of Agnostic Integration and discusses how to set up the integration between the third-party inventory software and PeopleSoft IT Asset Management.

Understanding Agnostic Integration

The purpose of Agnostic Integration is to provide alternative options to integrate inventory data from third-party discovery applications to PeopleSoft ITAM without employing the Request/Response model. However, the Request/Response model remains an option for the integration and the functionality is not impacted by Agnostic Integration.

Agnostic Integration is designed to leverage open interface tables called pre-staging tables. This eliminates the need to build a tightly-coupled XML connector, which is required for the Request/Response model. Agnostic Integration provides efficiency for those organizations that are implementing ITAM as well as flexibility for those who rely on a third party's connector. The data still needs to be integrated into a delivered web service or directly into the pre-staging tables.

The pre-staging tables can be populated directly using a custom program or via a one-way asynchronous inbound web service. The agnostic approach assumes that a third party can already provide an export of the discovery data as part of their native product. In this case, the third party does not need to understand a request from PeopleSoft ITAM. The only requirement is to transform the data directly into the pre-staging tables or into the web service in order to populate the pre-staging tables. This integration model is more loosely coupled than the Request/Response model, which remains an option for integration.

The following describes terms that are commonly used when describing the Agnostic Integration framework:

Request/Response Model	This is the asynchronous XML Request/Response integration option. A request is submitted using the Request Discovery Data run control page and a message is published by Integration Broker to the 3rd party. The request provides the parameters for the data from the discovery system. The response contains the assets matching those request parameters. Once the response is received, the IT_LOAD_PROC is automatically submitted to perform data translation and mapping edits. This integration is considered tightly coupled with the third party vendors.
Pre-Staging Tables	The pre-staging tables are interface tables for the hardware and software attributes of the discovered IT assets. They are used to integrate discovery or inventory data from third-party discovery applications. They are IT_DISCO_HW_PRE and IT_DISCO_SW_PRE. One of the options available in the Agnostic Integration feature is to utilize these tables as the integration point. The tables can be populated manually through a custom program or through the a web service
Web Service	Web service, as used in this section, refers to the inbound asynchronous XML message. It is one of the two additional integration options made available by the Agnostic Integration framework.
Integrate Discovery Data	This is the run control page that is used to submit the data load Application Engine process, IT_LOAD_PRE. Select to process all Batch IDs and all errors or specific Batch IDs and errors.

The following diagram represents the process flow for the Agnostic Integration framework:

Agnostic Integration process flow

This section discusses how to:

Select an integration option.
Run the data load process (IT_LOAD_PRE).
Identify preload errors.
View preload errors.

Pages Used to Process Agnostic Integration

Page Name	Definition Name	Navigation	Usage
Integrate Discovery Data	IT_PLOAD_RUN	IT Asset Management, Asset Discovery and Validation, Integrate Discovery Data	Set run control options to submit the IT_LOAD_PRE Application Engine process, Select to process all Batch IDs and all errors or specific Batch IDs and errors.
IT Assets Pre-load Errors	AM_IT_PRE_LOAD_ERRORS	Reporting Tools, Query, Query Manager, AM_IT_PRE_LOAD_ERRORS	Run this query to identify errors from the IT_LOAD_PRE process. The query lists the Serial IDs of the devices that fail any of the pre-stage error edits.

Selecting an Integration Option

The following section discusses the two options for Agnostic Integration:

Manual
Web Service

Note. The two options, Manual and Web Service, are processed as mutually exclusive tasks (TASK_ID). If you elect to use both options to integrate discovery data, you may lose the ability to filter out duplicate Serial ID errors. Since the two sources of data are processed separately, the data validation performed by the IT_LOAD_PROC will only check for duplicate Serial IDs within the one source.

Manual Option

This option is selected when using a custom program to manually load the pre-staging tables for hardware and software discovery data (IT_DISCO_HW_PRE and IT_DISCO_SW_PRE). When using this method, keep in mind the following points:

Create a custom program or use a third-party program to populate the pre-staging tables.
Fix or remove duplicate or invalid Serial IDs before loading the pre-staging tables. An example of an invalid Serial ID might be a blank value.
After ensuring that all discovery data is loaded to the pre-staging tables, use the run control page, Integrate Discovery Data, to submit the IT_LOAD_PRE Application Engine program, which processes data from the pre-staging tables and loads them to the staging tables. This process also calls the IT_LOAD_PROC Application Engine process to perform validations, translations, and transformations of the data.
Ensure there is no orphan software data. All integrated software data (IT_DISCO_SW_PRE) must have a parent record (IT_DISCO_HW_PRE). This is consistent with the existing expectation of data that is provided to ITAM from third party systems.

Web Service Option

The web service option uses an asynchronous inbound XML message to populate the pre-staging tables for hardware and software discovery data (IT_DISCO_HW_PRE and IT_DISCO_SW_PRE). When using this method, keep in mind the following points:

This method does not require a tightly coupled XML connector or dependence upon a preexisting partnership with a particular discovery vendor to populate the pre-staging tables.
The web service (PROCESS_DISCOVERYDATA) populates the pre-staging tables and submits the IT_LOAD_PRE Application Engine process automatically; however, reprocessing of web service errors is submitted from the Integrate Discovery Data run control page.
The web service implements an xml file-counting solution, which leverages the xml node FILE_CNT. After receiving all of the xml files, the IT_LOAD_PRE process is submitted automatically.
Do not introduce duplicate or invalid Serial IDs in the xml. An example of an invalid Serial ID might be a blank value.
Ensure that the BATCH_ID node value is the same throughout the XML file.

Running the Data Load Process (IT_LOAD_PRE)

Use the Integrate Discovery Data run control page to submit the IT_ LOAD_PRE Application Engine process when the pre-staging tables are populated manually by a custom program. Additionally, this page can be used to process pre-staging errors resulting from either method (manual or web service).

Access the Integrate Discovery Data page (IT Asset Management, Asset Discovery and Validation, Integrate Discovery Data).

Streamline Batch Process

Select to enable the option to automatically submit (streamline) the Compare Asset Repository and Generate Metrics processes.

Process All Batch IDs

Select to process all the unique Batch IDs in the pre-staging table. When selected, any existing rows in the grid are disabled. The IT_LOAD_PRE batch program processes all data in the pre-staging tables and overrides the Batch IDs that are specified in the grid. However, if there are rows in the grid where Process Errors is selected, the errors related to that Batch ID are also included as input for the IT_LOAD_PRE batch process.

Process All Errors

Select to process all the rows in the pre-staging error tables. When selected, the Process Errors check box is disabled in any existing grid row, The IT_LOAD_PRE batch program processes all data in the pre-staging error tables. It overrides the Process Errors option at the grid level.

Batch IDs

Batch ID	Select one or more specific BATCH_IDs for the IT_LOAD_PRE Application Engine program to process. If the Process All Batch IDs check box is selected, this field is disabled.
Process Errors	Select to specify if pre-stage errors are to be processed for the selected BATCH_ID. If Process All Batch IDs or Process All Errors is selected, this field is disabled.

Compare Asset Repositories Run Control and Metrics Run Control

Click the links that are provided to access the Compare Asset Repository and Generate Metrics run control pages. Verify or change the run control parameters for the two automatically-created run controls.

Note. When using the web service to populate the pre-staging tables, the IT_LOAD_PRE process is launched automatically when all the xml files are received successfully by Integration Broker. The user ID that is used to automatically submit the process is the user ID that is specified by the publishing Integration Broker node (&From Message Credential). If the user ID that is defined on the external node is used to enter the run controls on the Integrate Discovery Data page, and if a Web Service is received that has the same RUN_CNTL_ID, it will take precedence over the one entered on the page. (The Web Service utilizes the same tables to store the run control parameters. In this example, the records that are entered on the page are replaced by the parameters in the Web Service. The records are then deleted when the Web Service is processed).

Identifying Preload Errors

The following table provides a description of the preload errors that can result from the edits performed by the IT_LOAD_PRE Application Engine process:

Preload Errors	Description
Orphan Software error (100)	This is the first edit that is performed. It is only performed when directly populating the pre-staging tables using a custom program. This is done in order to validate the parent/child relationship for hardware and software data. To fix this error, a parent hardware record is needed. A record could be inserted in the IT_DISCO_HW_ER2 table; or, if resubmitting all of the data, the record should be inserted in the IT_DISCO_HW_PRE table.
Software Title/Known As Mapping error (090)	This is the next edit performed (first one for the Web Service option). To fix this error, ensure that the KNOWN_AS value in the xml is mapped on the ITAM Code Mappings page. Add the mapping and then use the run control page to reprocess the errors.
IT Resource Mapping error (080)	This is the third edit that is performed. To fix this error, ensure that you have the IT_RESOURCE value mapped on the IT Subtype page. It should be an active Third Party Value that is listed in the grid.

Viewing the Preload Errors

Run the delivered query, AM_IT_PRE_LOAD_ERRORS, to retrieve a report that lists the Serial IDs of the devices that fail any of the preload (pre-stage) error edits resulting from the IT_LOAD_PRE process. ITAM requires that Serial IDs be unique in each application in order to successfully integrate the discovered assets into ITAM. This query identifies duplicate Serial IDs.

Access the AM_IT_PRE_LOAD_ERRORS query (Reporting Tools, Query, Query Manager, AM_IT_PRE_LOAD_ERRORS).

The report provides the following fields Serial ID, IT Load Error Code, Third Party Value and Source Key ID.

Streamline Batch Process	Select to run Compare Asset Repository automatically after the third-party data is processed. If you select Streamline Batch Process, and a Run Control for Compare Asset Repository does not exist, a dialog gives you the choice of having the run controls created automatically or manually. If you choose to create the run controls manually, respond by clicking the Cancel button. This deselects the check box so that you can save the page. You can then navigate to the other Run Control pages to manually create them. Both run control pages can be accessed by using the links at the bottom of the page. When run controls are created automatically for the Compare Asset Repositories and Metrics processes, they are created with same Run Control ID. In the example above, the run controls will be created with Run Control ID of ABC. Conversely, if the user wants to create the run controls manually but wishes to streamline batch processes, the user needs to manually create two run controls with the same Run Control ID. Streamline Batch Process will not be implemented with run controls that have different Run Control IDs. Note. When the Compare Assets process is run, it may also perform actions to correct the exceptions. Business Rules can be defined to automatically execute actions. In this way, the Streamline Batch Process option can truly be a completely automated process without user intervention.
Third Party Value	Third Party Hardware displays all IT subtypes that have the Discover/Reconcile flag selected on the IT Subtypes page. Third Party Software displays all software titles with Track Requisition or Permission Required selected on the Define Software Title page.
Last Request Date	Displays the date of the last asset inventory data request for each third-party value.
Compare Asset Repositories Run Control	Click to view, create, or edit the Compare Asset Repositories run control.
Metrics Run Control	Click to view, create, or edit the Metrics run control.

Streamline Batch Process	Select to enable the option to automatically submit (streamline) the Compare Asset Repository and Generate Metrics processes.
Process All Batch IDs	Select to process all the unique Batch IDs in the pre-staging table. When selected, any existing rows in the grid are disabled. The IT_LOAD_PRE batch program processes all data in the pre-staging tables and overrides the Batch IDs that are specified in the grid. However, if there are rows in the grid where Process Errors is selected, the errors related to that Batch ID are also included as input for the IT_LOAD_PRE batch process.
Process All Errors	Select to process all the rows in the pre-staging error tables. When selected, the Process Errors check box is disabled in any existing grid row, The IT_LOAD_PRE batch program processes all data in the pre-staging error tables. It overrides the Process Errors option at the grid level.