Oracle Retail Navigator Installation Guide Release 11.2 ...Oracle Retail Navigator works in conjunction with the Oracle Retail Security Manager (RSM). In order for Oracle Retail Navigator

Oracle® Retail Navigator

Installation Guide Release 11.2

January 2007

Oracle® Retail Navigator Installation Guide, Release 11.2

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 agency-specific 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 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065

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, third-party 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.

iii

Contents Preface ............................................................................................................................... v

Audience ....................................................................................................................................v Related Documents ....................................................................................................................v Customer Support ......................................................................................................................v Conventions ...............................................................................................................................v

1 Hardware and Software Requirements...................................................................... 1 Database Server .........................................................................................................................1 Application Server .....................................................................................................................1 Client PC and Web Browser Requirements ...............................................................................1

Client PC Requirements......................................................................................................1 Browser Requirements........................................................................................................1

2 Database Configuration Instructions......................................................................... 3 3 Application Server Configuration Instructions......................................................... 5

UNIX (Sun Solaris/HPUX/AIX) ...............................................................................................5 Configure WebSphere 5.1.1.10 Application Server for Navigator 11 ................................5 Deploy Navigator.ear in WebSphere Application Server 5.1.1.10 .....................................8 Customize Necessary Configuration and Properties Files ..................................................9 Start Retek Navigator 11.2................................................................................................10

4 Client Installation Instructions ................................................................................. 11 5 Deploying the JNLP Web Application...................................................................... 13

Deploy jnlpgen.war in WebSphere Application Server 5.1.1.10 .............................................13 6 Test the Navigator Client and Jnlpgen Servlet ....................................................... 17

Navigator Client.......................................................................................................................17 A Appendix: Customizing Navigator to Integrate with Other Oracle Retail Applications..................................................................................................................... 23

RMS Based Applications.........................................................................................................23 RDW Applications...................................................................................................................23

Category Management......................................................................................................23 Customer Workbench .......................................................................................................23 Merchandise Workbench ..................................................................................................24 Store Operations ...............................................................................................................24

Oracle Retail Allocation and Oracle Retail Invoice Matching.................................................24 Invoice Matching ..............................................................................................................24 Allocation .........................................................................................................................25

v

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 For more information, see the following documents in the Oracle Retail Navigator Release 11.2 documentation set: Oracle Retail Navigator Release Notes Oracle Retail Navigator Operations Guide

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.

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.

https://metalink.oracle.com/

Hardware and Software Requirements 1

1 Hardware and Software Requirements Oracle Retail Navigator is a client-server application. Its client side code runs in a WebStart Java Virtual machine instance, while its server side code runs in the WebSphere EJB Container and accesses an Oracle Database server.

Database Server General requirements for a database server capable of running Oracle Retail Navigator application include: UNIX based OS certified with Oracle RDBMS 9i release 2 Enterprise Edition (Options

include AIX 5.2, Solaris 9, and HP-UX 11.11) Oracle RDBMS 9i release 2 Enterprise Edition.

Application Server General requirements for an application server capable of running Oracle Retail Navigator application include: UNIX based OS certified WebSphere Application Server version 5.1.1.10 (Options

include AIX 5.2, Solaris 9, and HP-UX 11.11) IBM WebSphere Application Server version 5.1.1.10.

Client PC and Web Browser Requirements

Client PC Requirements Operating system: Windows 2000 or XP Display resolution: 1024x768 or higher Processor is 1GHz or higher; Memory is 512MBytes or higher; Sun J2RE Runtime equal to v1.4.2_x

Browser Requirements Microsoft Internet Explorer 5.5 or higher

Database Configuration Instructions 3

2 Database Configuration Instructions

Oracle Retail Navigator works in conjunction with the Oracle Retail Security Manager (RSM). In order for Oracle Retail Navigator to run, RSM must first be installed and configured properly. The Navigator install may use the RSM schema owner.

Note: If Navigator 11.0.2 or 11.1 is installed it is not necessary to remove the Navigator database objects.

Application Server Configuration Instructions 5

3 Application Server Configuration

