Skip Headers

Oracle iStore Implementation and Administration Guide
Release 12.1
Part Number E13575-08
Go to Table of Contents
Go to previous page
Go to next page

Implementation Tasks for Oracle iStore

This chapter covers the following topics:

Overview of Implementation Tasks Chapter

This chapter describes the tasks required to set up Oracle iStore after you have verified your installation and dependencies.

Setting up the Site Administration Application

Your initial setup of the Oracle iStore Site Administration Application involves setting required profile options, creating administrative users, and testing the Site Administration Application.

Required tasks include:

Set Initial Profile Options

Set up by the System Administrator in Oracle Applications (Forms), profile options control the behavior of all Oracle Applications. Nearly every Oracle Applications profile option begins with a 2- or 3-letter code that is tied to the application or functionality group which it controls.

All Oracle iStore profile options begin with the prefix IBE.

Initially, you must set some Oracle CRM Technology Foundation (JTT) and Oracle iStore (IBE) profile options to enable Oracle iStore's Site Administration Application. These profile options must be set before the Site Administration UI can be launched.

For more information about Oracle Applications profile options in general, see Oracle Applications System Administrator's Guide.

Set Oracle Applications CRM Profile Options

The following Oracle CRM Technology Foundation profile options must be set:

For more information, see the section, "Foundation Profile Options for HTML UI Setup", in the appendix, Profile Options.

Set iStore Site Administration Application Profile Options

Before the Site Administration Application will display, you must set the following Oracle iStore (IBE) profile options at the iStore application level:

For more information, see the section, "Foundation Profile Options for iStore Administrator User", in the appendix, Profile Options.

Set Multi-Org Profile Options

For multiple-organization architecture, set and/or verify the setting of the profile option, MO: Operating Unit. For more information, see the section, "Customer UI Mandatory Setup Profile Options", in the appendix, Profile Options.

For more information on multiple organization architecture, see the chapter, Globalization and Multiple-Organization Architecture, and the latest version of Multiple Organizations in Oracle Applications.

Set up Administrators

You must create a site administrator (referred to as store manager in previous releases) who will set up and test the sites in the Site Administration UI. See the section, "Set up iStore Administrator", below, for more information.

You also must create a concurrent programs administrator who will run concurrent programs. Initiated through Oracle Forms, concurrent programs are system programs that refresh certain data in the database. See the "Set up Concurrent Program Administrator" section, below, for details.

When a user with the iStore Administrator responsibility logs in to the Oracle CRM Login Servlet at: http://host:port/oa_servlets/oracle.apps.jtf.base.session.CRMLogin, the Site Administration Application opens.

Both the iStore Administrator and iStore Concurrent Program responsibilities are supplied for Oracle iStore. Users with these responsibilities receive all the required menus and privileges to manage sites and run Oracle iStore concurrent programs.

The menu assigned to the iStore Administrator responsibility is named iStore Merchant user root menu (IBE_M_USER_ROOT).

Set up iStore Administrator

To set up a user account for the Oracle iStore site administrator, access the Users window in Oracle Forms (log in as System Administrator responsibility and select Security, User, Define).

After you create the user, set the following profile options at the user level:

See the section, "Foundation Profile Options for iStore Administrator User", in the appendix, Profile Options, for more information.


Use the following guidelines to assist you in this task:

Set up Concurrent Program Administrator

To set up the iStore concurrent programs administrator, access the Users window in Oracle Forms (log in as System Administrator responsibility and select Security, User, Define). You can either add the concurrent program responsibility to the iStore administrator created above, or create a new user with the concurrent programs responsibility. Both methods work --- which avenue you take depends upon your business needs.

After creating a new user or updating an existing one, set the following profile option and parameter at responsibility level to the iStore Concurrent Programs Responsibility and any other Oracle iStore concurrent program manager responsibility being used. In a multiple operating unit environment, the concurrent program manager responsibility's profile option values should match the customer responsibility's profile option values for each operating unit.

