Maintenance Pack Installation Instructions. Vendavo 8.2 on NetWeaver

Transcription

1 Maintenance Pack Installation Instructions Vendavo 8.2 on NetWeaver

2 Vendavo 8.2 on NetWeaver Release: 8.2 Document Revision: 1 Publication Date: December 2015 If you have questions or comments about Vendavo documentation, do not hesitate to contact us at VendavoDoc@vendavo.com. Also visit the Vendavo documentation portal at Copyright Copyright Vendavo, Inc. All rights reserved. Confidential This document is proprietary and contains confidential information of Vendavo. You may not use, disseminate or distribute this document, or any portion of it, to any third party, in any manner whatsoever, except as may be set forth in a non-disclosure agreement between your employer and Vendavo. Document Reproduction You may not reproduce this document, or any portion of it, in any manner whatsoever (including by photocopy, magnetic, digital, electronic media, or otherwise) without the prior written agreement of Vendavo, Inc. Trademarks The following terms are trademarks of Vendavo, Inc.: Vendavo, Vendavo ProfitVision, Vendavo Price Manager, Vendavo Deal Manager, Vendavo Profit Analyzer, Whole Price Management, Vendavo Price Engine, Vendavo Price Explorer, Vendavo Portfolio Manager, Vendavo Price List Manager, Vendavo Policy Manager, Vendavo Pricemart Server, Vendavo 8 Accelerate, and Vendavo 8. SAP NetWeaver is a registered trademark of SAP AG in Germany and in several other countries. IBM and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. All other trademarks are the property of their respective owners.

3 3 This document describes the steps necessary to apply a Vendavo maintenance pack on the NetWeaver platform. This is an incremental maintenance pack installation where the Vendavo database schema is retained. The steps below assume that the current Vendavo instance has been up and running and already working with a world implementation. The maintenance pack keeps the world implementation in place. Every world implementation build may require a modified procedure, but the generic approach is: Requirements Backup Upgrade Additional Steps Note that CONFIG_BASE environment variable is set to "demo" and OS is Windows. Requirements First, verify in Supported Platforms Guide whether the requirements for the given maintenance pack remained the same. Backup Second, perform backups: Undeploy the Vendavo application: v nw-undeploy-sca Stop the NetWeaver server. Back up the Vendavo Oracle schema. Back up the entire <VENDAVO_HOME> folder. Upgrade Third, follow these steps on the NetWeaver application server machine. Upgrade in Standalone Environment 1. Make sure the NetWeaver server is stopped: v nw-server-status 2. Unzip the Vendavo maintenance pack software distribution.zip format to a folder called <NEW_VENDAVO_HOME>, for example. 3. Copy the config.properties and config-<host>.properties from <VENDAVO_HOME>/config/users /demo/ to the same location under the new folder <NEW_VENDAVO_HOME>. 4. Copy the <VENDAVO_HOME>/meta/<World> to <NEW_VENDAVO_HOME>/meta/<World>.

4 4 5. (Optionally) If you have LDAP setup, copy the old web-j2ee-engine.xml file in <VENDAVO_HOME> to <NEW_VENDAVO_HOME>. 6. Rename <NEW_VENDAVO_HOME> to <VENDAVO_HOME> and continue in this folder. 7. Build the Vendavo application: Running this command re-creates the <appserver_home> and <vendavo_home>\web\app\web- INF directories. Any changes made in the files directly in these folders will be overwritten. 8. Generate SQL files to create or update the database based on OMI definitions: v pso-create-sql 9. Update the database schema with delta differences. (This executes the updated SQL created by pso-create-sql.) v pso-update-schema 10. Package the EAR in the SCA format: 11. Start the NetWeaver server. 12. Deploy the Vendavo application: 13. Please allow some time for Pricemart to load, the time may vary depending on the amount of data loaded. To check Pricemart status, use this command: v pricemart status 14. Log in Vendavo and test if all components in Vendavo work. To ensure the updated JavaScript file (delivered with the maintenance pack) is used, advise all the individual Vendavo users to clear the cache in their browser. Upgrade in Clustered Environment Undeploy old Vendavo. To do so, start the NetWeaver instances in this order: a. Remote Pricemart b. Node 1 or Node 2 of Vendavo cluster c. Web Dispatcher. On the server with Node 1 of Vendavo cluster run in the vendavo folder: v nw-undeploy On the server with Remote Pricemart run in the remotepa\vendavo folder, run in the commandline: set CONFIG_BASE=<folder with the.properties files>v nw-undeploy Stop the NetWeaver instances in this order: a. Web Dispatcher b. Node 1 or Node 2 of Vendavo cluster c. Remote Pricemart Copy the config.properties and config-<host>.properties from <VENDAVO_HOME>/config/users /demo/ to the same location under the new folder <NEW_VENDAVO_HOME> for all server nodes. Copy the <VENDAVO_HOME>/meta/<World> to <NEW_VENDAVO_HOME>/meta/<World>.

5 On the server with Remote Pricemart: a. Run the following sequence of commands: set CONFIG_BASE=<folder with the.properties files> (If localization is supported) v pso-create-sql v pso-update-schema b. Start the Remote Pricemart instance in the NetWeaver console. c. Run: On the server with Node 1 of Vendavo cluster: a. b. c. Run the following sequence of commands: (If localization is supported) Start Node 1 in the NetWeaver console. Run: On the server with Node 2 of Vendavo cluster (which may be the same server as with Remote Pricemart): a. b. Stop Node 2 in the NetWeaver console. Run the following sequence of commands: set CONFIG_BASE=<folder with the.properties files> (If localization is supported) c. Start Node 2 in SAP NetWeaver console On the server with Node 1 of Vendavo cluster: a. Start the Web Dispatcher instance in the NetWeaver console. Additional Steps There are also additional upgrade steps related to individual MP versions. These steps need to be resolved manually or with the help of Migration Tool. Their complete list is in the latest release notes.