Instructions The Oracle Retail Navigator server tier is packaged as an EAR file – Navigator.ear. Install the Navigator.ear file on the J2EE application server according to the vendor's documentation. The following are typical steps for deploying an ear file in WebSphere 5.1.1.10, assuming WebSphere Application Server 5.1.1.10 (WAS) and IBMHttpServer 5.1.1.10 have already been installed. It is also assumed Oracle has already been configured and loaded with the appropriate Navigator Schema for your installation.

UNIX (Sun Solaris/HPUX/AIX) Note: IBM JVM 1.4.2 is required for Oracle Retail Navigator server side installation (and is shipped with Websphere 5.1.1.10)

Note: IBM recommends that the IBMHttpServer be configured to run as the front-end for WebSphere Application Server.

Note: ojdbc14.jar is required for RSM 11. This file can be obtained from the Oracle Technology Network web site, and must be copied to a staging directory on the webserver where WebSphere 5.1.1.10 is installed (ie: /server/websp/jdbc/ojdbc14.jar)

Configure WebSphere 5.1.1.10 Application Server for Navigator 11 1. Log on to the UNIX webserver where WebSphere 5.1.1.10 is installed as the retek

user and determine where the Navigator 11 application server file (nav11appserver.zip) will be installed. There should be a minimum of 150 MB disk space available for the application installation files.

2. Copy nav11appserver.zip located at CD/appserverunix to a newly created staging directory on the UNIX server. This location will be referred to as INSTALL_DIR for the remainder of this chapter.

3. Change directories to INSTALL_DIR and extract the contents of nav11appserver.zip

UNIX (Sun Solaris/HPUX/AIX)

6 Oracle Retail Navigator

4. Open the WebSphere Administration Console that is to be used for administering the Navigator 11 application – http://:/admin. If the administrative URL console is unknown, consult the WebSphere 5.1.1.10 documentation for the correct URL. server = name or IP address of server where WebSphere 5.1.1.10 is running admin_port = WebSphere admin console port

Example: http://server:9090/admin Click on Environment->Manage WebSphere Variables. Under WebSphere Variables:

a. Click ORACLE_JDBC_DRIVER_PATH and set the value of this variable to the directory containing the oracle driver archive file ojdbc14.jar (obtained from otn.oracle.com).

Example: /server/websp/jdbc

b. Click Apply 5. Click on Security->JAAS Configuration->J2C Authentication Data.

Note: If Oracle Retail Navigator and Oracle Retail Security Manager are deployed using the same database schema the schema id below can be shared between the two.

6. Under J2C Authentication Data Entries, click New and enter the following information in the fields provided: a. Alias (alias for Authentication Data Entry) b. UserID (Navigator database schema owner) c. Password (Navigator database schema password) d. Click Apply

Example: Alias: navigatorAlias UserID: nav11dev Password: retek

7. Click on Resources->JDBC Providers. If the Oracle JDBC Driver (XA) JDBC Provider has already been created for another application that is running on this same WebSphere instance, select the Provider, skip steps 10 and 11 below and proceed to step 12.

8. Under JDBC Providers, click the server radial button or browse to the appropriate server (if multiple servers on this node) and then click Apply.

9. Create a new JDBC Provider by clicking New Select Oracle JDBC Driver (XA) from the JDBC list of values and click Apply

http://server:9090/admin



10. Under Additional Properties, select Data Sources and New: a. Data Source Name: Navigator (must be this value) b. JNDI Name: jdbc/fpdev11 (must be this value) c. Select Component Managed Alias. Choose the J2C Authentication Alias

(Example, navigatorAlias) that was created in step 4 above d. Leave the container-managed alias blank. CMP is not used in Oracle Retail

Navigator e. Select the Mapping-Configuration Alias to DefaultPrincipalMapping f. Leave all the other default values g. Click OK

Example: Name: Navigator JNDI Name: jdbc/fpdev11 Component-managed Authentication Alias: server/RSM11 Mapping-Configuration Alias: DefaultPrincipalMapping

11. Under Additional Properties, click Custom Properties for the Data Source and then click URL a. Value: jdbc:oracle:thin:@::