For information on the above profile option and parameter, refer to the appendix, Profile Options.


Use the following guidelines to assist you in this task:

Launch the Site Administration Application

All site creation tasks are performed in the Site Administration Application. You can enter the Site Administration Application by logging in to: http://<host>:<port>/oa_servlets/oracle.apps.jtf.base.session.CRMLogin with a user name that the system administrator has set up as an Oracle iStore site manager user account. See the "Set up Administrators" section for more information on creating a site manager user account. Verify that cookies are enabled for your browser before accessing the Site Administration Application.

Accessing the iStore Administrator's Profile Pages

On any page of the Site Administration Application, the site administrator can select the Profile icon to access his Oracle CRM user profile page. Use the Profile pages to update personal information and set preferences. See the Oracle Applications CRM System Administrator's Guide for more information.

Modifying Merchant Functions

If you need to modify the functions that the site manager can perform, follow these steps:

  1. Create a new responsibility for the user in the Application Object Library (AOL) module. For the new responsibility, you can assign the default menu, iStore Merchant user root menu (IBE_M_USER_ROOT), and still remove access to some of the tabs ("functions" in AOL terminology), or you can create a new menu using the Oracle iStore functions. All Oracle iStore functions can be found by searching for IBE_M_% in the Form Functions window.

  2. In order to complete the menu setup (when creating a new responsibility) and avoid receiving an error message, you should assign both the new responsibility and the seeded responsibility, iStore Administrator, to the new user.

  3. Next, set the new responsibility as the default responsibility of the new user. Do this by setting the profile option, JTF_PROFILE_DEFAULT_RESPONSIBILITY at the user level.

See Oracle Applications System Administrator's Guide - Security for more information on creating users, managing responsibilities, and building menus.

Setting up the Customer Application

The Oracle iStore Customer Application refers to the web pages accessed by customers/users of your Internet sites from the initial landing page through checkout and order tracking.

User registration is enabled by default in your sites. For more information, see the chapter, Implementing User Management.

The page that displays when customers initially approach your site is controlled by specific combinations of profile options. You do not need to change these profile options for users to access your sites. For information on customer landing page options, see the chapter, Implementing Initial Customer UI Pages.

The basic setup for enabling the Customer Application includes:

Important: It is a prerequisite to add and activate at least one site before accessing any of the Customer Application Web pages or Site Selection Page. Otherwise, an error will occur. See the chapter, Implementing Site Management, for site creation details.

Set up Guest User Access

Setting up a guest user is required for the Customer Application to display. It also allows customers to browse your sites without registering (although you can disable guest user access at the site level). Anonymous users who visit your sites are then automatically logged in with the guest user name. If a guest user makes any changes, such as modifying the preferred language or currency, or adding items to the shopping cart, the changes are saved in the cookie so that anonymous users cannot see each other's changes. A user must register before he can place an order or view order details in Order Tracker.

Guest user is a seeded Oracle Applications (FND) user. The username and password can be found from the profile option, Guest User Password.

Use the following steps to set up the guest user account.


  1. Log in to Oracle Forms with the System Administrator responsibility and select Security, User, Define. In the Users window that opens, search for the Guest user.

  2. After finding the guest user, in the Responsibilities block, choose the seeded Oracle iStore customer responsibility, IBE_CUSTOMER, from the Responsibility LOV.

  3. Save your changes.

  4. Set the following profile options at the user level for the guest user name:

  5. Verify the guest user account, as described in the next section: "Verify the Guest User Account".

Verify the Guest User Account

Use the following procedure to verify that you have set up the guest user account correctly.


  1. Log out of any Oracle applications.

  2. Restart the Apache server.

  3. Open the Oracle iStore Customer UI at the URL: http://<host>:<port>/OA_HTML/ibeCZzdMinisites.jsp.

The page that opens should have a list of the specialty sites that are accessible to guest users.

Set Mandatory Customer Application Profile Options

Profile options control many aspects of the Customer Application. At a minimum, you must set the profile options in this section.

