How to generate debug log files for Oracle iStore in Release 11i.
This feature creates separate user log files for both the Java Layer (middle tier) and PL/SQL (database tier) layers.
I. Initial Setup Requirements
The following steps are required to be able to log the debug information.
1. Ensure the Logging Parameters are set:
a. Go to the $APACHE_TOP/Jserv/etc directory and open the jserv.properties file
b. Ensure the following parameters are set:
wrapper.bin.parameters=-Dframework.Logging.system.filename=/&directory/fwsys.log
wrapper.bin.parameters=-Dservice.Logging.common.filename=/&directory/ibe.log
Note:
- Replace /&directory/ with a valid directory on your server and make sure it has the proper permissions.
- This will not be the name of the log file generated from iStore, see below for the exact name of the log file.
2. Ensure the Debug Properties are turned on for the application:
a. Login to jtflogin.jsp as sysadmin user
b. Navigate to Settings > System > Advanced
c. Choose JTF from the dropdown list
d. Verify the following properties are set:
framework.Logging.system.filename -> fwsys_jtf_log
framework.Logging.system.level -> debug
service.Logging.common.filename -> jtf_log
service.Logging.common.level -> debug
service.Logging.common.mode -> file
Note:
- The two *.filename properties are to be set to a name of file, do not enter a directory.
- The directory is defined from the parameters set in the jserv.properties.
- This will not be the name of the log file generated from iStore, see below for the exact name of the log file.
3. Set the "OM: Debug Log Directory" system profile:
Set the "OM: Debug Log Directory" profile at the site level to a directory that is writable by the database server. The profile value must be one of the directories listed in the utl_file_dir parameter.
Note:
- To find the utl_file_dir value set, the following query may be executed:
select value from v$parameter where name = 'utl_file_dir'
III. Steps to Generate Debug Log Files from iStore
1. Set the "OM: Debug Level" profile to 5 at the Site level.
2. Set the "IBE : Enable Debug" and "ASO : Enable ASO Debug" profiles to Yes at the user level.
Both profiles are needed to be set as iStore will call some Order Capture API's.
2. If the problem needs Pricing information: check the "QP: Debug" profile.
- If the profile has 'No' and 'Yes' as values, set the profile to 'Yes' at the user level.
- If the profile has the 3 values regarding the Request Viewer, set the profile to 'Request Viewer Off'.
At this point, the Pricing Debug information will be generated when the "OM: Debug Level" profile is set.
3. If the problem needs the Tax information, different steps are required based on Financials Family Pack applied.
For customers who are on Financials Family Pack E/11.5.9 or lower - should set both FND Logging Profiles and Tax Debug profiles for debugging. The debug log will be generated in directory specified by profile option Tax:Debug File Directory.
4. If the problem needs the ATP information, the following steps need to be followed:
- Set the "MSC: ATP Debug Mode" profile to 'Debug Only' at the site level.
- Make sure user level is set to NULL.
- A session-* log file will be generated in the 'utl_file_dir' directory.
5. Open a new browser window and replicate the issue in iStore.
6. Unset the profiles to stop the debugging.
IV. Where are the iStore Debug Log files generated?
1. The iStore pl/sql log file will be generated in the directory (located in the Database Tier) specified in the Order Management 'OM: Debug Log Directory' System Profile and has the syntax of IBE_.log
2. The iStore java layer log file will be generated in the directory specified in the 'Dframework.Logging.system.filename' JVM parameter of your Middle Tier (See section II step 1) and has the syntax of IBE__.log
Note:
Based on the action being done, there might also be a Quoting debug log file generated in the same directory which will have the following syntax: QOT_.log
Make sure to upload the iStore debug log file and the Quoting if one was generated.
V. Generating Configurator Log Files from iStore
If Configurator is involved in the replication steps, some configurator log files can (and should) be obtained for further debugging.
VI. Generating Debug Log Files as the guest user
To generate the iStore debug log files while you are the guest user, you will just need to append '?&log=t' (without the single quotes) to the end of the URL before the step you want to debug while you are the guest user.
There is no need to set all profiles from section III.
For example: http://:/OA_HTML/?&log=t
This will generate both log files for any actions done in the browser after that. It is not necessary to append the parameter again for that session.
Once you close the browser, it stops the debugging. If new browser is started and append the parameter again, it starts a new set of log files.
The logs will be generated the same way for the guest user:
1. The pl/sql file name will have a syntax of "IBE_.log" and be generated in the directory specified in the "OM: Debug Log Directory" system profile.
2. The java layer file name will have a syntax of "IBE__.log" and be generated in the directory specified in the 'Dframework.Logging.system.filename' parameter of the jserv.properties.
VII. Generating Debug Log File from the iStore Administration UI
Starting from iStore version 11.5.9 , a debug log file can be generated from the iStore Site Administration User Interface.
Login to the Application Forms and set the following System Profiles at the user level to the following values:
Profile Name Value
FND: Debug Log Enabled Yes
FND: Debug Log Module %
FND: Debug Log Level Statement
FND: Debug Log Filename /ibe_admin.log
Note: Replace with the value entered for the "OM: Debug Log Directory" profile.
-> The log file will be called ibe_admin.log and be located in the directory specified in the path entered in the 'FND: Debug Log Filename' profile.
Monday, February 11, 2008
How to generate debug log files for Oracle iStore
Implementing Oracle iStore
High Level process to implement iStore
--> Setup istore Administrator and concurrent Administrator
* Create a fnd_user (IBE_ADMIN) with responsibility iStore Administrator Responsibility and set the profile options
• FND: Branding Size
• 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
--> Setup guest User
* Query for Guest user in fnd_user and set the responsibility - IBE_CUSTOMER
• JTF_PROFILE_DEFAULT_APPLICATION -- 671 (for iStore)
• JTF_PROFILE_DEFAULT_CURRENCY -- US
• JTF_PROFILE_DEFAULT_RESPONSIBILITY -- 22372 (for IBE_CUSTOMER)
--> Setup Mandatory profile option -- Only some of them are mentioned here, please refer Implementation guide for all mandatory profile options
Set the profile options at application level
• IBE: Category Set --> Inventory Category set
• IBE: Item Validation Organization --> Master Inventory organization Id
• IBE: Pricing Event for Shopping Cart --> Set to Batch Processing
• IBE: Create Order in Entered State--> Set to Yes
• IBE: Pricing Event --> set to Enter Order Line
• IBE: Default Payment Term
• IBE: iStore Non Secure URL
• IBE: iStore Secure URL
• MO: Operating Unit.
• ASO: Default Order Type -- Set to Mixed
• ASO: Validate Salesrep -- Set to No
Refer Implementation Guide for more options..
Introduction to Customer Application Display
--------------------------------------------
Its uses JTF MVC framework
Model - oracle PL/SQL
View - JSP
Controller - Java API
It consists of
* Display Templates
* Section and product Hierarchy
* Content
Introduction to Oracle iStore
What is Oracle iStore ?
Oracle iStore allows you to create a comprehensive web presence to collaborate with Customers, Channel partners, distributors and resellers, and to profitably support the entire sales process from lead generation to ordering, to post sales support.
It integrates fully with oracle applications to provide a complete e-commerce solutions. It enables business to
* Build, test, and launch sophisticated online stores in multiple language and currencies
* Deploy sites in business partner, business-to-business (B2B) and business-to-consumer (B2C) scenarios
* Provide a full range of online purchasing capabilities including
- Customer home page
- Flexible pricing including qualifiers, modifiers, and customer specific prices
- Credit Card security features
- Sales assistance
- collaborative purchasing (shared carts and shared quotes)
- Regular or express checkout
- Shopping list and direct item entry
- Address defaulting into carts
- Services
- Promotional goods
- User maintenance by administrative customer users
- Order Tracking, Cancellations, returns, and access to customer installbase
It consists of two distinct integrated user interface,
1. Site Administration Applications
- Create and maintain unlimited number of sites
- Setup site business rules, such as price lists, payments and shipping methods
- Build product catalogs
- Change site look and feel
- view and configure oracle workflow notifications
2. Customer Applications
- Online Shopping with order processed in OM
- Configure complex products
- Save carts, quotes and lists
- Share and retrieve carts and quotes
- Track orders
- Cancel orders
- View Installbase items
- Submit return orders
- Store and access user address and credit card data
Oracle iStore - Frequently Asked Questions (FAQ)
1. Cart Vs Quote
A cart / quote contains products that you have configured and/or the spare models that you have added to the shopping cart in the web store. The basic difference between a cart and a quote is that a quote has been through the Sales Assistance process.
2. Where is current active cart information stored?
IBE_ACTIVE_QUOTES_ALL table will have details of active cart for each user
3. When an Item is added to the cart, what will happen in background?
Cart will be created in ASO_QUOTE_HEADERS_ALL table with status_code as 'iStore Draft'
4. When a Cart is converted Quote?
Incase if a cart is requested for sales assistance, new version of cart will be created in ASO_QUOTE_HEADERS_ALL with status_code 'Draft'
5. How to remove the checkout button
Remove the permission - IBE_CHECKOUT and IBE_CREATE_ORDER
6. Incase if an item is not visible after adding to the catalog, what would be the problem ?
Verify the Item web properties orderable on web and published flag enabled in the item master
7. What is the process to customize the jsp in iStore ?
i. Copy the jsp and rename it to the custom name
ii. Do the changes and copy back to $COMMON_TOP/html
iii. Map the Jsp source file in the display manager template
8. What are basic tables affected when we create a cart / quote ?
i. ASO_QUOTE_HEADERS holds Order Capture quotation information. it has the header data of a quote. For each quote header, there can zero or many quote lines attached to it
ii. ASO_QUOTE_LINES_ALL stores information for a typical quote or an order line. This includes the item, item organization, unit of measure, quantity ordered, price list etc. The ITEM_TYPE column specifies what kind of item is quoted for this line. Each quote line can have zero or many detail lines in ASO_QUOTE_LINE_DETAILS_ALL, which stores specific line information about certain item types (e.g. service, configuration details)
iii. ASO_QUOTE_LINE_DETAILS_ALL stores information specific to certain types of quote lines. This includes service related attributes, model/option related attributes and return related attributes
iv. ASO_LINE_RELATIONSHIPS links one quote line to another and records the type of relationship. The reciprocal flag indicates if the relationship is bidirectional
v. ASO_HEADER_RELATIONSHIPS links one quote to another and records the type of relationship. The reciprocal flag indicates if the relationship is bidirectional.
vi. ASO_QUOTE_LINE_ATTRIBS_EXT to extend the more attribute fields
vii. ASO_PRICE_ATTRIBUTES stores information on qualifiers and pricing attributes, which the corresponding price adjustment line qualified for.
viii. ASO_PRICE_ADJUSTMENTS stores price adjusment details
ix. ASO_TAX_DETAILS stores quotes tax details
x. ASO_PAYMENTS holds payment related information for the quote
xi. ASO_SHIPMENTS store shipping information for a quote at header level or line level. At header level means the shipping information is the same for all the quote lines, therefore the quote_line_id is null. At line level means each line has its own shipping information. At line level, it can further break down at line quantity level if the quantity in ASO_SHIPMENTS is different than in ASO_QUOTE_LINES_ALL.
xii. ASO_QUOTE_RELATED_OBJECTS stores the relationship between a quote or a quote line to any entity in the schema and records the type of relationship. The OBJECT_TYPE_CODE defines the type of entity the quote or quote line is related to, and the OBJECT_ID is the unique identifier of the related object.
xiii. ASO_QUOTE_STATUSES_B stores the pre-defined and user-definable statuses for a quote header or a quote line
xiv. IBE_QUOTE_ACCESS stores information about who can share the Shopping cart (Quote). The information stored also include Update Privileges to be given to the sharee.
9. What are the required Inventory Flags for Oracle iStore Products ?
* Web Status Flag - Set this flag to Published in Inventory Master Form, Web Option tab - Published / Unpublished
* Orderable on the Web - Select the checkbox in Inventory Master Form, Web Option tab
* Customer Orders Enabled - Set the flag orderable by customer in Inventory Master Form, OM tab
* OE Transactable - Set this to Yes in order managment attributes group
Sunday, October 14, 2007
How to Ensure that New Business User Approval Goes To Primary User and Not To Sysadmin
Oracle iStore - Version: 11.5.10.2
Information in this document applies to any platform.
Goal
The newly registered business user SHOULD appear in the primary users list of people to approve, but does not.
Here are the steps to explain the requirement clearly :- Step 1 : A person has created an account for a new organisation, and are approved as the primary user. Following are the steps: 1. A person (lets call him 'Alex')clicks "Register as a user of an existing organization". 2. Alex enters all the mandatory details. (e.g name, address...)3. Alex clicks submit4. Alex is then advised that access is pending approval.
5. Primary User then logs in to his iStore account
6. The primary user then navigates to the Pending Approval page
7. The primary should see 'Alex' as a user pending approval. 8. 'Alex' IS NOT IN THE LIST ON USERS PENDING APPROVAL.
Now: 9. SYSADMIN logs in and selects CRM HTML Administration
10. Navigates to User Management
11. Navigates to Pending Approvals.
12. 'Alex' IS IN HIS LIST OF USERS PENDING Approval. So in summary point '8' is the requirement.
The new user SHOULD appear in the primary users list of people to approve, but does not.
Solution
Create BUSINESSUSERAPPROVER user. System Administrator>Security>User>define Assign a dummy email address Save (User requires no responsibilities) Assign BUSINESSUSERAPPROVER with the JTF_APPROVER role CRM HTML Administration>Users>Registration>User Maintenance Search for BUSINESSUSERAPPROVER Click BUSINESSUSERAPPROVER link Click Roles Locate the ‘JTF_APPROVER’ role and assign to BUSINESSUSERAPPROVER Click Update Set BUSINESSUSERAPPROVER user as approver CRM HTML Administration>Users>Setup>Approval Setup>Default Click ‘JTF User Approval’ Click ‘Next’ Remove all approvers (SYSADMIN may be listed by default) Search for and add BUSINESSUSERAPPROVER to list Enter an Order of ‘1’ Click Submit Set JTF_PRIMARY_USER System Administrator>Profile>System Search for JTF_PRIMARY_USER profile Set BUSINESSUSERAPPROVER at site level Save NOTE: Do not use SYSADMIN as approver. It is necessary to create a BUSINESSUSERAPPROVER as defined above.
How to Create a Simple Specialty Store with Vision 11i
This note will teach you through the following setup to create a specialty
store using the Vision Demo for 11i:
1. Create a specialty store called Vision Store.
2. Define multimedia for the product, Sentinel Standard Desktop and for a
subsection called Computer.
3. Build the Vision Store hierarchy with a section called Vision Store and
a subsection called Computer.
4. Add the Sentinel Standard Desktop, AS54888, to your Vision Specialty
Store Computer section.
5. Associate multimedia to the Computer section and to your item.
This document will use the following values and filenames.
Name of Specialty Store: Vision Store
Name of Section: Vision Store
Name of Subsection: Computer
Name of item to add: Sentinel Standard Desktop, AS54888
Name of large image that represents the item: AS54888_large_image.gif
(must exist in $OA_MEDIA)
Name of large item multimedia component: Item Large image
Name of small image for Computer section: COMPUTER_SECT_small_image.gif
(must exist in $OA_MEDIA)
Name of section small image multimedia component: Section small image
This document refers to iStore administration by logging as
ibe_admin/manager at the following URL:
http://hostname.domain:
This document refers to the iStore storefront by accessing the following URL.
The iStore store is composed of one or more Specialty Stores called minisites.
http://hostname.domain:
How to create a simple specialty store with Vision 11i
------------------------------------------------------
Part I. Creating a minisite
This step updates JTF_MSITE_TL and JTF_MSITE_B tables. You are creating a
minisite entity.
This step is the first step in many to create a Specialty Store.
You will not have a functioning Specialty Store after completing this step.
1. Log on to iStore administration as ibe_admin/manager.
2. You should be in the Setup region. If not, click on the Setup tab.
3. Click on create tab in the Specialty Stores page.
4. Provide a name for your Specialty store such as Vision Store
5. Provide a description.
6. Check the Enabled for Store box. (If you don't check this, you will not get
the wizard setup and you have to manually access the Specialty Store menus
by clicking the hyperlinks in the Specialty Store Detail Page).
7. Scroll down to bottom of page and select the default Language from the pull
down menu.
8. Click on continue.
9. From the pull down menu at the bottom of the Business Unit page.
(jtfmmbas.jsp), select Vision Operations as the default organization.
10. Click on continue.
11. In the Store Flags page (jtfmmflg.jsp), ATP enabled is not a option at
the store level. ATP is only available at the item level.
12. Select Yes from the Walkin Customers Enabled pull down.
13. Click on GO next to the Root Section.
14. Highlight the Home folder in the applet window. This attaches your
store to the hierarchy with a root name of Home.
15. Click on Done in the applet window.
16. Click on continue.
17. Check the US dollar currency in the Currencies and Price Lists page
(jtfmmflg.jsp)
18. Select the Corporate Price list for the Walkin Customer, Registered
Customer and Business Partner Price List.
19. Select default currency as US dollar.
20. Click on continue.
21. Your Specialty Store is created and you will be returned to the
Specialty Store main page.
Part II. Defining Multimedia
iStore provides 3 canned multimedia setups:
· Store item large image (default multimedia for Multimedia component
Item large image)
· Store item small image (default multimedia for Multimedia component
Item small image)
· Store section small image (default multimedia for Multimedia component
Section small image)
You will be creating Multimedia for the Multimedia Component Item large
image for the Sentinel Standard Desktop with source file name
AS54888_large_image.gif.
1. Check to make sure that AS54888_large_image.gif exists under
$OA_MEDIA on the forms/web node.
2. Click on the Multimedia tab.
3. Click on the Create button in the upper right corner.
4. Provide a name for the multimedia. Try to follow a standard naming
convention such as "Productname Size Type", i.e., AS54888 large image.
5. Provide a programmatic access name. Try to follow a standard naming
convention such as "PRODUCT_SIZE_TYPE", i.e., AS54888_LARGE_IMAGE.
6. Choose "category" from the pulldown menu for "Displays".
7. Provide a default source file for your multimedia:
/OA_MEDIA/AS54888_LARGE_IMAGE.gif.
8. Provide a description for the image: Large image for AS54888.
9. Click on Update.
10. Click on the hyperlink source file name in the Multimedia Details page.
11. Make this gif available to your minisite and provide a language
from the GO button. ????
12. Click on update.
Now create a Section small image multimedia:
1. Check to make sure that COMPUTER_SECT_small_image.gif exists
under $OA_MEDIA on the forms/web node.
2. Click on the Multimedia tab.
3. Click on the Create button in the upper right corner.
4. Provide the name, Computer Section small image, for the section multimedia.
5. Choose "section" from the pulldown menu for "Displays".
6. Provide a default source file for your multimedia:
/OA_MEDIA/COMPUTER_SECT_small_image.gif.
7. Provide a description for the image: Small image for Computer section.
8. Click on update.
Part III. Defining Multimedia Components.
Defining Multimedia Components gives you a generic bucket to which your
multimedia belong. You can create multimedia components needed for
different facets of your store such as logo, thumbnail image, etc. \
When creating a Multimedia Component, you can assign an existing
multimedia (from part II) as your default multimedia. You are provided
with 3 canned multimedia components:
· Item large image: used to associate an image to the item on the item
detail page, ibecitmd.jsp. Default image is product_large_image.gif.
· Item small image: Default image is product_small_image.gif
· Section small image: used to associate an image to a section page,
ibeclfsm.jsp. Default image is section_small_image.gif.
You will need to decide if your store structure will need another
multimedia component. You can work with the canned multimedia components
for this document. Creating another multimedia component is not necessary
right now.
Part IV. Define Display Styles.
Display styles represent a particular style for displaying products.
There are 3 display styles available out-of-the-box:
· STORE_PRODUCT_DETAIL
· STORE_PRODUCT_SMALL_DESCR
· STORE_FEATURE_PRODUCT
For the purpose of this document, you will not need to create a new display
style. This will be the subject of another document.
Part V. Define Hierarchy
A hierarchy consists of navigational sections and feature sections. The end
of a hierarchy branch is the products you want to sell. You can not have
products and section at the same node level. In order to have products sold
at the section level, you will need to use a feature section.
Feature section will be the subject of another document. A hierarchy
structure belongs to the entire store. You create speciality
stores that include/exclude the sections of the store.
1. Click on Hierarchy tab.
2. Highlight the root of the hierarchy, Home, in left frame.
3. Click on the Create button above Home.
4. Provide the name of your section, i.e., Vision to match the name of your
specialty store.
5. Keep section type a navigational.
6. Click on Continue.
7. Click on Continue since you will not be assigning an image to this
section level.
8. Select the Minisite, Vision, for your included Specialty Store.
9. Click Continue.
10. Click on Continue in the Relationship page.
11. Click on Finish in the Advanced Settings page.
12. Click on Refresh in the Hierarchy left frame.
13. With your new section highlighted in the left frame, create another
section by clicking the Add Section button in the right frame.
14. Provide a name such as "Computers" for the subsection of your Vision
section.
15. Keep this section type as navigational.
16. Click on Continue.
17. Assign the small section image multimedia name that you created in
Part II to this subsection by clicking on the Go button next to Section
small image.
18. Click on Continue.
19. Confirm the included specialty store and click continue.
20. Click on Continue in the Relationship page.
21. Click on Finish in the Advanced Settings page.
Part VI. Adding a product to a section.
1. Click on the Hierarchy tab.
2. Expand the Hierarchy in the left frame until you get to the section that
you want to contain products.
Home --> Vision --> Computers
3. Click on Add product in right frame. An applet window will pop up.
4. Choose part number in the pulldown menu and place a % in the text box.
5. Click on Go.
6. Select Sentinel Standard Desktop.
7. Click on Done at the bottom of the applet window.
Part VII. Assigning multimedia to a product.
1. Click on the hierarchy tab.
2. Expand your section under the root Home in the left frame until you get
to your product section.
3. Click on your hyperlinked item name.
4. Click on the Multimedia components hyperlink.
5. Click on the blank radio button next to the item large image and press GO.
6. Click on the Multimedia name for AS54888.
7. Click on update.
Part VIII. Test your store.
1. Bounce the Apache server.
2. Go to the store front URL and click on your minisite name, Vision Store.
3. Navigate to your product and see if the image and price exist for your
product.
Tuesday, May 09, 2006
Oracle iStore
How to set JDeveloper 9.0.3.4 for iStore
This is the corrected document as required during implementation:
Oracle JDeveloper can be used to customize and extend Oracle iStore. The setup procedure for JDeveloper to run iStore middle-tier (java/JSP layer) on Microsoft Windows 2000 is documented below.Assumptions:1. JDeveloper version 9.0.3.4 is installed. (otn download link)2. iStore middle-tier is setup correctly on Unix/Linux environment.Note: This document uses to represent the directory location in which JDeveloper was installed. For example, if JDeveloper were unzipped in c:\jdev9i, the would be c:\jdev9i.Step 1: Setup Workspace and Project in JDeveloper1. Start JDeveloper: \jdev\bin\jdevw.exe2. Create or reuse a workspace and a project. The workspace is iStore.jws and the project is iStoreProject.jpr.3. Keep default project properties. Example: HTML root directory: \public_htmlNote: represents C:\myprojects\ directory.Test 1: Create, Compile and Run a Test JSP Page1. Create a new JSP page with static text message – the JSP page is created in HTML root directory. Compile and run – the text message should appear on a browser window.Step 2: Copy iStore FilesiStore JSP files and java classes will be installed under subdirectory. Copy iStore files from Unix/Linux environment as follows:Note: Copy $COMMON_TOP/java/oracle/apps/* into and add it to the project library in JDeveloper. No need to copy files into the classes directory.Also copy the following java classes to the \classes directoryCopy jtfincl.jsp, jtfsctp.jsp and jtfucss.css from $COMMON_TOP/html into \public_html\OA_HTML. Copy more files as and when needed. Remove language="java" attribute from @page directives in jtfincl.jsp. Remove directive from jtfincl.jsp. Remove directive in ibeCCtdMenu.jsp.