Example: jdbc:oracle:thin:@dbserver:1521:prod_db1

b. Click Apply; Click back to Custom Properties c. Click transactionBranchesLooselyCoupled. Enter the following information in

the Value Field: true d. Click Apply; Click back to Custom Properties e. Click preTestSQLString. Enter the following information in the Value Field:

select count(*) from dual f. Click Apply

12. Save the configuration by clicking the Save link in the Message(s) section, and then by clicking the Save button in the Save to Master Configuration section.

13. Verify the configuration by using the “Test Connection” option in the Data Sources configuration section (Resources->JDBC Providers->Oracle JDBC Driver (XA)->Data Sources->Data Source Name->Test Connection button). A successful message in the Message(s) section should appear. In the case of an unsuccessful connection test, review all previous steps to ensure that the configuration thus far is accurate.

14. Click on Servers -> Application Servers 15. Under Application Servers, click on the link for the server instance created during

installation; the default name of the initial application server instance is server1. 16. In the General Properties section click on the Endpoints link in the lower section of

the page. 17. Under BOOTSTRAP_ADDRESS, verify the Host and Port values are set correctly.

Record these host and port values as they will be needed when configuring the Navigator 11 client.



18. Update the file j2c.properties adding a new advanced-connection-properties parameter for the Navigator JNDI name. The file is located in the directory WAS_HOME/properties.

Example: true 5

Note: The j2c.properties file is associated with a particular application server. This application server must be restarted before these changes will take affect.

Deploy Navigator.ear in WebSphere Application Server 5.1.1.10

Note: Prior to proceeding to ear deployment it is necessary to inject the hibernate2.jar file into the RSM11.ear file. Due to open source licensing restrictions, clients are required to manually download and install hibernate2.jar.

1. Open the WebSphere Administrative Console that is to be used for administering the Navigator application -

2. Click on Applications->Install New Application. 3. Under Preparing for the application installation, select the Server path radial button

and set this field to INSTALL_DIR/Navigator.ear and then click Next.

Example: server path: /server/websp/nav11en/Navigator.ear

4. Accept the default options for Steps 1 – 3; clicking Next until reaching “Step 4: Map modules to application servers”.

5. Under “Step 4: Map modules to application servers”, select the server which will be used for deploying the application (default server is server1), check the checkbox for the Navigator module and click the Apply pushbutton. The server field will be updated with the appropriate server. Click Next.

6. Accept the default options for the rest application installation and click Next until reaching “Step 6: Summary”.

7. An “Application Security Warnings” page may be displayed; this warning can be ignored and the Continue button clicked.

8. Under “Step 6: Summary”, verify all installation information is correct and click Finish. This may take several minutes. Upon completion, the message “Application navigator installed successfully” should appear.

9. Click the Save to Master Configuration link when it appears. 10. Click the Save button in the Save to Master Configuration section. Following a

successful save, you will be re-directed to the WebSphere Application Server Administrative Console.

11. Click on Applications->Enterprise Applications; click on the Navigator application link to load the Navigator application configuration page



12. Under General Properties, set the Classloader Mode property to PARENT_LAST, and then click the OK button.

13. Save to master configuration once again.

Customize Necessary Configuration and Properties Files Before starting the Navigator application, the launchParams.properties and jndi_providers_rsm.xml files must be updated with application-specific information.

launchParams.properties The launchParams.properties file is located in directory WAS_HOME/installedApps//Navigator.ear/conf/retek/. This file needs to be customized to point to the specific Oracle Retail application URLs used by the client. In each case the server and port must be updated. For Java Web Start applications (RPM, RSM) launched using the jnlp web application, replace string ‘@deploy.jnlpgen.url@’ with the server and port of the JNLPGEN web application. For web applications Oracle Retail Allocation and Oracle Retail Invoice Matching, update their corresponding string tokens with their server and port information: @alloc.server.port@, @reim.server.port@. For Microstrategy (RDW) and Oracle Forms based applications (RMS, ARI), update string @deploy.client.codebase@ which corresponds to the web server that serves the submitter.html file used.

