Page tree
Skip to end of metadata
Go to start of metadata

The migration of Configurations between different application servers can be referred to as horizontal. 
Currently, you can migrate Configurations between WebSphere (full profile) and WebSphere Liberty Profile. The migration is supported for the following versions:

  • WebSphere (full profile) version 8.5 to WebSphere Liberty Profile version 8.5
  • WebSphere Liberty Profile version 8.5 to WebSphere (full profile) version 8.5 

The following use cases document the possible horizontal migration types: 

Migrate a sample application that uses the WebSphere Liberty Profile database to WebSphere (full profile)

  1. Start WebSphere Liberty Profile.
  2. Ensure that the application that you want to migrate is started on the WebSphere Liberty Profile.
  3. Start BMC MIddleware Automation version 8.6.
  4. Create a Snapshot of the current Liberty Profile Configuration.
  5. Right-click the created Snapshot and select Migrate Configuration.
  6. In the Migrate Configuration dialog, click the ‘…’ button next to Source Server Profile to select the WebSphere Liberty Profile server profile.
  7. Select WebSphere Application Server version 8.5 from the Target Application Server list.
  8. Select the Migrate Liberty Applications check box, and click Next.
  9. Select an output folder for the migrated configuration, and click Next.
  10. Review the migration summary, and click Finish.
  11. Start the WebSphere Application Server Full Profile instance.
  12. Ensure that at least one server exists on WebSphere (full profile) 8.5 (for example, server1). 
    In case there is no server available, follow one of the following options to create a server:
    • Install BMC Middleware Automation Configuration (for example, Configurations\WAS.855\create_server1.xml) for server creation on WebSphere 8.5 Server Profile.
    • Open the WebSphere administration console in the browser, and then create a server:
      Menu: Servers > All Servers > New

    Note

    Ensure that for this server the WC_defaulthost port value (Servers > All servers > server1 > Ports) exists under Environment > Virtual hosts > default_host > Host Aliases. If such a server value does not exists, add it.

  13. Install the migrated Configuration using the token set, by using one of the following instructions:
    1. Replace the following tokens by their possible values:

       

      TokenValue
      CELLlocalhost -Dmgr01cell01
      CarSale_war_ContextRootCarSale
      NODElocalhost-AppSrv01
      SERVERserver1
      webModule_VirtualHostdefault_host
      jDBCProvider_Classification_1APPLICATION_SERVER2
      jDBCProvider_Target_1server1
      UserDefined_JDBC_DRIVER_PATHC:\IBM\855\WebSphere\AppServer\postgreDriver
    2. Use the predefined token set in the WebSphere (full profile) 8.5 server profile.
  14. Open the browser and navigate to the WebSphere administration console. Go to Servers > All servers, and start the server on which you installed the application (for example, server1 in this case).
  15. Start the application in WebSphere administration console: Applications > All applications, select the check box next to your application name, and then click Submit Action.
  16. Open the browser, and ensure that the application is installed and started.

    Note

     Ensure that you use the target server port WC_defaulthost value in the application URL.

Back to top

Migrate a sample application that uses the WebSphere (full profile) database to WebSphere Liberty Profile

  1. Start WebSphere 8.5 (full profile).
  2. Ensure that the application that you want to migrate is started on WebSphere (full profile).
  3. Use the WebSphere 8.5 (full profile) server profile to create a Snapshot of the current server Configuration.
  4. Right-click the created Snapshot, and select Migrate Configuration.
  5. In the Migrate Configuration dialog, click the ‘…’ button next to Source Server Profile to select the WebSphere 8.5 (full profile) server profile.
  6. From the Target Application Server list, select WebSphere Liberty Profile 8.5, and click Next.
  7. Select an output folder for the migrated configuration, and click Next.
  8. Select the Server(s) migration migration mode, and click Next.
  9. Select server1, and then click Next.
  10. Select your .war file, and click Next.
  11. Review the migration summary, and click Finish.
  12. Start the WebSphere Liberty Profile instance.
  13. Install the migrated configuration on WebSphere Liberty Profile either by setting the values for the token set, or by using the predefined one:
    1. Set the values for the tokens: 

      TokenValue
      UserDefined_Application_LOCATION${server.config.dir}/apps
      UserDefined_Application_SOURCEPATHC:\Users\Administrator\BladeLogic\AppRelease\workspace\Release\horizontalMigrationApps
    2. Use the predefined token set.
  14. Open the browser and ensure that the application is installed and started.

Back to top

