Preparing to migrate a z/OS stand-alone application server

Preparing to migrate a stand-alone application server node to WebSphere® Application Server Versão 9.0 for z/OS® includes activities related to inventorying your existing configuration as well as generating CNTL and DATA datasets that you will use in the actual migration.

Before you begin

Configurações suportadas Configurações suportadas:

Este artigo trata da migração da configuração de perfil. Para migrar seus aplicativos para a versão mais recente, use o Kit de Ferramentas de Migração do WebSphere Application Server. Para obter mais informações, consulte o Kit de ferramentas de migração no WASdev.

sptcfg

Read Overview of migration, coexistence, and interoperability and Migration considerations.

Migrating a stand-alone application server node is relatively simple because it consists of a single server and a daemon.

Graphic depicting a stand-alone application server node

You might have configured multiple application servers inside a stand-alone application server node. Generally, this configuration is not recommended; but if you have this configuration, the migration utilities will migrate all servers in the node just as it would all the servers in a Network Deployment application server node.

WebSphere Application Server for z/OS Versão 9.0 supplies migration jobs in the target dataset that you allocate when you generate your migration jobs. Use these jobs to perform the actual migration.
  • BBOWMG1B: Sets an XML flag to indicate the transaction logs are to be cleared.
  • BBOWMG2B: Sets the XML flag back to the normal state.
  • BBOMBHFS or BBOMBZFS: Allocates and mounts the file system that will be the target for the migration.
  • BBOWMG3B: Performs the migration.
  • BBOWBPRO: Creates the Websphere Application Server home and default profile.
  • BBOWBPRE: Runs the migration pre-upgrade process.
  • BBOWBPOS: Runs the migration post-upgrade and finish-up (change file permission) processes.
  • BBOMBCP: Copies the generated Job Control Language (JCL) procedures to start the servers to the specified procedure library. If your Versão 9.0 configuration uses different JCL start procedure names, this utility updates the new Versão 9.0 configuration, and substitutes your new JCL names for the names that existed in your previous configuration.

For help, see Troubleshooting migration.

Procedure

  1. Inventory your configurations.

    Print this procedure, and enter the values for your configurations in the appropriate columns of the following tables.

    • WebSphere Application Server for z/OS Versão 7.0 ou posterior configuration general information:
      Table 1. Configuration general information. Enter your values:
      Item Value                                                              
      Cell short name:  
      Cell long name:  
      Sysplex name:  
      Location of original Versão 7.0 ou posterior configuration datasets:  
      WebSphere Application Server Versão 7.0 ou posterior home directory (configuration file system):  
    • WebSphere Application Server for z/OS Versão 7.0 ou posterior stand-alone application server node:
      Table 2. Server node information. Enter your values:
      Item Value                                                              
      Configuration mount point:  
      Configuration file system dataset:  
      Home directory:

      Default: /AppServer

      Your value: ___________________

      WebSphere Application Server SMP/E home:

      Default: /usr/lpp/zWebSphere/V7R0

      Your value: ___________________

      Controller Job Control Language (JCL) start procedure:  
      Servant JCL start procedure:  
      Daemon JCL start procedure:  
    • WebSphere Application Server for z/OS Versão 9.0 installation information:
      Table 3. Installation information. Enter your values:
      Item Value                                                              
      Product dataset HLQ:  
      Product directory (installation location of Versão 9.0):  
      WebSphere Application Server Versão 9.0 in LPA/LNKLST?:

      __ No

      __ Yes

  2. Produce migration CNTL and DATA datasets for the node.

    You must provide a set of CNTL and DATA datasets for the migration utilities to read in order to perform the migration. Generate a set of customized jobs for the node in your configuration that you want to migrate.

    Graphic depicting a set of CNTL and DATA datasets.

    Some important points about these steps:

    The purpose of creating these customized CNTL and DATA datasets is to give the migration utilities access to key information about your new Versão 9.0 configuration as well as access to shell scripts customized with this new information. The migration utilities get the bulk of the configuration information from your existing Versão 7.0 ou posterior configuration file system.


Ícone que indica o tipo de tópico Tópico de Tarefa



Ícone de registro de data e hora Última atualização: June 20, 2016 0:09
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-zos&topic=tmig_z_prepsas
Nome do arquivo: tmig_z_prepsas.html