This chapter covers the following topics:
This chapter describes the tasks required to set up Oracle iStore after you have verified your installation and dependencies.
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 Administrators
Launch the Site Administration Application
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.
The following Oracle CRM Technology Foundation profile options must be set:
JTF_PROFILE_DEFAULT_APPLICATION
JTF_PROFILE_DEFAULT_BLANK_ROWS
JTF_PROFILE_DEFAULT_CSS
JTF_PROFILE_DEFAULT_CURRENCY
JTF_PROFILE_DEFAULT_NUM_ROWS
JTF_PROFILE_DEFAULT_RESPONSIBILITY
For more information, see the section, "Foundation Profile Options for HTML UI Setup", in the appendix, Profile Options.
Before the Site Administration Application will display, you must set the following Oracle iStore (IBE) profile options at the iStore application level:
IBE: Category Set
IBE: Item Validation Organization
For more information, see the section, "Foundation Profile Options for iStore Administrator User", in the appendix, 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.
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).
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:
JTF_PROFILE_DEFAULT_APPLICATION
JTF_PROFILE_DEFAULT_RESPONSIBILITY
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:
In the User Name field, enter the user name that the site manager will use to log in to the Oracle iStore Site Administration UI. An example is IBE_ADMIN.
In the Responsibilities block, choose iStore Administrator (key = IBE_ADMINSTRATOR) from the Responsibility LOV.
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.
Set the Oracle Quoting parameter Default Order Type to Mixed.
Set the profile option ASO: Validate Salesrep to No.
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:
If you are creating a new user, create the new user information and add the iStore Concurrent Programs Responsibility to the new user.
If you are using an existing user, query up the user and add the iStore Concurrent Programs Responsibility to the user.
Set the same profile option values for the iStore Concurrent Programs Responsibility as for the IBE_CUSTOMER responsibility. 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.
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.
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.
If you need to modify the functions that the site manager can perform, follow these steps:
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.
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.
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.
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.
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.
Steps
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.
After finding the guest user, in the Responsibilities block, choose the seeded Oracle iStore customer responsibility, IBE_CUSTOMER, from the Responsibility LOV.
Save your changes.
Set the following profile options at the user level for the guest user name:
JTF_PROFILE_DEFAULT_APPLICATION -- Specifies the default application ID. Set to 671 for Oracle iStore.
JTF_PROFILE_DEFAULT_CURRENCY -- Specifies the default currency. Set to U.S. or other applicable currency.
JTF_PROFILE_DEFAULT_RESPONSIBILITY -- Specifies the default responsibility for the guest user's responsibility. Set to 22372 for the IBE_CUSTOMER responsibility.
Verify the guest user account, as described in the next section: "Verify the Guest User Account".
Use the following procedure to verify that you have set up the guest user account correctly.
Steps
Log out of any Oracle applications.
Restart the Apache server.
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.
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.
Enabling cookie encryption is a mandatory setup step. For additional information see Cookie Properties.
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.
IBE: Pricing Event for Shopping Cart: Set to Batch Processing.
IBE: Create Order in Entered State, if it has errors while booking: Set to Yes.
IBE: Pricing Event--Before Shopping Cart: Set to Enter Order Line.
IBE: Default Payment Term: Set to the payment term that will be the default payment term for orders.
IBE: iStore Non Secure URL and IBE: iStore Secure URL: See the chapter, Implementing Miscellaneous Internet-Related Features, and the appendix, Profile Options, for more information.
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.
ASO: Automatic Numbering: Set to Yes at site and application levels.
ASO: Credit Card Authorization: Set to Yes if you are implementing online credit card authorization; otherwise, set to No.
ASO: Configuration Effective Date: Set to the default effective date.
ASO: Copy Configuration Effective Date: Set to the default effective date.
ASO: Default Quote Status: Set to Store Draft.
ASO: Default Order State: Set to Booked.
ASO: Enable TCA Changes: Set to Yes.
ASO: OM Defaulting: Set this to No or Yes, depending upon your configuration of Oracle Order Management and your business needs. For more information, see the section, "Setting up Defaulting Rules", in the chapter, Verify Mandatory Dependencies.
Set the following Oracle Quoting parameters:
Default Salesrep: Set to the default sales representative for sales assistance.
For information on setting the parameters, see the "Oracle Quoting Integration Parameters" topic in the appendix, Profile Options.
Also set the following mandatory profile options:
Sequential Numbering: Set to Always Used at site level. This profile option (which unlike other profile options has no product prefix, such as IBE or ASO), is required in the Oracle iStore orders process. Note that this profile also can be set to Partially Used and Not Used, but these values should not be used at site level. You may be able to set them at lesser levels. See the appendix, Profile Options, for additional guidelines on this profile.
HZ: Generate Party Number and HZ: Generate Party Site Number: Set to Yes at iStore application level, in order to auto-generate party numbers and party site numbers.
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.
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:
Time Zone (GMT +05:30)Calcutta
Time Zone (GMT –08:00/-07:00)Pacific Time
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.
Oracle Workflow automatically inserts time zone information into e-mail notifications. See the Oracle Workflow Guide for more information.
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.
You should verify that the Customer Application works correctly before launching your sites. See the chapter, Verifying the Implementation, for detailed steps.
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.
| 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 |