Migrate from WebSphere Liberty Profile to WebSphere (full profile) a sample application that uses Java Message Service for performing Point to Point and Publish/Subscribe messaging

  1. Ensure that the WebSphere Liberty Profile Java Message Service server instance is running (for example, run the JMSSample.bat file).
  2. Open browser and enter the URL of the application that uses Java Message Service.
  3. Ensure that the message is sent and received successfully, and the Point to Point messaging works.
  4. Enter the URL of the message that you received from the application.
  5. Ensure that the message for non-durable subscriber is received, and the Publish/Subscribe messaging works.
  6. Use the WebSphere Liberty Profile 8.5 Java Message Service server profile to create a Snapshot of the current WebSphere Liberty Profile Configuration.
  7. Right-click the created Snapshot, and select Migrate Configuration.
  8. In the Migrate Configuration dialog, select WebSphere Application Server 8.5 from the Target Application Server list.
  9. Click the ‘…’ button next to Source Server Profile to select the WebSphere Liberty Profile 8.5 server profile.
  10. Select the Migrate Liberty Applications check box, and click Next.
  11. Select an output folder for the migrated configuration, and click Next.
  12. Review the migration summary, and then click Finish.
    If you want to use the predefined token set, go to step 19. If you want to specify values for the tokens manually, follow the next steps.
  13. Right-click the migrated configuration .xml file, and select Pull Tokens from configuration.
  14. Select the WebSphere 8.5 (full profile) server profile and its WLP_JMS empty token set.
  15. Follow the wizard to copy the tokens into the WLP_JMS token set.
  16. Use the WebSphere 8.5 (full profile) server profile and the J2CResourceAdapter snapshot filter to create a Snapshot of the available Java Message Service providers in WebSphere (full profile).
  17. Open the Token Editor by selecting Actions > Open Token Editor, and navigate to the WebSphere 8.5 (full profile) server profile and its WLP_JMS token set.
  18. Fill in the values for all the tokens by switching between the Snapshot from step 16, and the Token Editor:
    • All the MapResEnvRefToRes and MapResRefToEJB token names can have the same value as the value of the referenceBinding attributes for respective application deployment tasks in the migrated Configuration.
    • The j2CActivationSpec_jndiName and BindJndiForEJBMessageBinding JNDI token names must have the same value.
    • The j2CResourceAdapter_name and j2CActivationSpec_activationSpecClass token values should be taken from the WebSphere (full profile) Configuration taken in step 16.
    • Other *name* tokens can have arbitrary values.
    • Below is the sample list of tokens and their values:
    TokenValue
    CELLWIN-967B8KGWE6D-Dmgr01cell01
    JMSApp_war_ContextRootJMSApp

    JMSSample_MapResEnvRefToRes_1_JNDI

    jndi_INPUT_Q

    JMSSample_MapResEnvRefToRes_2_JNDI

    jndi/MDBQ

    JMSSample_MapResEnvRefToRes_3_JNDI

    jndi/MDBREPLYQ

    JMSSample_MapResEnvRefToRes_4_JNDI

    jmsTopic

    JMSSample_MapResRefToEJB_1_JNDI

    jndi_JMS_BASE_QCF

    JMSSample_MapResRefToEJB_2_JNDI

    jmsTCF
    NODE

    WIN-967B8KGWE6D-AppSrv01

    NODE_Classification

    APPLICATION_SERVER2

    SERVERserver1

    j2CResourceAdapter_Classification_1

    APPLICATION_SERVER2

    j2CResourceAdapter_Target_1

    Node

    j2CResourceAdapter_name_1

    SIB JMS Resource Adapter

    j2CActivationSpec_activationSpecClass_1

    com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl

    com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl

    jndi/ActivSpec1

    j2CActivationSpec_name_1

    wlpActivSpec1

    j2CConnectionFactory_name_1

    connectionFactory1

    j2CConnectionFactory_name_2

    connectionFactory2

    unknown_BindJndiForEJBMessageBinding_JNDI

    jndi/ActivSpec1

    webModule_VirtualHost

    default_host

  19. Install the migrated configuration using the WLP_JMS token set (or WLP_JMS_PREDEF, if you skipped the previous steps) onto the WebSphere 8.5 (full profile) server profile.
  20. Open the browser, and navigate to the WebSphere administration console.
  21. Log into the administration console of WebSphere 8.5 (full profile), go to Servers > All servers, and start the server to which you installed the Java Message Service application (server1, in this case).
  22. Open the browser, navigate to the URL of the application that uses Java Message Service, and then to the URL of the message sent by the application. Ensure that messaging is working as on WebSphere Liberty Profile.

    Note

    Port number must be equal to the WC_defaulthost value of the target server, where the Java Message Service application is installed.

Back to top

Migrate the application that uses Java Message Service from WebSphere (full profile) to WebSphere Liberty Profile

  1. Create a full Snapshot of the WebSphere 8.5 (full profile).
  2. Migrate the source Snapshot to WebSphere Liberty Profile version 8.5 using the Migration Wizard:
    1. Right-click the Configuration, and select Migrate Configuration.
    2. Select WebSphere Liberty Profile 8.5 from the Target Application Server list, and click Next.
    3. Select an output folder for the migrated configuration, and click Next.
    4. On the Migration Mode selection screen, select Node(s) migration.
    5. Select nodes from the list that you want to migrate. 
    6. Select your source server from which you want to migrate.
    7. Select the .war file with the application that you want to migrate, and click Next.
    8. Review the migration summary, and click Finish.
  3. In the Design View of the newly created Configuration, remove all the jdbcDriver, dataSource, library and fileset elements as they are not used by the application.
    Alternatively, you can create a Configuration package and exclude those elements.
  4. Start a new instance of the blank WebSphere Liberty Profile server (for example, run the .bat file).

  5. Install the migrated configuration on the WebSphere Liberty Profile either by setting the values for the token set, or using the predefined one:

    1.  Set the values for tokens: 

      TokenValue
      UserDefined_Application_LOCATION${server.config.dir}/apps
      UserDefined_Application_SOURCEPATHC:\Users\Administrator\BladeLogic\AppRelease\workspace\Release\horizontalMigrationApps


    2. Use the predefined token set:

  6. Open the browser, navigate to the URL of the application that uses Java Message Service, and then to the URL of the message sent by the application to verify application operability.

    Note

    In case there is an issue with the application operability, check whether the port values are correct and there are no port conflicts. You may also need to restart the WebSphere Liberty Profile server using the .bat files.

Back to top

Related topic

Migrating and cloning Configurations between different WebSphere versions

Migration of Configurations

  • No labels