Oracle Retail Server Installation Guide Release September 2007

Transcription

1 Oracle Retail Server Installation Guide Release September 2007

2 Oracle Retail Server Installation Guide, Release Copyright 2007, Oracle. All rights reserved. Primary Author: Paul Kehler The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR , Commercial Computer Software Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, thirdparty Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

3 Value-Added Reseller (VAR) Language (i) the software component known as ACUMATE developed and licensed by Lucent Technologies Inc. of Murray Hill, New Jersey, to Oracle and imbedded in the Oracle Retail Predictive Application Server Enterprise Engine, Oracle Retail Category Management, Oracle Retail Item Planning, Oracle Retail Merchandise Financial Planning, Oracle Retail Advanced Inventory Planning and Oracle Retail Demand Forecasting applications. (ii) the MicroStrategy Components developed and licensed by MicroStrategy Services Corporation (MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle Retail Data Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications. (iii) the SeeBeyond component developed and licensed by Sun MicroSystems, Inc. (Sun) of Santa Clara, California, to Oracle and imbedded in the Oracle Retail Integration Bus application. (iv) the Wavelink component developed and licensed by Wavelink Corporation (Wavelink) of Kirkland, Washington, to Oracle and imbedded in Oracle Retail Store Inventory Management. (v) the software component known as Crystal Enterprise Professional and/or Crystal Reports Professional licensed by Business Objects Software Limited ( Business Objects ) and imbedded in Oracle Retail Store Inventory Management. (vi) the software component known as Access Via licensed by Access Via of Seattle, Washington, and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags. (vii) the software component known as Adobe Flex licensed by Adobe Systems Incorporated of San Jose, California, and imbedded in Oracle Retail Promotion Planning & Optimization application. (viii) the software component known as Style Report developed and licensed by InetSoft Technology Corp. of Piscataway, New Jersey, to Oracle and imbedded in the Oracle Retail Value Chain Collaboration application. (ix) the software component known as i-net Crystal-Clear developed and licensed by I-NET Software Inc. of Berlin, Germany, to Oracle and imbedded in the Oracle Retail Central Office and Oracle Retail Back Office applications. (x) the software component known as WebLogic developed and licensed by BEA Systems, Inc. of San Jose, California, to Oracle and imbedded in the Oracle Retail Value Chain Collaboration application. (xi) the software component known as DataBeacon developed and licensed by Cognos Incorporated of Ottawa, Ontario, Canada, to Oracle and imbedded in the Oracle Retail Value Chain Collaboration application. iii

4

5 Contents Preface... vii Audience... vii Related Documents... vii Customer Support... vii Review Patch Documentation... vii Oracle Retail Documentation on the Oracle Technology Network... vii Conventions...viii 1 Hardware and Software Requirements... 1 Database Server...1 Application Server...1 FTP Server...2 Application Server...2 Web Browser and Client Requirements...2 Requirements for PC Systems...2 Requirements for Macintosh Systems Database Server Installation Instructions... 5 Getting Started with Oracle...5 Create a UNIX User Account for Oracle...5 Modify the init.ora File in the $ORACLE_HOME/dbs Directory...5 Verify the Existence of Oracle Packages...5 Create ORACLE Tablespaces...5 Create RRS Schema Owner in Oracle Instance FTP Server Instructions Application Server Installation Instructions... 9 UNIX (Sun/Solaris/HPUX/AIX)...9 Deploy RRS War File in WebSphere Application Server Configure the RRS Online Application Installing a Patch (or New Release) to Retail Server in Websphere Overview...15 Steps to Uninstall and Reinstall the Retail Server (Design/Webtrack) war File...15 v

6

7 Preface Oracle Retail Installation Guides contain the requirements and procedures that are necessary for the retailer to install Oracle Retail products. Audience This Installation Guide is written for the following audiences: Database administrators (DBA) System analysts and designers Integrators and implementation staff Related Documents Customer Support For more information, see the following documents in the Oracle Retail Server Release documentation set: Oracle Retail WebTrack Release Notes Oracle Retail Design Release Notes When contacting Customer Support, please provide the following: Product version and program/module name Functional and technical description of the problem (include business impact) Detailed step-by-step instructions to re-create Exact error message received Screen shots of each step you take Review Patch Documentation For a base release (".0" release, such as 12.0), Oracle Retail strongly recommends that you read all patch documentation before you begin installation procedures. Patch documentation can contain critical information related to the base release, based on new information and code changes that have been made since the base release. Oracle Retail Documentation on the Oracle Technology Network In addition to being packaged with each product release (on the base or patch level), all Oracle Retail documentation is available on the following Web site: Documentation should be available on this Web site within a month after a product release. Note that documentation is always available with the packaged code on the release date. Installation Guide vii

8 Conventions Navigate: This is a navigate statement. It tells you how to get to the start of the procedure and ends with a screen shot of the starting point and the statement the Window Name window opens. Note: This is a note. It is used to call out information that is important, but not necessarily part of the procedure. This is a code sample It is used to display examples of code A hyperlink appears like this. viii Oracle Retail Server

9 Database Server Hardware and Software Requirements Oracle Retail Server is the foundation for the following products: Oracle Retail Design, Oracle Retail Webtrack, and Oracle Retail Integrator. If you are licensed for any combination of these products, you are required to install Oracle Retail Server. Before you install any Oracle Retail Server products, you need to make sure that your information systems can adequately run the software that you are installing, as well as process the amount of data that you expect to manage. This section lists the suggested hardware and software requirements for Oracle Retail Server products. The following are suggested hardware and software requirements: Database Server database software requirements Application Server including operating system software and development tools, and a list of hardware choices. Web Browser including the requirements that a Web browser must meet and a list of Web browsers and versions from which you can choose. Because you need to choose hardware that has sufficient random access memory (RAM) and program and data storage capacity for the products you choose, each section lists criteria you can use to size your hardware selections. The totals you discover after factoring in sizing issues are approximate. General requirements for a database server capable of running Retail Server include: 1 Requirement Operating System Oracle RDBMS Version UNIX based OS (Solaris 9, HP-UX or AIX 5.2) certified with Oracle9i release 2 Enterprise Edition Note: Oracle Retail Server is certified on Solaris 9 only when running Oracle Database 10g with Oracle Application Server Oracle9i Enterprise Edition or Oracle Database 10g Application Server General requirements for an application server capable of running the RRS application include: Requirement Operating System Version UNIX based OS (Solaris 9, HP-UX or AIX 5.2) certified with IBM WebSphere Application Server WebSphere or Oracle Application Server Note: Oracle Application Server requires Oracle Database 10g. Installation Guide 1

10 Hardware and Software Requirements FTP Server Application Server A secure FTP daemon is required for an FTP server capable of running Retail Server. General requirements for an application server capable of running Retail Server include: Requirement UNIX (or UNIX variant) Version N/A IBM WebSphere Application Server CD-ROM drive N/A 1 GB network adapter N/A ~300 MB free disk space for RRS War file and Java source code N/A Web Browser and Client Requirements General requirements and suggestions for client capable of running Oracle Retail Server are listed in following tables. Requirements for PC Systems System Component Minimum Requirements Recommended Configuration Hardware Pentium 233Mhz processor 128Mb RAM Pentium 1.1Ghz processor 512Mb RAM Desktop Resolution 1024 x 768 pixels 1024 x 768 pixels Operating System Windows 2000 Professional, Windows 2000 Server, Windows 2003 Server, Windows XP Home, or Windows XP Professional Windows XP Professional Sun Microsystems Java Virtual Machine J2SE 5.0 (Java 1.5) J2SE 5.0 (Java 1.5) Web Browser Microsoft Internet Explorer 6.0 Microsoft Internet Explorer 6.0 Note: All operating system and other software should be at the latest patch or update level (including service packs) for the listed version. 2 Oracle Retail Server

11 Oracle Retail Server Requirements for Macintosh Systems System Component Minimum Requirements Recommended Configuration Hardware 400 MHz processor 128Mb RAM 800 MHz processor 256Mb RAM Desktop Resolution 1024 x 768 pixels 1024 x 768 pixels Operating System Mac OS X 10.3 (Panther) Mac OS X 10.4 (Tiger) Sun Microsystems Java Virtual Machine (available from Apple) J2SE (Java 1.4.2) J2SE 5.0 (Java 1.5) Web Browser Latest version of Apple Safari Latest version of Apple Safari Note: All operating system and other software should be at the latest patch or update level (including service packs) for the listed version. Installation Guide 3

12

13 Database Server Installation Instructions Getting Started with Oracle Create a UNIX User Account for Oracle 1. Create the following UNIX groups: dba 2. Create the following UNIX user, using ksh as the default shell: Oracle dba group (owns the Oracle RDBMS) Modify the init.ora File in the $ORACLE_HOME/dbs Directory 1. Install Oracle 9i as the Oracle account. 2. Place the following in the init.ora: nls_date_format= DD-MON-RR job_queue_processes=<number of CPUs + 1> open_cursors= Create a 9i database. Verify the Existence of Oracle Packages The DBMS_SESSION, DBMS_RANDOM, DBMS_ALERT, DBMS_PIPE, and DBMS_JOB packages must be created in each database that RRS 12 will be run against. These Oracle packages are provided with the ORACLE software, and are normally created by the catproc.sql script as part of the Oracle installation process. 1. Log into the database and query the USER_OBJECTS view to verify whether or not the packages have been created, and that Oracle user sys owns these packages. Note: The source for these packages are located in the $ORACLE_HOME/rdbms/admin directory. 2. If necessary, re-create the packages by running the catproc.sql script while logged in as the Oracle user sys. Create ORACLE Tablespaces RRS 12 requires that a tablespace be created initially for the RRS installation. 1. Create the tablespace, retek_data. 2. The size of all of this tablespace varies from client to client, depending on how much data the client intends on having in their environment. The recommended size is 4 GB. The system tablespace should have at least 400 MB free for each installation of the RRS 12 schema. 2 Installation Guide 5

14 Database Server Installation Instructions Create RRS Schema Owner in Oracle Instance 1. Create the ORACLE user that corresponds to the RRS environment. This user is referred to as rrsdev12 in the rest of the install guide. Log into SQLPLUS as the user system. Enter the following commands, replacing the text in brackets with the appropriate names: SQL> create user <RRS 12 Schema Owner> identified by <password> default tablespace retek_data temporary tablespace <temporary tablespace name>; 2. The ORACLE user <RRS 12 Schema Owner> serves as the owner of the database objects and should be granted the following permissions. Additional privileges must be granted to the RRS Schema Owner Log in to SQLPLUS as the user system Enter the following commands: SQL> GRANT SELECT_CATALOG_ROLE, ALTER SESSION, ANALYZE ANY, CREATE SEQUENCE, CREATE SESSION, CREATE TABLE, CREATE VIEW, SELECT ANY SEQUENCE, SELECT ANY TABLE TO <RRS 12.0 Schema Owner> / alter user <RRS 12 Schema Owner> quota unlimited on retek_data / 6 Oracle Retail Server

15 3 FTP Server Instructions Create a username on the ftp server. This user is used exclusively by Retail Server to get and put files. This is a private username for Retail Server and is different from the usernames given out to trading partners. This username must have write permissions on all subsequent ftp accounts created for trading partners. Note: This should be a secured ftp daemon. Installation Guide 7

16

17 Application Server Installation Instructions The RRS server tier is packaged as a WAR RetailServer.war. Install the RetailServer.war file in the J2EE application server according to the vendor's documentation. The following are typical steps for deploying a war file in WebSphere assuming WebSphere Application Server (WAS) and IBMHttpServer have already been installed. It is also assumed that Oracle has already been configured and loaded with the appropriate RRS Schema for your installation. UNIX (Sun/Solaris/HPUX/AIX) Notes: JVM 1.4.x is a requirement for RRS. The same war file is used for Design and Webtrack the license.bin file determines which application is turned on. This license is available from Oracle Fulfillment Department. If installing RRS 12.0 in a different J2EE container, the following jar files must also be included by adding them to the jre/lib/ext directory on the JVM (WebSphere has the correct version of the JVM and these jar files already): - activation.jar from JavaBeans Activation Framework at - mail.jar from JavaMail at - jce1_2_2.jar and sunjce_provider.jar from Java Cryptography Extension at These files are bundled with a JVM of version 1.4 and later. 4 Installation Guide 9

18 Application Server Installation Instructions Deploy RRS War File in WebSphere Application Server Log into the UNIX webserver where WebSphere is installed as the retek user and determine where the RetailServer.war file will be installed from. There should be a minimum of 100 MB disk space available for the application installation files. 2. Copy the RetailServer.war file located at CDROM to a newly created staging directory on the UNIX server. This location is referred to as INSTALL_DIR for the remainder of this chapter, and is used for the RRS Online application configuration process. Example: /u00/websp/rrs Open the WebSphere Administrative Console that is to be used for administering the RRS 12.0 application If the administrative console URL is unknown, consult the WebSphere documentation for the correct URL. Server = name or IP address of the server where WebSphere is running Port = WebSphere Admin Console port Example: 4. Click Applications->Install New Application 5. Under Preparing for the application installation (Specify the EAR/WAR/JAR module to upload and install.) click the Server Path radial button and set this field to INSTALL_DIR/RetailServer.war file (from step 2 above). 6. Enter a context name to be used when calling the application through the URL and click Next. Example: /retailserver 7. Under Preparing for the application installation (generate default bindings and mappings), leave all fields set as default and click Next. 8. Under Step 1: Provide options to perform the installation, change the Application Name to retailserver. 9. Accept the default options for the rest of the application installation steps until reaching Step 4: Summary. 10. Under Step 4: Summary, verify all installation information is correct and click Finish. This may take several minutes. Upon completion, the message Application retailserver installed successfully should appear. 11. Click the Save to Master Configuration link when it appears. 12. Click the Save button in the Save to Master Configuration section. Following a successful save, you are re-directed to the WebSphere Application Server Administrative Console. 13. Start the retailserver application. At this point the retailserver application should have a solid green arrow indicating successful startup. 10 Oracle Retail Server

19 Oracle Retail Server Configure the RRS Online Application Notes: A setup page is used to configure the properties files for RRS Online. Do not run the setup page on a Macintosh system. 1. On the UNIX application server, create a /config and /data directory in INSTALL_DIR that will be used for configuring RSS Online and loading data. These directories must be readable and writeable by the user that runs the WebSphere Application Server. Example: /u00/websp/rrs1202/config /u00/websp/rrs1202/data 2. Load the new RRS Online application by entering the following URL in a browser: Server = name or IP address of the server where WebSphere is running http_port = WAS HTTP port as defined by the HTTPTransport_1 value in the file WAS_HOME/config/cells/<cell>/nodes/<node>/servers/server1/server.xml Example: A page displaying a link to the setup_page appears. Click on this link. 3. The RRS Online Setup page appears. In the Directory structure section set the Configuration directory and Data directory to the respective directories created in Step 1 above; leave the Data ZIP file field blank unless directed by Oracle Retail. Configuration directory = <INSTALL_DIR>/config Example: Configuration Directory: /u00/websp/rrs1202/config Data directory = <INSTALL_DIR>/data Example: Data Directory: /u00/websp/rrs1202/data 4. Under Application Licensing set the License file field to the license.bin file. Note: The license.bin file needs to be obtained from Oracle Fulfillment Department. License file = <INSTALL_DIR>/license.bin Example: /u00/websp/rrs1202/license.bin Installation Guide 11

20 Application Server Installation Instructions 5. Under Database setup, set the following values in the fields provided: Database type, Database name, Username and password, Network host, Port number, Schema name, Dump file name. Datebase type = Oracle Datebase name = Oracle database SID name Example: prod_db1 Username and password = Oracle RRS schema owner and password Example: Username: rrs12 Password: retek Network host = IP address or name of server where the Oracle database is running Example: dbserver Port Number = Oracle database port Example: 1521 Schema name = leave this field blank Dump file name = leave blank unless directed by Oracle Retail 6. Under setup, retain the default settings for any of the following fields as this version of RRS does not provide functionality: External host name, from address, SMTP mail server, test address. The test address is the only non-required field. All other fields must be populated. Example: External Host Name: localhost:http_port From Address: admin@server.com SMTP Mail Server: localhost 7. Under Integration, set the following values in the fields provided: FTP server, FTP user and password, internal server name. Alternatively, these fields can be left blank and the FTP server can be configured later: FTP server = IP address or name of the ftp server FTP user and password = username/password created in Chapter 3 for Retail Server s exclusive use Example: FTP server: localhost FTP user and password: user retek Internal server name = leave blank unless directed by Oracle Retail 12 Oracle Retail Server

21 Oracle Retail Server Under Security, set the following fields as appropriate: Administration hosts, SSL available, CA certificate. Click Next. Administration hosts = comma-separated list of IP address/mask values to select the clients which are allowed to log in to perform system administration. Note: If no Administration Hosts are entered, all hosts are able to connect to the administration console. This configuration is not recommended. SSL available: This option may be selected if the application server is configured for SSL (https) access. CA certificate = This option may be selected if the server certificate in use was obtained from a recognized Certificate Authority (such as Verisign). Note: This setting determines when SSL mode is enabled for Macintosh systems. Macintosh browsers do not recognize SSL certificates which are not from a recognized Certificate Authority. 9. The RRS Online Setup: Part II: confirm settings page appears if no configuration errors were encountered after clicking the Next button from step 8. Confirm that all settings are correct on this page. If any values are incorrect, click the Back button in the browser to go to the previous page and make the proper adjustments. When the settings are correct, click Next. 10. The RRS Online Setup: Part III: installing page briefly appears, followed by the loading of RRS Online: Part IV: status page. A message appears stating the installation was successful and to restart the application server to continue configuring RRS Online. Review the installation log to ensure that no errors were encountered during the installation process. 11. Bounce (stop/start) the WebSphere application server in order for the RRS Online configuration changes to be made effective. 12. If necessary start the RRS Online application through the WebSphere Administrative Console. On the Enterprise Applications page, start the RRS Online application by checking the box next to this application and then clicking the start button. Ensure that the status of the RRS Online application is now up (green arrow). 13. Load the RRS Online application System Administration page by clicking the link in RRS Online Setup: Part IV (step 12 above) of the RRS Online Setup step (Please restart your application server and then click here to enter system administration). In the event that the page has timed out or been closed enter the application url in a browser. Example: After the WAR file installation, ensure that the cronexe.ksh is executable. Also, verify that the RMIservlethost=localhost in integrator.properties file. 15. Set up the Online Enterprise and users. Installation Guide 13

22

23 Installing a Patch (or New Release) to Retail Server in Websphere 5 Overview When running Retail Server (Design/Webtrack) on the Websphere Application Server, the recommended approach to upgrading to a new release is to uninstall and then reinstall the Retail Server (Design/Webtrack) application. Steps to Uninstall and Reinstall the Retail Server (Design/Webtrack) war File Note: For the purposes of these instructions, assume the Retail Server (Design/Webtrack) application is called: test1 and the Websphere server is called: server Make a copy of the Websphere Retail Server (Design/Webtrack) configuration directory which is found at: "AppServer/WebSphere/installedApps/server1/test1/RetailServer.war/WEB- INF/config" 2. Go to the Websphere Admin console. From here, do the following: a. Find the Retail Server (test1) application and click stop b. Click uninstall c. Click install and install the application using the same settings on each configuration screen used in previous installations. d. Stop Websphere 3. If there is a database script included with the patch, execute it now. 4. Remove the file: "AppServer/WebSphere/installedApps/server1/test1/RetailServer.war/WEB- INF/setup/blank" 5. Restore the directory: "AppServer/WebSphere/installedApps/server1/test1/RetailServer.war/WEB- INF/config" 6. Start Websphere Installation Guide 15