Examples: rms=http://server:port/navigator/submitter.html?config=rms11en allocation=http://server:port/alloc/index.jsp?fromrsm=true reim=http://server:port/reim/index.jsp?fromrsm=true rpm=http://server:port/jnlpgen/generate.go?template=rpm11_jnlp_template.vm rsm=http://server:port/jnlpgen/generate.go?template=rsm11_jnlp_template.vm

Note: Some Oracle applications require HTML files and Javascript (ie. submitter.html) to achieve single sign-on. Updates are required to these HTML files. These updates are highlighted in Chapter 4, Client Installation Instructions.

Connect Strings The connect strings section is specifically for Oracle Forms-based applications (such as RMS) that require connect string parameters in their URL. These properties are string variables that contain database connection information. These string values (@ARIdbConnectString@, @RMSdbConnectString@) must be updated to point at the database being used for each application.

Examples: #app.launch.parameter connect strings conn.ariadmin=ps28rmsp conn.rms=sup9i conn.htsfindfmb=sup9i



jndi_providers_rsm.xml Oracle Retail Navigator requires OracleRetail Security Manager for encryption, authorization and authentication. The file jndi_providers_rsm.xml contains the information necessary for Navigator to communicate with RSM. The string token @deploy.rsm.url@ should be updated with the correct WebSphere BOOTSTRAP_ADDRESS of RSM. This file is located in directory WAS_HOME/installedApps//Navigator.ear/conf/retek.

Example: com/retek/rsm/app/app/security/service/SecurityService

Start Retek Navigator 11.2 1. Open the WebSphere Administrative Console. 2. Under Applications->Enterprise Applications, select the Navigator application and

start the application. 3. At this point the Navigator application should have a solid green arrow indicating

successful startup.

Client Installation Instructions 11

4 Client Installation Instructions

The following steps describe how the Oracle Retail Navigator 11 client is configured to serve its files over the IBMHttpServer in conjunction with Java WebStart. This installation assumes that the IBMHttpServer is the front-end to the WebSphere Application Server where the Navigator.ear file was installed and configured.

Note: SUN JRE 1.4.2 must be installed on the client PC in order for the Navigator 11 client to run. Any Sun JRE 1.4.2x contains Java WebStart, which is used to distribute and update clients via HTTP. Sun JRE 1.4.2 can be downloaded from the Sun website – http://java.sun.com

1. On the webserver, change directories to the document root for IBMHttpServer. This location can be determined by examining the file IBMHttpServer/conf/httpd.conf; the value for the DocumentRoot directive in this file specifies the document root for IBMHttpServer.

Example: cd /u00/websp/IBMHttpServer/htdocs/en_US

2. Create a /navigator directory under the DocumentRoot directory

Example: mkdir navigator

3. Change directories to the newly created navigator directory. 4. Copy the navigator client zip file located in the directory INSTALL_DIR/client into

the newly created navigator directory.

Example: /u00/websp/IBMHttpServer/htdocs/en_US/navigator> cp /u00/websp/nav11en/client/NavClient.zip

5. Unzip the navigator client zip file.

Example: /u00/websp/IBMHttpServer/htdocs/en_US/navigator> unzip NavClient.zip

http://java.sun.com/



6. Edit the appropriate Navigator jnlp files according to the language in which the application will be displayed. These files are located in the document root directory of the web server where Navigator was unzipped. a. navigator-.jnlp or navigator.jnlp for English:

java.naming.provider.url property (@deploy.navigator.url@): Points to the WebSphere application server's host and port from the BOOTSTRAP_ADDRESS.

Example:

a. Codebase attribute (@deploy.client.codebase@): Points to the URL where the client code is stored.

Example:

Icon attribute: Icon displayed by Java WebStart when Navigator client is downloaded. Points to file in the images directory of the Navigator document root directory (web server).

Example:

b. navBC.jnlp: Codebase attribute (@deploy.client.codebase@): Points to the URL where the

client code is stored.

Example:

Icon attribute: Icon displayed by Java WebStart when Navigator client is downloaded. Points to file in the images directory of the Navigator document root directory (web server).

Example:

For Navigator to successfully launch other Oracle Retail applications some configuration changes are necessary. See Appendix A for details on these required changes.

