To Migrate a Version 2.2 Agent:

1. Login to the server where the version 2.2 agent is installed.

   To migrate the agent, you must have write permission to the version 2.2 agent's deployment container files and directories.

2. Stop the Application Server instance for the version 2.2 agent.

3. Create a directory to download and unzip the version 3.0 agent. For example: v30agent

4. Download and unzip the version 3.0 agent that corresponds to the version 2.2 agent you are migrating.

   The version 3.0 agents are available from the sites listed in Downloading and Unzipping the appserver_v9_agent.zip Distribution File.

5. Change to the version 3.0 agent's /bin directory.

   For example, if you downloaded and unzipped the version 3.0 Application Server and GlassFish agent in the v30agent directory:

   cd /v30agent/j2ee_agents/appserver_v9_agent/bin

6. On Solaris and Linux systems, set the permissions for the agentadmin program as follows, if needed:

   # chmod 755 agentadmin

7. Run the version 3.0 agentadmin program with the --migrate option. For example:

   ./agentadmin --migrate

8. When the agentadmin program prompts you, enter the path to the version 2.2 agent's deployment directory. For example:

   ...
   Enter the migrated agent's deployment directory:
   /opt/j2ee_agents/appserver_v9_agent
   ...

   In this example, /opt is the directory where you downloaded and upzipped the version 2.2 agent.

   The agentadmin program migrates the version 2.2 agent.

9. After the agentadmin program finishes, set the following properties:

   1. In Agent_nnn/config/OpenSSOAgentBootstrap.properties, change:

      com.sun.identity.agents.config.username = new-v3.0-agent-profile-name

      For example:

      com.sun.identity.agents.config.username = AS9v3Agent

10. Copy the Agent_nnn/config/OpenSSOAgentConfiguration.properties file to the /bin directory where ssoadm is installed on the OpenSSO Enterprise server.

11. In OpenSSOAgentConfiguration.properties, add the un-encrypted version 2.2 agent profile password at the end of the file, as follows:

    userpassword=v2.2–agent-profile-password

12. On OpenSSO Enterprise server, create a password file for the OpenSSO Enterprise administrator (amadmin).

    This password file is an ASCII text file with only one line specifying the amadmin password in plain text. For example: /tmp/amadminpw

13. On OpenSSO Enterprise server, run ssoadm to create a new agent configuration in the OpenSSO Enterprise centralized agent configuration repository. For example:

    cd tools_zip_root/opensso/bin
    ./ssoadm create-agent -e / -b AS9v3Agent -t J2EEAgent -u amadmin 
    -f /tmp/amadminpw -D ./OpenSSOAgentConfiguration.properties

    In this example:

    • tools_zip_root is the directory where you unzipped ssoAdminTools.zip.

    • -e / specifies the specifies the root realm for the agent configuration.

    • -b AS9v3Agent specifies the version 3.0 agent configuration name.

    • -t J2EEAgent specifies the agent type for J2EE agents.

    • -u amadmin species the OpenSSO Enterprise administrator

    • -f /tmp/amadminpw specifies the path to the administrator password file.

    • -D ./OpenSSOAgentConfiguration.properties specifies the agent configuration file

    Caution: After you run ssoadm, you might want to delete OpenSSOAgentConfiguration.properties from the /bin directory. This file contains sensitive information, including as the agent profile password, and the original file is maintained on the server where the agent is installed.

14. Restart the Application Server and GlassFish instance for the migrated agent.

Next Steps

After you migrate the agent, you can manage the new 3.0 agent configuration using the OpenSSO Enterprise Administration Console or the ssoadm utility, as described in Managing the Application Server and GlassFish Agent.