WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: Linux, Windows


Configuring a Tivoli Intelligent Orchestrator file repository

Use Tivoli Intelligent Orchestrator file repositories to define sets of servers that centrally store software.

Before you begin

Before configuring a Tivoli Intelligent Orchestrator file repository, you must know the repository location to configure. You can create a new repository location on your server, or use an existing folder. If you plan to use a system other than the Tivoli Intelligent Orchestrator server as your file repository, verify that the system is configured for management by Tivoli Intelligent Orchestrator.

About this task

Use a file repository to enhance silent installation. For more information about silent installation, see Silent installation. If you are using a file repository, you do not have to verify that the software images exist on all of the systems that you are provisioning. Instead, you can verify that the software images exist in the file repository only. When the installation workflow runs, the workflow deploys the software images onto the target systems automatically from the file repository.

Procedure

  1. Create the Tivoli Intelligent Orchestrator file repository.
    1. In the Tivoli Intelligent Orchestrator Web interface, click Inventory > Infrastructure > File repositories.
    2. Click Edit > Add File Repository.
    3. Set the properties of the file repository, including the root path of the file repository. The root path of the file repository is the location for the software images. When the workflow runs, it looks for the required software images in the root path on file repository server, and then copies the images to the system that you are provisioning. If the required software images do not exist in this path on the file repository, the workflow creates an error message. For example, the path might be /opt/IBM/tivoli/SWrepository/XDFiles.
    4. Click Save. The file repository is created.
  2. Create the necessary credentials for your servers. Set the credentials on the file repository and target system to trust each other so that the copy utility works. To add or modify credentials, you must use service access points. To add a new service access point to the server, perform the following steps:
    1. Click Data center assets and resources > Inventory > Servers and click the server that you want to work with. Click the Credentials tab.
    2. Click Edit > Add Access Point. Complete the fields as follows:
      • In the Type list, click the type of protocol to use for connecting to that service.
      • Select Host if you want this server to be the host that provides the service through service access points. Optionally, you can enter the service access point domain and context. You can use the context field to define a unique identifier for this service access point.
      • Type the port number to use for this service access point. Based on the selected type of protocol, the default port for the SAP is displayed. Set that port number to 0 for a client SAP (The host option is not selected).
      • Select the Authentication check box if the access to that service requires authentication. If authentication is required, specific credentials must be defined, corresponding to the selected type of protocol.
      • Click Perform using dcm.interaction to run the Device. Create Service Access Point logical operation.
    3. Click Save.
  3. Prepare the WebSphere Extended Deployment base installation, Update Installer, and interim fix images.
    1. Create a zip file from the WebSphere Extended Deployment base CD. Verify that the install executable file is in the top level directory inside of the zip file. Put the zip file in the root directory of the file repository. You specified this directory when you created the repository in Tivoli Intelligent Orchestrator.
    2. Download the Update Installer zip or tar file, and copy it to the root directory of the file repository. The Update Installer is a tool that you use to install service packs on top of an existing WebSphere Extended Deployment installation. Download the Update Installer at the following Web address: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24008401.
    3. Copy the interim fix .pak file to the root directory of the file repository.
  4. Add the properties to complete your configuration. See Configuration properties for Tivoli Intelligent Orchestrator for more information.

Results

Tivoli Intelligent Orchestrator can automatically provision WebSphere Extended Deployment nodes, using the file repository to install WebSphere Extended Deployment instead of installing the installation image to each system.

What to do next

Before you use the workflow to install WebSphere Extended Deployment, verify that the Update Installer silent install response file is in the same location as the WebSphere Extended Deployment silent installation response file on the Tivoli Intelligent Orchestrator server. When the installation workflow runs, it copies over the image, unpacks the image, copies the response file, invokes the installer, and then checks the result.



Related concepts
Tivoli Intelligent Orchestrator integration
Related tasks
Configuring Tivoli Intelligent Orchestrator to work with WebSphere Extended Deployment
Installing the WebSphere Extended Deployment driver into Tivoli Intelligent Orchestrator
Task topic    

Terms of Use | Feedback

Last updated: Nov 30, 2007 3:59:37 PM EST
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/odoe_task/ttiocreaterepos.html