Prepare to migrate composite applications

 

+

Search Tips   |   Advanced Search

 

Prior to running the migration tasks for composite applications complete the prerequisite tasks. Whether you migrate composite applications as part of the core portal migration or independently, the prerequisite tasks will ensure successful migration of composite application artifacts and data. Understand the following restrictions before you migrate composite applications:

PK67050 will be available soon as a recommended fix. This interim fix will allow you to migrate composite applications regardless of whether they are enabled for backup. It will also allow you to migrate applications that contain business components that do not support backup. PK67050 will remove the prerequisite that composite applications be enabled for backup before the migration tasks are run.

 

Prerequisites procedure

  1. On the WebSphere Portal V6.1.0.3 server, make sure that all composite applications can be enabled for backup:

    If you apply interim fix PK67050 when it becomes available, you can skip this step.

    1. Activate the display of the application property Application Backup for Archiving and Restore for all applications running on the portal server by editing...

      portal_server_root/shared/app/ai.xml.impl.service.jar/backup.properties

      ...as follows... 

      # block the backup of any application all.backup.block=false

    2. Activate the display of the application property Application Backup for Archiving and Restore for workflow-enabled applications running on the portal server by editing....

      portal_server_root/shared/app/ai.xml.impl.service.jar/wf.backup.properties

      ...as follows: 

      # block the backup of workflow applications wf.backup.block=false

      Although WebSphere Portal V6.1 no longer supports workflow for composite applications, you should edit the wf.backup.properties file to ensure that workflow-enabled composite applications are migrated for reuse in your upgraded portal deployment as non-workflow applications.

    3. From the page menu of each application, click Edit Application Properties.

    4. Verify that the property Application Backup for Archiving and Restore is set to Enable Backup.

  2. On the WebSphere Portal V6.1.0.3 server, enable scripting for composite applications:

    1. Create....

      portal_server_root/shared/aservices/ScriptingService.properties

      ... and add the following line:

      ServerExt.applications=com.ibm.wps.scripting.server.ApplicationServerExtensions

    2. In...

      WP_PROFILEcells/cell/nodes/node/libraries.xml

      ...add the following lines: 

      <classPath>${WPS_HOME}/shared/app/scripting/ai.xml.api.script.jar</classPath>
<classPath>${WPS_HOME}/shared/app/scripting/ai.xml.impl.script.jar</classPath>
<libraries:Library .... name="WPSlib">

      Specify WPSlib as the name of the library: 

      <libraries:Library xmi:id="Library_library_identifier" name="WPSlib">
    <classPath>${WPS_HOME}/shared/app</classPath>
    <classPath>${WPS_HOME}/shared/app/scripting/wp.link.jar</classPath>
  </libraries:Library>

    3. Path of the scripts:

      Windows: In....

      portal_server_root\bin\wpscript.bat

      ...add the line: 

       set SCRPATH=%SCRIBS%\scripting\ai.xml.api.script.jar;%SCRIBS%\scripting\ai.xml.impl.script.jar;

      UNIX: In....

      portal_server_root/bin/wpscript.sh

      ...add the line: 

       set SCRPATH=$SCRIBS/scripting/ai.xml.api.script.jar:$SCRIBS/scripting/ai.xml.impl.script.jar

  3. On the WebSphere Portal V6.1.0.3 server, check the settings in....

    portal_server_root

    1. Verify the passwords are set for WasPassword and PortalAdminPwd.

    2. Find the SOAP port number. You will need to know the SOAP port number for Step 5b.

  4. Restart the WebSphere Portal V6.1.0.3 server.

  5. At least once before you migrate composite applications, run the wsadmin tool with the option to establish a SOAP connection from the WebSphere Portal V6.1 server to the WebSphere Portal V6.1.0.3 server. The IBM WAS administration scripting tool must work and a SOAP connection must be established between the portal servers to update SSL trust store because the migration task migrate-ai-export uses the Portal Scripting Interface commands for the backing up and restoring composite applications. The Portal Scripting Interface is based on the wsadmin tool.

    1. On the WebSphere Portal V6.1 server, open a command prompt and change to the directory AppServer_root/bin/.

    2. Type the following command:

      wsadmin -host portalversion6013_hostname -conntype SOAP -port portalversion6013_SOAPport_number -user was_userid -password was_password

    3. Review the SSL Signer Exchange Prompt information that is displayed in the console and verify that the digest value matches what is displayed at the server:

      • Subject DN
      • Issuer DN
      • Serial Number
      • Expires
      • SHA-1 Digest
      • MD5 Digest

    4. At the prompt Add signer to the trust store now? type Y.

      Confirmation is displayed as Connected to process WebSphere Portal on node portalversion6013_host_node using SOAP connector.

    5. After you receive confirmation that the SOAP connection is established between the portal servers, at the wsadmin prompt type exit.

  6. Before you run either task, portal-pre-upgrade or migrate-ai-export, make sure that the source WebSphere Portal V6.0.1.3 server is running and that....

    portal_server_root

    ...specifies the values for the properties WasPassword and PortalAdminPwd.

  7. Before you run either task, portal-post-upgrade or migrate-ai-import, make sure that the target WebSphere Portal V.1 server is running and that...

    WP_PROFILE/ConfigEngine/properties/wkplc.properties

    ...specifies the values for the properties WasPassword and PortalAdminPwd.

  8. Ensure that all portlet applications that are rendered on the pages of composite applications in the source environment are installed on or migrated to the WebSphere Portal V6.1.x. environment before you migrate the composite applications. If the
    target environment does not already have available the portlets used by the composite applications, the migration of the composite applications will fail.

    • Although the core portal migration tasks automatically migrate portlet applications, as explained in Understanding migration, you will want to verify that all portlet applications needed by migrated composite applications are available.

    • Also refer to the topic Migrating deprecated portlets to confirm whether the composite applications that you intend to migrate contain portlets that are removed in WebSphere Portal V6.1.x. This topic explains how deprecated portlets are handled for transition after migration.

  9. Ensure that you have explicitly transferred the backend data of the business components of composite applications. The migration tasks for composite applications will not migrate the backend data of business components, for example, the contents of a WCM document library.

    • If the business components of an application store data in the WebSphere Portal Community database domain then consider using the XML Configuration Interface to transfer the backend data from the source environment to the target environment. For example, in the case of WCM document libraries, you might want to copy the entire WebSphere Portal V6.0x Java Content Repository (JCR) to the WebSphere Portal V6.1.0 environment or configure the WebSphere Portal V6.1.0 environment to use the v6x JCR.

    • If application business components store data in repositories that are external to the WebSphere Portal configuration, you cannot use the XML Configuration Interface and will need to use another method of explicitly migrating application component data.

Now you are ready to run the migration tasks for composite applications.

 

Parent topic

Migrating composite applications

Previous topic:

Suppressing migration of composite applications

Next topic:

Run migration tasks for composite applications

 

Related concepts

Understanding migration
The XML configuration interface
Migrating deprecated portlets
Migrating Web content

 

Related tasks

Preparing for migration
Use scripts for composite applications
Deploying a template to another server

 

Related information

Wsadmin tool

Recommended fixes and updates for WebSphere Portal and WCM