Migrate managed base application servers

Before you begin

Start the Version 8.5 administrative agent

About this task

Step 8 towards the goal: Migrating an administrative agent profile and its registered set of managed base application servers
Ensure that the Version 8.5 administrative agent is running. For each managed base application server that you plan to migrate to Version 8.5, perform the following steps:
Avoid trouble Avoid trouble: For the migration to be successful:
  • Managed base application servers must be located on the same machine as the associated administrative agent.
  • The node names must be the same on the Version 8.5 and previous releases.
gotcha

Procedure

  1. Create the target base application server profile. Run the manageprofiles command with the appropriate parameters to create a new managed profile. For example:
    [IBM i]
    /QIBM/ProdData/WebSphere/AppServer/V85/ND/bin/manageprofiles -create -profileName 
    AppSrv01 -templatePath /QIBM/ProdData/WebSphere/AppServer/V85/ND/profileTemplates/default 
    -nodeName AppSrv01Node01 -cellName AppSrv01Cell01 -hostName mynode1host.company.com
  2. Run the WASPreUpgrade command to save the current managed base application server information to a migration backup directory. Choose a new directory for the backup files. For example:
    [IBM i]
    /QIBM/ProdData/WebSphere/AppServer/V85/ND/bin/WASPreUpgrade /mybackup/
    WAS70Appserver01backup /QIBM/UserData/WebSphere/AppServer/V70/ND/profiles/AppSrv01

  3. Run the WASPostUpgrade command to restore the saved managed application server profile configuration into the new Version 8.5 base application server profile.
    Avoid trouble Avoid trouble: This command requires additional parameters and the following example assumes that security is enabled on both administrative agents.gotcha
    For example:
    [IBM i]
    /QIBM/ProdData/WebSphere/AppServer/V85/ND/bin/WASPostUpgrade 
    /mybackup/WAS70Appserver01backup -profileName AppSrv01 
    -oldAdminAgentProfilePath /QIBM/UserData/WebSphere/AppServer
    /V70/ND/profiles/AdminAgent01 -oldAdminAgentHostname myhostname 
    -oldAdminAgentSoapPort 8879 -oldAdminAgentUsername myusername 
    -oldAdminAgentPassword mypassword -newAdminAgentProfilePath 
    /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/AdminAgent01 
    -newAdminAgentHostname myhostname -newAdminAgentSoapPort 8887
    -newAdminAgentUsername myusername1 -newAdminAgentPassword mypassword1

  4. Start the migrated Version 8.5 managed application server.
  5. Check the Version 8.5 managed application server SystemOut.log file for warnings or errors.
    Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.
Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 11:33 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=tmig_migrate_admin_agent_step8
File name: tmig_migrate_admin_agent_step8.html