7. Edit the file IBMHttpServer/conf/mime.types by adding the jnlp MIME type: application/x-java-jnlp-file jnlp

Example: application/x-javascript js application/x-java-jnlp-file jnlp application/x-koan skp skd skt skm

8. Reload the IBMHttpServer for the above changes to take effect.

http://server:port/navigator/http://server:9081/navigator/http://server:9081/navigator/images/retek_logo.jpg

Deploying the JNLP Web Application 13

5 Deploying the JNLP Web Application

Deploy jnlpgen.war in WebSphere Application Server 5.1.1.10 Some applications launched by Oracle Retail Navigator and Java WebStart require dynamically generated jnlp files. This is accomplished by deploying a web application with a jnlp servlet. This application is packaged as a WAR file – jnlpgen.war. Install the jnlpgen.war file on the J2EE application server according to the vendor's documentation. The following are typical steps for deploying a war file in WebSphere 5.1.1.10, assuming WebSphere Application Server 5.1.1.10 has already been installed. 1. Open the WebSphere Administration Console that is to be used for administering the

RSM 11 client – http://:/admin. If the administration console URL is unknown, consult the WebSphere 5.1.1.10 documentation for the correct URL. server = name or IP address of server where WebSphere 5.1.1.10 is running admin_Port = WebSphere Admin Console Port

Example: http://server:9090/admin

2. Click on Application->Install New Application 3. Under Preparing for the application installation, select the Server path radial button

and set this field to INSTALL_DIR/temp/jnlpgen.war (from step 2 in the previous section above).

Example: server path: /u00/websp/rsm11/temp/jnlpgen.war

4. Enter a context name to be used when calling the servlet through the URL; click Next.

Example: /jnlpgen

5. Under Preparing for application installation – Generate Default Bindings, select the virtual host that will be used for deploying the application (default virtual host is default_host); click Next.

6. An “Application Security Warnings” page may be displayed; this warning can be ignored and the Continue button clicked.

7. Under “Step 1: Provide options to perform the installation”, change the Application Name from jnlpgen_war to jnlpgen; click Next.

8. Under “Step 2 :Map virtual hosts for web modules”, select the virtual host which will be used for hosting the application (default virtual host is default_host). Click Next.

9. Under “Step 3 :Map modules to application servers”, select the server which will be used for deploying the application (default server is server1), check the checkbox for the jnlpgen.war module and click the Apply pushbutton. The Server field will be updated with the appropriate server. Click Next.

10. Under “Step 4: Summary”, verify all installation information is correct and click Finish. This may take several minutes. Upon completion, the message “Application jnlpgen installed successfully” should appear”.

http://server:9090/admin

Deploy jnlpgen.war in WebSphere Application Server 5.1.1.10


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 will be re-directed to the WebSphere Application Server Administrative Console.

13. Under Servers Application Servers, click on the link for the server instance created during the WebSphere installation; the default name of the initial application server instance is server1.

14. In the Additional Properties section click on the Web Container link in the lower section of the page.

15. Click on link HTTP transports 16. Verify that the Host, Port and SSL Enabled values are set correctly. Record these

settings as they will be needed when configuring the jnlpgen URL’s.

Example: Host Port SSL * 9080 false * 9090 false * 9443 true * 9043 true

Note: The host and transport information must be in the current web server plugin configuration file for the servlet to execute. Click on Environment Update Web Server Plugin to view the current plugin. If they don’t exist, click OK to update the configuration file. Refer to the WebSphere vendor documentation for more information.

17. After a successful installation of the jnlpgen application the configuration files contained within the war file must be modified. These files are located in directory WAS_HOME/installedApps//jnlpgen.ear/jnlpgen.war/. a. rsm11_jnlp_template.vm & rsm11_login_jnlp_template.vm b. Code base attribute (@deploy.rsm.codebase@): Update the code base to point to

the library (URL) on the web server containing the client jar files.

Example:

c. Icon attribute: Update the location of the parameter ‘icon’ to point to the directory on the web server containing the Retek logo (from step 2 above).

Example:

d. Web Help URL property: Update this property to the location of the RSM online web help.

