Migrating the data collector interactively

You can migrate an earlier maintenance level of the data collector interactively using the migration utility.

Before you begin

If you installed the WebSphere® Application Server or WebSphere Portal Server using a non-root user account, before you run the configuration utilities, verify that the non-root user has read and write privileges to the following agent directories in install_dir/yndchome/7.3.0.14.08 where install_dir is the installation directory of the WebSphere Applications agent:

• data
• bin
• runtime
• logs

Provide read and write permissions using the chmod 777 command, if required. Also, log in as the user that was used to install the application server.

1. Log in as the user that was used to install the application server.
2. Start the migration utility from the installation directory of the latest version of the agent.

   Run the command dc_home/bin/migrate.sh

   Run the command dc_home\bin\migrate.bat

3. The utility displays the IP addresses of all network cards that are found on the local computer system.
   Enter the number that corresponds to the IP address to use.
4. The utility discovers all servers configured by older maintenance levels of the data collector and lists them. The data collectors are grouped by maintenance level.
   Select one or more application server instances from the list.

   The list might include both traditional WebSphere server instances and Liberty servers. Traditional WebSphere server instances might be under different profiles.

   Tip:

   • If several instances under one profile are monitored, you must select them all for migrating at the same time.
   • Migrate all servers under the liberty profile at the same time. Partially migrating configured servers might cause instability.

   Remember:

   • For a stand-alone environment, application server instances must be running.
   • For a Network Deployment environment, the node agent and deployment manager must be running.
   • Liberty servers are not required to be running during the migration.
5. Enter the number that corresponds to the application server instance whose data collector is to be migrated or enter an asterisk (*) to migrate the data collector of all application server instances.

   To specify a subset of servers, enter the numbers, separated by commas, that represents the servers. For example: 1,2,3.

   The migration utility automatically integrates each data collector with the monitoring agent. The monitoring agent host and port values are retrieved from the existing configuration files.

6. Enter an alias for each of the selected servers.
   The default value is the existing server alias.
7. For the Liberty server instance, enter the JVM home directory when prompted. For example, /opt/IBM/java.
8. The utility determines whether WebSphere global security is enabled for each of the profiles where data collection is being migrated.
   If WebSphere Global Security is enabled for one or more profiles, specify whether to retrieve security settings from a client properties file:
   The data collector communicates with the WebSphere Administrative Services using the RMI or the SOAP protocol. If global security is enabled for a profile, you must specify the user ID and password of a user who is authorized to log in to the IBM® WebSphere Application Server administrative console for the profile.

   Alternatively, you can encrypt the user name and password and store them in the application server client properties files before configuring the data collector. You must use the sas.client.props file for an RMI connection, or the soap.client.props file for an SOA connection.

9. Enter 1 to allow the utility to retrieve the user name and password from the appropriate client properties file and skip to step 11. Otherwise, enter 2 to enter the user name and password.
   Important: It may take some time to log in to the WebSphere Application Server administrative console.
10. Enter the user name and password for each profile whether WebSphere Global Security is enabled.
11. The utility migrates data collection for each selected application server instance. It displays a status message that indicates whether the migration of each server completed successfully.
12. Restart the instances as directed by the utility. The data collector configuration takes effect when the application server instances are restarted.