Oracle® Retail Place Installation Guide Release 12.
Oracle® Retail Place Installation Guide, Release 12.2 Copyright © 2006, 2008, Oracle. All rights reserved. Primary Author: Anirudha Accanoor 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.
Value-Added Reseller (VAR) Language Oracle Retail VAR Applications The following restrictions and provisions only apply to the programs referred to in this section and licensed to you. You acknowledge that the programs may contain third party software (VAR applications) licensed to Oracle. Depending upon your product and its version number, the VAR applications may include: (i) the software component known as ACUMATE developed and licensed by Lucent Technologies Inc.
Contents Preface ................................................................................................................................................................. ix Audience....................................................................................................................................................... Related Documents ..................................................................................................................................... Customer Support .
Setting Up the WebLogic Startup Script.............................................................................................. 4-4 Setting Up the Maximum Message Size .............................................................................................. 4-5 5 Installing Place Overview of the Installation Process.................................................................................................... 5-1 About Password Security Management ...........................................
Setting Up a Foreign JMS Server on WebLogic Server..................................................................... 6-6 A Files and Directory Structure Application Directory Structure ........................................................................................................... A-1 Modules Deployed On WebLogic Server ...........................................................................................
viii
Preface This guide enables you to install the Oracle Retail Place application, along with the server-side components required for the application.
Customer Support ■ https://metalink.oracle.com When contacting Customer Support, please provide: ■ Product version and program/module name ■ Functional and technical description of the problem (include business impact) ■ Detailed step-by-step instructions to recreate ■ Exact error message received ■ Screen shots of each step you take Review Patch Documentation If you are installing the application for the first time, you install either a base release (for example, 12.
1 Overview This chapter provides an overview of Oracle Retail Place and a roadmap for implementing the application. It contains the following sections: ■ Overview of Place ■ Overview of Oracle Configuration Manager ■ Roadmap for Implementing Place Overview of Place Oracle® Retail Place enables retailers to generate and publish recommended allocations based on optimal size profiles, pack configurations, available warehouse inventory or advance shipping notices (ASNs), and forecasted sales.
Overview of Place Figure 1–1 Typical Configuration for Place Client System Tier The Client System tier contains the systems that connect to the Place application using a Web browser. It includes systems with the following components: ■ Microsoft Windows ■ Microsoft Office ■ Microsoft Internet Explorer 7.
Overview of Place Database Server Tier The Database Server tier contains the systems configured with the database management systems (Oracle 10g Database) along with the necessary database software. The following essential schemas are created during the Place installation: ■ ■ ■ ■ ■ AUDIT schema – contains information that helps you better track objects, events and critical data changes. PLACE schema – contains data specific to the application.
Roadmap for Implementing Place Roadmap for Implementing Place This guide explains how you can install and set up the Place application, along with the required and optional software. The instructions in this guide assume knowledge of application servers, databases, and application installation, and are intended for system administrators and experienced IT personnel.
2 Planning Your Installation Before installing the Place application, you must first determine the performance and availability goals for your business, and then plan the hardware, network, and storage requirements accordingly. This chapter provides some basic considerations for the implementation. It also includes the list of hardware and software requirements.
Supported Configurations Planning for Optimal Place Performance Consider the following steps to plan and prepare the product environment. 1. Determine the Place metrics relevant to your business needs. 2. Determine your relevant business policies. The business policy is a statement of what rules govern the application processes. You need to develop a business policy based on your business rules. For more information about business rules, see the Place Configuration Guide. 3.
Supported Configurations Database Requirements Place requires the use of the Oracle database as described in the following table: Table 2–1 Oracle Database Requirements Software Requirement Database Oracle 10g Release 2 (10.2.0.2) Oracle 10g Release 2 (10.2.0.3) Operating System HP-UX 11i v2 (11.23) Enterprise Release on Itanium-based systems Solaris 10 for SPARC platform and x86 platform (with appropriate libc and timezone patches).
Supported Configurations Client System Requirements The following table lists the supported client system options: Table 2–3 Client System Environment Software Windows XP Pro SP2 (with Office XP) Windows XP Pro SP2 (with Office 2000) 2-4 Oracle® Retail Place Installation Guide Requirements ■ Microsoft Office XP ■ Microsoft Internet Explorer 7.0 ■ Microsoft Office 2000 ■ Microsoft Internet Explorer 7.
3 Setting Up the Database Before you run the Oracle installer to install the application, you must set up the database to include certain necessary tablespaces, and a database user account. This chapter describes how you can set up your database, and the various database components.
Creating the Default Tablespaces Creating the Default Tablespaces When you run the Oracle installer, schemas and tables for the application get installed on the database you create. For the schemas and tables to install successfully, the database must include certain default tablespaces. Use the Oracle 10g Database Configuration Assistant to create a default database with the tablespaces mentioned in Table 3–1, Business Database Tablespaces.
Creating the Database Links Creating the Database Links If you plan to install the Place application across two database instances, you must create the instances in the following manner, and then set up the database links between the two instances: ■ ■ Set up the ELM schema (historical data) on a database instance (for example, INSTANCE1). Set up the remaining database schemas (PLACE, AUDIT, OAK, and PINE schema) as a single BASE schema, on the other database instance (for example, INSTANCE2).
Creating the Database Links 3-4 Oracle® Retail Place Installation Guide
4 Setting Up the Application Server Before installing the Place application, you must set up a domain on the application server. Based on your business need, you must set up the domain to include one or more server instances, and logically related resources and services. This chapter describes how you can set up a domain on the WebLogic server.
Setting Up a WebLogic Domain Setting Up a WebLogic Domain Use the BEA WebLogic Configuration Wizard to create and set up a domain on the WebLogic Server. This section describes how you can create and set up a domain. It also includes the steps to configure the managed servers and clusters on the application server. To set up a WebLogic domain: 1. Navigate to the .\weblogic81\common\bin directory, and run the following command to start the BEA WebLogic Configuration Wizard in the graphical mode: sh config.
Setting Up a WebLogic Domain Table 4–1 Steps to Set Up a WebLogic Domain Step Window Task a. Configure Managed Servers Window Click Add, and then enter appropriate information in the following fields: ■ ■ ■ ■ Name – Valid server name. (String of characters that can include spaces.) Listen address – Listen address for a server instance. Listen port – Valid value for the listen port. The default value is 7001. SSL listen port – Valid value to be used for secure requests. The default value is 7002.
Setting Up the WebLogic Startup Script Table 4–1 Steps to Set Up a WebLogic Domain Step Window Task 8. Configure Administrative Username and Password Window Set up an administrative user name and password. Important: Please keep a note of the user name and password. You must specify this user name and password in the install.properties file. The Oracle Installer uses this user account to connect to the WebLogic Server during Place installation. 9. Configure Windows Options Window Click Next. 10.
Setting Up the Maximum Message Size 2. After the CLASSPATH statement, add the following statement to set up the LD_LIBRARY_PATH environment variable: export LD_LIBRARY_PATH=$/modules/Engine/lib/linux_ i686:$LD_LIBRARY_PATH You can choose to set up this environment variable as part of the automation process (for example, .bash_profile) defined for your business. Note: 3.
Setting Up the Maximum Message Size 4-6 Oracle® Retail Place Installation Guide
5 Installing Place After you have set up your database and application server, you can install Place using the guidelines provided in this chapter. This chapter contains the following sections: ■ Overview of the Installation Process ■ Installing Place ■ Install.properties Parameters Reference ■ Troubleshooting Installation Issues Overview of the Installation Process Although the options for IBM AIX, DB2, and WebSphere display on the Oracle Installer, they are not supported in this release.
Installing Place Installing Place Installing Place consists of the following tasks: ■ Accessing the Installation Software ■ Setting Up Your Installation Properties File ■ Installing Place in the Silent Mode ■ Installing Place Using the Graphical Oracle Installer ■ Installing the Sample Dataset During the installation, passwords entered on screen or set up in the install.properties file get encrypted using the Password Security Management module.
Installing Place Oracle E-Delivery writes a ZIP file to the default location you have selected for downloads. 6. Unpack the ZIP file to a temporary directory. In this guide, the directory that contains the installation media is referred to as the directory. Now you can set up your Place installation properties file. Setting Up Your Installation Properties File In order to install Place, you first need to specify the properties to use during the installation process.
Installing Place Argument Description -p Optional. Specifies an alternate path to the install.properties file. Defaults to ./install.properties. -l, --log-config Optional. Specifies an alternate log4j configuration file (to change the verbosity level or the log file output location). Defaults to ./Install/conf/log4j.properties. The log4j log file is used for troubleshooting. -y | -n Optional. Specifies whether or not to overwrite existing files.
Installing Place bash install.sh For more information about this command, see Installing Place in the Silent Mode. Note: The Welcome screen appears. Figure 5–1 Welcome Screen 5. Click Next. The Place Installation Destination screen appears. 6. On the Place Installation Destination screen, specify the paths for the following: ■ Destination Directory - path to the Place installation target directory. ■ Spool Directory - path to the Place spool directory.
Installing Place Figure 5–2 Place Installation Destination Screen 7. Click Next. The Place Selections screen appears. 8. On the Place Selections screen, select the component you want to install, and click Next. Figure 5–3 Place Selections Screen 9. On the Application Server Selections screen, click BEA WebLogic, and then click Next.
Installing Place Figure 5–4 Application Server Selections Screen 10. On the WebLogic Application Server screen, enter the relevant information (such as host, port, user name, password) to connect to the WebLogic server set up for the application. Figure 5–5 WebLogic Application Server In case the installation does not proceed ahead, check the WebLogic server information or the status of the application server. Note: 11.
Installing Place Figure 5–6 Java Message Server Properties Screen 12. Click Next. The Database Selections screen appears. 13. On the Database Selections screen, click Oracle, and then click Next. Figure 5–7 Database Selections Screen 14. On the Database Properties screen, enter the following database information for the Place Front End, Actual History, Application, Audit, and Plan Front End databases: ■ ■ ■ Database server address – Enter the address of the database server.
Installing Place ■ ■ Database alias – Enter the database alias, which is typically the same name as the database. Tables – Select one of the following options: – No Change – Select this option if you have an existing database schema that you do not want to modify. This enables you to configure data sources, EAR files, and so forth, without affecting the database. – Create – Select this option if you are installing a new database schema for Place.
Installing Place Figure 5–9 Schema Link Properties Screen 16. Review the Selection Verification screen, and click Install. Figure 5–10 Selection Verification Screen The Installation Progress screen appears. If the installation resulted in issues, see Troubleshooting Installation Issues on page 5-24. 17.
Installing Place Setting Up ADF Libraries For the Online Help to work, you must invoke the ADF libraries in the WebLogic Server Home directory. Although the ADF libraries are part of the product installation and they get installed along with the product, you must source the setupadf.sh file in the WebLogic startup script. To source the setupadf.sh in the WebLogic startup script: 1.
Installing Place Table 5–1 Servername and Portnumber Description Where Is servername The name of the application server where the application is installed. portnumber The port number that the application server uses for the application. 2. On the WebLogic Server Console, under Service Configurations, click Servers in the JMS column. The JMS Servers page appears. 3. On the JMS Servers page, click AllocationServer. 4. On the AllocationServer page, click the Target and Deploy tab. 5.
Installing Place Installing the Sample Dataset The Place installation comes along with a sample dataset that can be used during implementation and demonstrations. This dataset contains generic data and is designed to work along with the default product configuration. The data files, along with the necessary data load scripts, are included as part of the installation media. When you run the Oracle Installer, the sample dataset does not get installed by default.
Install.properties Parameters Reference Install.properties Parameters Reference The install.
Install.properties Parameters Reference Last Session Properties Files The Last Session Properties Files settings enable you to specify the location where you want to store the last-session.properties and missing-entries.properties files. The following table describes the Last Session Properties Files settings: Table 5–4 Last Session Properties Files Parameter Description install.properties.savefile Use this parameter to specify the location where you want to store the last-session.properties file.
Install.properties Parameters Reference Table 5–6 Connections in the Connection Pools Parameter Description weblogic.dbcpool.historicalconnectionpool.min Use this parameter to specify the minimum database connections in the historical connection pool. weblogic.dbcpool.historicalconnectionpool.max Use this parameter to specify the maximum database connections in the historical connection pool. weblogic.dbcpool.analyticalconnectionpool.
Install.properties Parameters Reference Table 5–8 WebLogic Application Server Settings Parameter Description weblogic.managedserver.address Indicates the URL to connect to the managed server. The value defaults to the URL specified in the weblogic.server.address parameter. For a clustered-based installation, ensure that you set the appropriate managed server address. weblogic.managedserver.port Indicates the port to connect to the managed server.
Install.properties Parameters Reference Table 5–9 Connection and Authentication Settings Parameter Description dbms.oracle.alias Use this parameter to specify the database alias name. dbms.oracle.user Use this parameter to specify the user name to connect to the database. dbms.oracle.pass Use this parameter to specify the password to connect to the database. Oracle DB Configuration database.commondb.oracle.address Use this parameter to specify the URL where the Oracle database is installed.
Install.properties Parameters Reference Audit Database Properties The Audit Database properties enable you to specify the connection and authentication parameters for the Audit database. The following table describes the Audit Database properties: Table 5–10 Audit Database Properties Parameter Description database.AuditDB.oracle.dbname Use this parameter to specify the name of the Audit database. database.AuditDB.oracle.auth.auditoracleauth.
Install.properties Parameters Reference Place Schema Properties The Place Schema properties enable you to specify the connection and authentication parameters for the Place schema in the Place database. The following table describes the Place Schema properties: Table 5–11 Place Schema Properties Parameter Description Properties to Define the Place Database database.placedb.oracle.address Use this parameter to specify the URL where the Place Front End database is installed database.placedb.oracle.
Install.properties Parameters Reference Table 5–12 Plan Front End Database Properties Parameter Description database.plandb.oracle.create Use this parameter to indicate that a new Plan database be created. Valid values are Yes or No. database.plandb.oracle.upgrade Use this parameter to indicate that the existing Plan database be upgraded. Valid values are Yes or No.
Install.properties Parameters Reference Place-specific Suite Properties The Place-specific Suite properties enable you to specify properties that apply across the product suite. The following table describes the Place-specific Suite properties: Table 5–14 Place-specific Suite Properties Parameter Description http.protocol Use this parameter to specify to specify the type of http protocol. ce.url Use this parameter to specify the URL where the Calculation Engine is installed.
Install.properties Parameters Reference Table 5–15 Cluster Properties Parameter Description jndi.host Use this parameter to specify the host name of the JNDI server. jndi.port Use this parameter to specify the port to connect to the JNDI server. integration.jndi.host Use this parameter to specify the host name of the JNDI server that is used as an external queue. integration.jndi.port Use this parameter to specify the port to connect to the JNDI server that is used as an external queue. jndi.
Troubleshooting Installation Issues Table 5–16 Last Session Properties Files Parameter Description mstr.users.max Use this parameter to specify the maximum number of users that can connect to the MicroStrategy server at a time. bi.server Use this parameter to specify the Business Intelligence (BI) server version. Valid values are MS7 or MS8. Plan supports the Microstrategy 8 platform.
Troubleshooting Installation Issues Installation Aborts Because of Incompatible Components When upgrading to the Plan Release 12.2 and Place Release 12.2 on a co-deployed environment, in case the installation does not complete because of the incompatible components, you must run the first product upgrade with "-P" argument. For more information, see Upgrading a Co-deployed Environment.
Troubleshooting Installation Issues 5-26 Oracle® Retail Place Installation Guide
6 Installing Place Over Plan This chapter describes how you can install the Place application to work along with an existing installation of Plan. It includes the procedures you can use to deploy the Place application in the same WebLogic domain used by Plan. It includes the following sections: ■ Setting Up the Plan Installation (applies to upgrades from Plan version 2.
Setting Up the Place Installation database..oracle.upgrade=yes For more information on the installation properties file and the Plan installation procedure, see the chapter Installing Plan. Setting Up the Place Installation Before you start installing the Place application, you must edit the installation properties file and direct the installer to create a new Place schema.
Configuring Place Configuring Place Once the Place application is installed, you must load the user roles and business rules used between Place and Plan. You must also run certain scripts that load seed data for the Place application.
Configuring Place load the seed data. For more information on the scripts, see Reference to the Data Load Scripts. To load the seed data: 1. At the SQL prompt, run the following scripts: ■ custom_ir_objects.sql (Custom script) ■ pl_dd_attributes.sql (Generic script) ■ data_levels_tbl.sql (Custom script) ■ dist_centers_tbl.sql (Custom script) These scripts are common for the Place and Plan applications.
Configuring Place Reference to the Data Load Scripts The following table describes the scripts (required for the data load), and lists their location in the AESample directory: Table 6–1 Data Load Scripts for Place and Plan Script Name Script Location (Place_Install\DataSets\AESample) Script Description Custom Scripts custom_ir_objects.sql AESample\Data\Seed This SQL script loads the customized inference rules. data_levels_tbl.
Upgrading a Co-deployed Environment Upgrading a Co-deployed Environment When upgrading to the Plan Release 12.2 and Place Release 12.2 on an existing co-deployed environment, the installation may abort because of the incompatible components. The following example (Example 6–1) displays an error message that lists the incompatible components (Alert 1.3.1 and Suite 1.5.0). Example 6–1 Incompatible Components Error ERROR: The following components are not compatible: ERROR: Alerts 1.3.1 and Suite 1.5.
Setting Up a Foreign JMS Server on WebLogic Server Local JNDI Name: CommonConnectionFactory Remote JNDI Name: CommonConnectionFactory 7. Configure a new Foreign JMS Topic and point it to the topic created under the CommonJMSServer deployed on Plan. For example, Name: RemoteNotificationTopic Local JNDI Name: com.profitlogic.notification.topic Remote JNDI Name: com.profitlogic.notification.topic The 'com.profitlogic.notification.
Setting Up a Foreign JMS Server on WebLogic Server 6-8 Oracle® Retail Place Installation Guide
A Files and Directory Structure This appendix provides a reference to the directory structure of a typical Place installation. It includes information on the locations of the various enterprise archive (EAR) modules that get deployed over the WebLogic server.
Application Directory Structure Table A–1 Application Directory Structure First Level Second Third Level Level Fourth Level |------ Description The Place Installation Base folder. integration |----- testharness |----- translators |----- xsd |----- xsdvalidator Contains the configuration files for the Integration module. This includes the integration.properties file. |------ SIT Contains the configuration files for the System Information Tool (SIT) module.
Application Directory Structure Table A–1 Application Directory Structure First Level Second Third Level Level Fourth Level Description The Place Installation Base folder. |------ Database Contains the scripts that help set up the application database. |------ Datasets Contains the scripts and control files that help set up a sample (AESample) dataset.
Modules Deployed On WebLogic Server Modules Deployed On WebLogic Server The following table lists the application modules EARs deployed on the WebLogic server: Table A–2 Modules Deployed on WebLogic Server Module Name Description EAR File Name and Location allocating4p Place application /modules/Place/allocating4p.ear BRMHelp Business Rule Management Online Help /modules/Suite/brmhelp.ear BusinessRuleMgr Business Rule Management Module /modules/Suite/businessrulemgr.
Index A E ADF libraries, 5-11 application server requirements, 2-3 application server and database settings, 5-15 E-delivery, 5-2 enterprise components application server tier, 1-2 client system tier, 1-2 database server tier, 1-3 B brmadmin, 6-3 bulk loader, 6-3 business rules, 6-3 C CE user setting, 5-16 client system requirements, 2-4 command shell settings, 5-14 configure load roles, 6-3 load rules, 6-3 load seed data, 6-3 place over plan, 6-3 connection pools settings, 5-15 custom scripts, 6-5 D
webLogic application server settings, 5-16 install.