Example:

Deploy jnlpgen.war in WebSphere Application Server 5.1.1.10

Deploying the JNLP Web Application 15

e. Provider URL property (@deploy.rsm.url@): Contains the bootstrap address (IIOP) of the RSM Service.

Example:

Note: If other Oracle Retail applications will be deployed and executed via Java WebStart, jnlp templates will need to be added/updated here for them to be accessed via Navigator. The first grouping of letters in the template file name designates the application. For example, rsm11_jnlp_template.vm is Oracle Retail Security Manager and rpm11_jnlp_template.vm is Oracle Retail Price Management.

18. If your installation includes RPM, make the corresponding changes to the RPM jnlp file. This file is located in directory WAS_HOME/installedApps//jnlpgen.ear/jnlpgen.war/. a. rpm11_jnlp_template.vm b. Code base attribute (@deploy.rpm.codebase@): Update the code base to point to

the library (URL) on the web server containing the RPM client jar files. 19. Start the jnlpgen application. 20. At this point, the jnlpgen application should have solid green arrow indicating

successful startup.

Test the Navigator Client and Jnlpgen Servlet 17

6 Test the Navigator Client and Jnlpgen

Servlet Note: Before testing the Oracle Retail Navigator or the Jnlpgen web application, Oracle Retail Security Manager must be successfully installed and running.

Navigator Client 1. Load the newly configured navigator.jnlp file by entering the URL in a browser.

server = name or IP address of the server where IBMHttpServer is running http_port = IBMHttpServer port as defined by the Port value in the file

IBMHttpServer/conf/httpd.conf

Example: http://server:9081/navigator/navigator.jnlp

Note: Ensure that the client has a J2RE installed with Java WebStart. WebStart should automatically install and run the Oracle Retail Navigator client application.

The following dialogue will be displayed when running the Navigator client via Java WebStart.

Note: Dialogues may differ slightly depending on the version of Java WebStart used.

A Security Warning window similar to the following may appear. Click the Start button to continue.

http://server:9081/navigator/navigator.jnlp

Navigator Client


A Security Warning window similar to the following may appear. Click the Install button to continue.

The Oracle Retail Navigator Login screen will appear. Enter a valid user Id and password. This will be authenticated using Oracle Retail Security Manager.

Navigator Client


The main Oracle Retail Navigator screen will be displayed. If this user has access to any other Oracle Retail applications they will be listed in the Oracle Retail Tasks window.

Jnlpgen Servlet 1. Test the jnlpgen application and the RSM client by entering the following URL in a

browser: http://://generate.go?template=rsm11_login_jnlp_template.vm webserver = name or IP address of the server where the IBMHttpServer is

running port = IBMHttpServer port as defined by the Port value in the file

IBMHttpServer/conf/httpd.conf context = value of Context Root as entered when deploying the jnlpgen web

application

Example: http://server:9085/jnlpgen/generate.go?template=rsm11_login_jnlp_template.vm

A Java WebStart window similar to the following should appear the first time the jnlpgen application is accessed per PC if JRE 1.4.x and Java Web Start were installed as required. This window displays the RSM install on the client PC.

Navigator Client


A Security Warning window similar to the following may appear. Click the Start button to continue.

A Security Warning window similar to the following may appear. Click the Install button to continue.

Navigator Client


A login dialogue similar to the following should appear. Enter a valid user Id and password.

Users with permission to view content within RSM will see the following screen.

Navigator Client


Users that do not have permission to view content in RSM will see the following screen.

Appendix: Customizing Navigator to Integrate with Other Oracle Retail Applications 23

A Appendix: Customizing Navigator to

Integrate with Other Oracle Retail Applications

RMS Based Applications RMS and RMS based applications can be securely launched from Navigator. Submitter.html located in directory docroot/navigator must be updated to point to the RMS Oracle servlet. The edit ‘action’ parameter (@rms.login.url@) inside the submitter.html must be updated to point to the appropriate location.

Example: Update the POST action parameter. (''); (''); ('');

RDW Applications Directory docroot/navigator on Navigator’s web server contains four RDW submitter HTML files. In each of these files the Microstrategy Intelligence server and Microstrategy Web server property must be updated.

