Loading the repository

The InterChange Server repository is a database that holds metadata about InterChange Server components. You need to load the repository objects (Java archive (.jar) files that hold the metadata) into the database. These .jar files are located in various subdirectories of the ProductDir directory. See Table 24 for the locations of various repository objects.

Note:
InterChange Server must be running in order for you to load the repository.

To load the repository:

  1. Navigate to the directory holding the repository object you want to load.
  2. Load the repository using repos_copy, passing as arguments the server name, the InterChange Server user name and the password, and each input file:
    ./repos_copy -sservername -uusername -ppassword -iinput_JarFile
    

    In the preceding command, servername is the name of the InterChange Server, username is the name of the InterChange Server user, password is the password for the InterChange Server user, and input_JarFile is the fully qualified path and name of the .jar file to be loaded into the repository.

    The repos_copy command loads the data into the repository tables. For more information about loading the repository and the repos_copy command, see the Implementation Guide for WebSphere InterChange Server.

    Note:
    There are several optional arguments that can be added to the repos_copy command and these are detailed in WebSphere InterChange Server: System Administration Guide. The argument -xmsp is a new optional flag to import membership and security policy information. The membership and security policy is part of the role-based access control (RBAC) that is used to appropriately limit access and permissions of users, see the WebSphere InterChange Server: System Administration Guide for more details.
  3. Restart InterChange Server, as follows:
    1. Follow the instructions in section titled "Shutting down InterChange Server" in the Implementation Guide for WebSphere InterChange Server to shut down the server.
    2. Follow the instructions in Starting InterChange Server to start the server up again.

    You can shut down InterChange Server with the -stop option. When the server restarts, all items loaded into the repository are stored in memory and available.

  4. After InterChange Server is running, connect to the server instance using System Manager as described in the section titled "Registering an InterChange Server instance" in the Implementation Guide for WebSphere InterChange Server.

    You can use the InterChange Server Component Management view in System Manager to browse the components loaded into the server.

Note:
The repos_copy command is known to fail for the Email.jar file during a fresh install of InterChange Server. It is possible to deploy components such as Email.jar with System Manager. The steps to load the Email.jar file into the repository are:
  1. Invoke the System Manager (see the WebSphere InterChange Server: System Administration Guide for details)
  2. import the Email.jar file into InterChange Server
  3. create a user project
  4. deploy the user project.

Copyright IBM Corp. 1997, 2004