Prepare to migrate composite applications

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:

Complete the following prerequisites before you migrate composite applications:

  1. On the source WebSphere Portal server, enable scripting for composite applications:

    1. Create the file $PORTAL_HOME/shared/app/config/services/ScriptingService.properties and add the following line:

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

    2. In the file WP_PROFILE/config/cells/cell/nodes/node/libraries.xml, locate the stanza for WPSlib. It should look like the following: 

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

        Change it to look as follows: 

        <libraries:Library xmi:id="Library_1218796172015" name="WPSlib">
 <classPath>${WPS_HOME}/shared/app</classPath>
 <classPath>${WPS_HOME}/shared/app/scripting/wp.link.jar</classPath>
 <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>

    3. Specify the path of the scripts:

        Windows: In the file $PORTAL_HOME/bin/wpscript.bat, add the line: 

        set SCRPATH=%SCRIBS%/scripting/wp.script.jar;%SCRIBS%/scripting/wp.link.jar;
%SCRIBS%/wp.base.jar; %SCRIBS%/wp.model.api.jar;
%SCRIBS%/wp.user.api.jar;%SCRIBS%/wp.cmd.base.jar;%

        UNIX: In the file $PORTAL_HOME/bin/wpscript.sh, add the line: 

        set SCRPATH=%SCRIBS%/scripting/wp.script.jar;%SCRIBS%/scripting/wp.link.jar;
%SCRIBS%/wp.base.jar; %SCRIBS%/wp.model.api.jar;
%SCRIBS%/wp.user.api.jar;%SCRIBS%/wp.cmd.base.jar;%

  2. On the source WebSphere Portal server, check the settings in the file $PORTAL_HOME/config/wpconfig.properties:

    1. Make sure that the passwords are set for WasPassword and PortalAdminPwd.

      If the WasUserid is different from the PortalAdminId, add the WasUserid to the portal administrator group wpsadmins. An interim fix will be available soon to correct a problem with Portal Login to the scripts that support the composite application migration tasks. Until the interim fix is available, if you do not add WasUserid to the portal administrator group wpsadmins, the migration tasks for composite applications will not work properly.

    2. Find the SOAP port number.

  3. Restart the source WebSphere Portal server.

  4. At least once before you migrate composite applications, run the wsadmin tool with the option to establish a SOAP connection from the new, target WebSphere Portal server to the source WebSphere Portal server.

      The IBM WebSphere Application Server 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 new WebSphere Portal server, open a command prompt and cd WAS_HOME/bin/.

      2. Type the following command:

          wsadmin -host portalversion6014_hostname -conntype SOAP -port portalversion6014_SOAPport_number -user was_userid -password was_password The wsadmin tool might display a warning about a version mismatch between the two servers. This warning does not affect the operation of the tool and can be disregarded.

      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 portalversion6014_host_node_name using SOAP connector.

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

  5. Before you run either task, portal-pre-upgrade or migrate-ai-export, verify the source WebSphere Portal server is running and that the file $PORTAL_HOME/config/wpconfig.properties specifies the values for the properties WasPassword and PortalAdminPwd.

  6. Before you run either task, portal-post-upgrade or migrate-ai-import, verify the target WebSphere Portal v7.0 server is running and that the file WP_PROFILE/ConfigEngine/properties/wkplc.properties specifies the values for the properties WasPassword and PortalAdminPwd.

  7. 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 new WebSphere Portal 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 Understand migration, you will want to verify that all portlet applications needed by migrated composite applications are available.

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

  8. 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 Web Content Manager 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 Web Content Manager document libraries, you might want to copy the entire WebSphere Portal v6.0x Java™ Content Repository (JCR) to the WebSphere Portal v7.0 environment or configure the WebSphere Portal v7.0 environment to use the v6.0x 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

Migrate composite applications


Next topic

Suppressing migration of composite applications
Understand migration
The XML configuration interface
Migrate deprecated portlets


Related tasks


Prepare for migration from v6.0.1.x
Use scripts for composite applications
Deploy a template to another server
Running migration tasks for composite applications

Wsadmin tool

Recommended fixes and updates for WebSphere Portal and Web Content Management

 


+

Search Tips   |   Advanced Search