You can also set other Oracle iStore (IBE) profile options for the Customer Application if you do not want to use the default settings. See the appendix, Profile Options, for a complete list.

Set Mandatory Customer UI Profile Options

Enabling cookie encryption is a mandatory setup step. For additional information see Cookie Properties.

Mandatory iStore Customer Application Profile Options

Set the following mandatory IBE profile options at the iStore application level in order to configure the Customer Application. For more information, see the appendix, Profile Options.

Important: You must set these profile options for orders to be submitted properly.

Mandatory Oracle Quoting/Order Capture Profile Options and Parameters

Set the following mandatory Oracle Order Capture and Oracle Quoting profile options to configure the Customer Application. Set these at the iStore application level, unless it is stated otherwise in the descriptions. For more information, see the appendix, Profile Options. See also: Oracle Order Management Implementation Manual and Oracle Quoting Implementation Guide.

Set the following Oracle Quoting parameters:

For information on setting the parameters, see the "Oracle Quoting Integration Parameters" topic in the appendix, Profile Options.

Other Mandatory Profile Options

Also set the following mandatory profile options:

Set up Time Zone Support

Oracle iStore supports the display of time zone data in its Customer Application pages and user e-mail notifications. These features are discussed in the sections that follow.

For more information on Time Zone Support other than that found here, see the OracleMetaLink Note 330075.1, User Preferred Time Zone Support Guidelines for Applications.

Time Zone Display in Customer Application Pages

In Customer Application pages that display time-sensitive information (for example, order tracker pages), the server time zone will be displayed in text format on the page. The time zone will always be the time zone of the server running the database, and the display is retrieved dynamically using tokens. Following are examples of the text that displays:

Implementing Time Zone Display

Time zone text only display in Customer Application pages if the Oracle Applications profile option, ENABLE_TIMEZONE_CONVERSIONS, is enabled. See the Oracle Applications implementation documentation for more information.

Implementers can modify the text of the message that displays the time zone. The default text, “Time Zone ”, can be changed by modifying the Oracle Applications message, IBE_TIMEZONE_UI.

Time Zone Display in E-Mail Notifications

Oracle Workflow automatically inserts time zone information into e-mail notifications. See the Oracle Workflow Guide for more information.

Customer Time Zone Preference

Users can set their preferred time zone in the Oracle iStore Customer Application by navigating to Profile> Preferences > General. In this release, user preference will not be reflected in Oracle iStore. However, setting preferred time zone will enable users to see date/time information in their preferred time zone in other applications which support user-preferred time zone, such as Oracle iSupport.

Testing the Sites

You should verify that the Customer Application works correctly before launching your sites. See the chapter, Verifying the Implementation, for detailed steps.

Additional Implementation Tasks

After performing the required tasks in this chapter, continue your implementation by performing the following tasks, some of which are optional. The following table can guide you in your setup of Oracle iStore.

Additional Required and Optional Implementation Tasks
Task Required? Chapter
Create sites Yes Implementing Site Management
Verify or alter Customer Application initial landing page settings No Implementing Initial Customer Application Pages
Implement or verify products setup Yes Implementing Products
Set up pricing Yes Implementing Pricing
Set up the online catalog Yes Implementing the Catalog
Add content to sites No Implementing Content
Set up payment types and shipping methods Yes Implementing Payment Types and Shipping Methods
Configure carts and orders No Implementing Carts and Orders
Set up multicustomer access No Implementing User Management
Set up users Yes Implementing User Management
Set up customer assistance No Implementing Customer Assistance
Configure messages No Implementing Messages and Prompts
Set up reports No Implementing Reports
Set up global features No Implementing Globalization and Multi-Org Architecture
Set up Internet-related features No Implementing Miscellaneous Internet-Related Features
Integrate with other Oracle Applications No See the other chapters in this guide which detail how to integrate with other Oracle applications.
Implement or enable Product Comparison Yes Implementing Products