WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Adding a new agent by downloading agent properties

This topic describes how to create a new agent by downloading agent details from an update site using the WebSphere® Premises Server Administrative Console.

Before you begin
Before downloading agent details from an update site, make sure that WebSphere Application Server is running.
About this task
You can define an agent by downloading agent properties from an update site. For information about update sites, refer to Working with update sites.
Procedure
  1. Open the WebSphere Premises Server Administrative Console. The Welcome page displays.
  2. In the left navigation panel, navigate to Data Capture Configuration > Agent Configuration. The Agent Configuration panel displays.
  3. Click Download Agent. The Download Agent Properties panel displays.
  4. Select Create a new agent.
  5. In the Agent Type field, select the type of agent from the list. An agent can be ControllerType, DeviceType, or LocationType. Then click Next.
  6. Select the update site to use for the new agent. Click Next.
  7. Select a feature for the agent. The list of features is retrieved from the update site. Click Next.
    Note: The name and description of the new agent are taken from the feature you select.
  8. Accept the license agreement and click Next.
  9. Confirm your selections and then click Finish to begin the download process.
Results
During the download process, the status will be displayed in the Agent Configuration panel. If errors occur, you can delete the agent and then recreate it.
Note: During the download process, an XSL style sheet is used to transform the agent configuration supplied by the agent's vendor to the format that is required by WebSphere Premises Server. The default XSL file, IBMRFIDPremisesDefaultMapping.xsl, is stored in the IHS_HOME\bundles\import_mappings directory. You can override the default XSL transformation by creating a new XSL file and storing it in the IHS_HOME\bundles\import_mappings directory. The XSL file must have the same name as the update site's feature with an .xsl extension. The XSL file is only applied to device agents.

The input to and output from the XSL file follows the same schema used in the import XML file. See Sample XML schema and configuration files.


Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.