Migration - V6.2 to V6.3

Transcription

1 2012 by Pegasystems, Inc. All rights reserved.

2 2012 by Pegasystems, Inc. All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary information. The document and product are protected by copyright and distributed under licenses restricting their use, copying distribution, or transmittal in any form without prior written authorization of Pegasystems Inc. This document is current as of the date of publication only. Changes in the document may be made from time to time at the discretion of Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request. This document does not imply any commitment to offer or deliver the products or services described. This document may include references to Pegasystems product features that have not been licensed by your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems service consultant. Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors. This document or Help System could contain technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Pegasystems Inc. may make improvements and/or changes in the information described herein at any time. This document is the property of Pegasystems Inc. Publishing Date: August 27, 2012 Contact Product Support Visit the Pega Developer Network 2012 by Pegasystems, Inc. All rights reserved.

3 Migration Overview 2 Database 3 Application Server 4 Upgrade Steps 4 Deployable Archives 4 GridGain Node 5 PRPC Applications by Pegasystems, Inc. All rights reserved. 1

4 Migration Overview This document describes how to migrate your Decision Management service layer from V6.2 to V6.3. The process of migrating the Decision Management service layer consists of the steps listed below. 1. Locate your PRPC distribution image. You will need the resources, and deployable archives contained in this folder. 2. Perform database migration steps (page 3). 3. Perform application server migration steps (page 4). 4. If applicable, perform GridGain node migration steps (page 5). 5. Update PRPC applications (page 6) by Pegasystems, Inc. All rights reserved. 2

5 Database It is recommended to perform a backup of the database before proceeding with the database migration steps. Follow the steps described below to migrate your IS and VBD schemas from V6.2 to V6.3 (ADM does not require database migration). In the steps below, you should read <database> as a placeholder value for oracle (Oracle), or db2 (IBM DB2). Connect to the database as the IS user, and run the migration_62_to_63.ddl script located in Additional_Products/DSM/Products/Interaction Services/<database>/schema. Connect to the database as the VBD user, and run the migration_62_to_63.ddl script located in Additional_Products/DSM/Products/Visual Business Director/server/<database>/schema by Pegasystems, Inc. All rights reserved. 3

6 Application Server Upgrade steps (page 4) Deployable archives (page 4) Upgrade Steps Using the tools and methods available to you through your application server: 1. Replace the DSM V6.2 EAR files with the applicable V6.3 deployable archives (page 4). 2. Redeploy applications. Deployable Archives The is_long and ads_long deployable archives (is.war or is-web.ear, and adm.war or adm.ear) are located in the Additional_Products/DSM/Products/<application>/<database>/archives folders. The vbd_long deployable archives (vbd.war or vbd.ear) are located in the Additional_Products/DSM/ Products/Visual Business Director/server/<database>/archives. <application> stands for Interaction Services, or Adaptive Decision Manager. <database> stands for oracle, or db2. EAR archives are provided for application servers (WebSphere, and WebLogic), WAR archives for Tomcat by Pegasystems, Inc. All rights reserved. 4

7 GridGain Node Follow the steps described below to upgrade your GridGain node(s). 1. Stop the existing node. 2. Locate the vbd-gg-node folder in Additional_Products/DSM/Products/Visual Business Director. 3. Use the contents of this folder to update your existing node, making sure that you apply the existing configuration in the new files: If applicable, reflect the GridGain home. Reflect the connection to the VBD schema. Make sure the database driver is at the expected location. If additional configuration was applied for running multiple nodes, make sure you reflect it. 4. Repeat the same steps for all other applicable nodes. 5. Restart the node(s) by Pegasystems, Inc. All rights reserved. 5

8 PRPC Applications 1. If you defined PegaDM as Built on Application in the application rule: a. Update the built on version of PegaDM to b. Update the required rule sets for Pega-DecisionArchitect to If you did not define PegaDM as Built on Application, and instead added the Pega-DecisionArchitect and Pega-DecisionEngine rule sets in the Application RuleSets section of your application rule, update the Pega-DecisionArchitect and Pega-DecisionEngine rule set versions to by Pegasystems, Inc. All rights reserved. 6