Category Management

Example: Update the POST action parameter (@rdw.category.login.url@)of file RDWCatMgmtSubmitter.html to contain the server and URL information for your installation. ('');

Customer Workbench

Example: Update the POST action parameter (@rdw.customer.login.url@)of file RDWCustWBSubmitter.html to contain the server and URL information for your installation. ('');

Oracle Retail Allocation and Oracle Retail Invoice Matching


Merchandise Workbench

Example: Update the POST action parameter (@rdw.merch.login.url@) of file RDWMerchWBSubmitter.html to contain the server and URL information for your installation. ('');

Store Operations

Example: Update the edit action parameter (@rdw.store.login.url@) of file RDWStoreOpWBSubmitter.html to contain the server and URL information for your installation. ('');

Oracle Retail Allocation and Oracle Retail Invoice Matching In order to access Oracle Retail Allocation and Invoice Matching via Navigator’s single sign-on, several permissions tables in each of the respective schemas will need to be updated. See the documentation included with the applications below for more information.

Invoice Matching 1. Change directories to J2EE_HOME/applications/reim/WEB-INF/classes and create

a new directory retek

Example: mkdir retek

2. Change directories to J2EE_HOME/applications/reim/WEB-INF/lib 3. Extract the file services_platform.xml from platform-conf.jar. Copy the xml file to

J2EE_HOME/applications/reim/WEB-INF/classes/retek.

Example: jar –xf platform-conf.jar retek/services_platform.xml

4. Extract the file services_rsm.xml from rsm11-api.jar. Copy the xml file to J2EE_HOME/applications/reim/WEB-INF/classes/retek.

Example: jar –xf rsm11-api.jar retek/services_rsm.xml

Oracle Retail Allocation and Oracle Retail Invoice Matching

Appendix: Customizing Navigator to Integrate with Other Oracle Retail Applications 25

5. Edit the reim.properties file located at J2EE_HOME/applications/reim/WEB-INF/classes/com/retek/reim/ changing the sso_url parameter to reflect the RSM WebSphere server and RSM bootstrap port.

Example: sso_url=iiop\://server\:bootstrap_port

6. Add a record in both the IM_USER_AUTHORIZATION table and IM_BUSINESS_ROLE_MEMBER table. The user created must exist and match exactly (case sensitivity must be taken into account) with the user in the RSM directory service.

Allocation 1. Edit the allocation.properties file located at J2EE_HOME/applications/alloc/WEB-

INF/classes/com/retek/alloc/ changing the sso_url parameter to reflect the RSM WebSphere server and RSM bootstrap port.

Example: sso_url=iiop\://server\:bootstrap_port

2. Add a record in both the ALC_USERS table and ALC_USER_DEPTS table. The user created must exist and match exactly (case sensitivity must be taken into account) with the user in the RSM directory service.

3. It may be necessary to extract the services_platform.xml and services_rsm.xml files as in steps 1 – 5 from Invoice Match above.

PrefaceAudienceRelated DocumentsCustomer SupportConventions

Hardware and Software RequirementsDatabase ServerApplication ServerClient PC and Web Browser RequirementsClient PC RequirementsBrowser Requirements

Database Configuration InstructionsApplication Server Configuration InstructionsUNIX (Sun Solaris/HPUX/AIX)Configure WebSphere 5.1.1.10 Application Server for Navigator 11Deploy Navigator.ear in WebSphere Application Server 5.1.1.10Customize Necessary Configuration and Properties FilesStart Retek Navigator 11.2

Client Installation InstructionsDeploying the JNLP Web ApplicationDeploy jnlpgen.war in WebSphere Application Server 5.1.1.10

Test the Navigator Client and Jnlpgen ServletNavigator Client

Appendix: Customizing Navigator to Integrate with Other Oracle Retail ApplicationsRMS Based ApplicationsRDW ApplicationsCategory ManagementCustomer WorkbenchMerchandise Workbench Store Operations

Oracle Retail Allocation and Oracle Retail Invoice MatchingInvoice MatchingAllocation