Oracle WEBADI - BNE Admin Servlet & Debug

BNE Servlet helps you to clear cache, you can view log-First, log-last, log-search options, I have explained below

For 11i
http://hostname:portnumber/oa_servlets/oracle.apps.bne.framework.BneAdminServlet

For R12
http://hostname:portnumber/OA_HTML/BneAdminServlet

Note :- It’s always better to login using system administrator in first tab then open above URL in next tab are same window, so that you no need to re-enter credentials


With BNE Servlet you can clear the BNE cache, click the "clear-cache" link.
You can also monitor the size and location of your log file, or change the log level.

Valid arguments to BNE servlet


bne:action= log-all | log-first | log-last | log-marker | log-search
Additional Option: bne:lines = <number> (defaults to 100 if not set)
Additional Option: bne:text = String (useful for searching or marking the log file)
bne:action= log-set-level (Current JVM only)
Required Option: bne:log-level=REQUIRED | CRITICAL ERROR | ERROR | WARNING | INFORMATION | DETAIL | TRACE

bne:action= cache-clear (Current JVM only)
bne:action= site-properties-clear (Current JVM only)
bne:action= async-uploads (all async uploads started in the last 24 hours)
Additional Option: bne:async-job-number = number (Report on a particular job)
Additional Option: bne:action2=upload-cancel (Cancel a particular job)
bne:action= delete job history (clear job history > 7 days old)
bne:action= delete performance statistics
bne:action= threads (Current JVM only)

In R12 oracle provided default options, once BNE servlet opens you can choose whatever you want, if you are looking any specific option simply you can modify your URL based on above arguments.


To Clear BNE cache:
A. Releases prior to 12.2.7

Using System Administrator responsibility:
  1. Login to the application as a user with System Administrator Responsibility.
  2. Select the System Administrator Responsibility.
  3. Bring up the AdminServlet by changing the URL in the browser where you are logged into the applications keeping the appropriate hostname.domain and port number.
  4. Release 11i:
    http://hostname.domain:portnumber/oa_servlets/oracle.apps.bne.framework.BneAdminServlet
    On the new web page that loads, scroll down and click the "clear-cache" link
  5. Release 12.0 - 12.2.6:
    http://hostname.domain:portnumber/OA_HTML/BneAdminServlet
    On the new web page that loads, scroll down to the Cache Name section.
    Clear the cache for the following by clicking the "(clear)" link:

    Cache Name
    ============
    Default Cache
    Generic SQL Statements
    Web ADI Repository Objects
    Web ADI Parameter Lists
    Web ADI Parameter Definitions
The BNE cache is now cleared.
B. Release 12.2.7 and higher
Access to the BneAdminServlet is now secured by the function WDF_CREATE_INTEGRATOR (Desktop Integration Manager - Create Integrator).
Note: WDF_CREATE_INTEGRATOR is included in the seeded responsibility Desktop Integration Manager.
  1. Login to the application.
  2. Select the Desktop Integration Manager responsibility or a responsibility that includes the function WDF_CREATE_INTEGRATOR.
  3. Proceed as in step 5 for release 12 above.

This action is similar to clearing the Apache cache and does not need to be performed first on a
non-production instance. It does not require a bounce of Apache or downtime.

Debugging
You can get a log file to help diagnose an error in Web ADI. The following profile options need to be set:
BNE: Server Log Filename: Use this profile option to change the name of the Web ADI log file on the middle tier. If this profile option is not set, bne.log is used.
BNE: Server Log Path: This profile option can be used to set the directory for the Web ADI log file on the applications server. If this profile option is not set, then the FND_TOP/log directory is used.
BNE: Server Log Level: This profile option determines the level of detail that is recorded in the Web ADI log file. The valid values are noted below. The level of granularity and amount of information recorded to the log file increases as you move down the list.

Pre-req
For Microsoft Excel 2002 or 2003:
1.From the Tools menu, select Macro, then Security, and then Security Level.
2.In the Security Level tab, select the High option.
3.In the Trusted Sources or Trusted Publishers tab, select the Trust access to Visual Basic Project option.

For Microsoft Excel 2007:
1.Choose the Microsoft Office button, and then choose Excel Options. In the Trust Center category, choose Trust Center Settings, and then the Macro Settings category.
2.Select the Disable all macros except digitally signed macros option.
3.Select the Trust access to the VBA project object model option.

Set profile option 'BNE Allow No Security Rule' to Yes at user level. The default value is No.
Add responsibilities 'Desktop Integration Manager', 'Desktop Integrator' to the current user.

  • CRITICAL_ERROR: - Messages that are the result of a system failure. The integrity and reliability of the system is in doubt as a result of this error.
  • ERROR: - Messages that are the result of an unexpected error in the system. It is possible to recover from these errors; the system may still be in a usable state. Setting the profile option to this value will include CRITICAL_ERROR messages in the log file.
  • WARNING: - Messages trapped by the application.These errors were handled by the application but the system administrator should be aware of them occurring. Setting the profile option to this value will include ERROR and CRITICAL_ERROR messages as well.
  • INFORMATION: - Additional messaging is added to the log file that includes processing information. Setting the profile option to this value includes CRITICAL_ERROR, WARNING, and ERROR log messages. This is the setting that is used by Web ADI if the profile option is not set at the site level.
  • DETAIL: - Messages that summarize what is written to the log file. Setting the profile option to this value includes CRITICAL_ERROR, WARNING, ERROR, and INFORMATION log messages.
  • TRACE: - Messaging that generated detailed debugging statements. Setting the profile option to this value includes CRITICAL_ERROR, WARNING, ERROR, INFORMATION and DETAIL log messages.

Main Tables and API

BNE_INTEGRATORS_TL
BNE_INTERFACES_TL
BNE_INTERFACE_COLS_TL
BNE_CONTENTS_TL
BNE_MAPPINGS_TL
BNE_LAYOUTS_TL
BNE_LAYOUT_COLS

API to create custom web ADI programmatically..
BNE_INTEGRATOR_UTILS.CREATE_INTEGRATOR
BNE_INTEGRATOR_UTILS.CREATE_INTERFACE_FOR_API
BNE_INTEGRATOR_UTILS.CREATE_DEFAULT_LAYOUT
BNE_INTEGRATOR_UTILS.CREATE_TABLE_LOV
BNE_INTEGRATOR_UTILS.CREATE_CCID_KFF
BNE_INTEGRATOR_UTILS.CREATE_JAVA_LOV

Comments

Post a Comment

Popular posts from this blog

Oracle BI Publisher Tags For-each grouping for Matrix report

For-Each Extensions For-each tags can be confusing.  We will be going over the following tags:     For-each@ section :    For-each@ cell   For-each- group :   field1; field2;     For-each-group: current-group() ;field3;   For-each-group@ column       Sample XML:  <CORPORATION>      <NAME>Vision</NAME>     <DEPT>     <DEPT_NAME>IT</DEPT_NAME>      <EMPLOYEE>         <EMPNO>6</EMPNO>        <ENAME>Rich Walker</ENAME>        <JOB>CLERK</JOB>        <SAL>100</SAL>     </<EMPLOYEE>>     <EMPLOYEE>        ...
Read more

SQL Scripts for Custom Table Creation in Oracle Application 12.2.x

Due to introduction of Online Patching, Post 12.2.x version, there are certain steps to be followed while creating Custom Table. 1. For new table creations - after creating the table in custom schema execute below script to generate edition view and synonym for it in APPS schema. exec AD_ZD_TABLE.UPGRADE('xxcust_schema','xxcust_Table'); 2. For table alterations - after running the DDL run below script to regenerate the edition view for synchronizing any table changes. exec AD_ZD_TABLE.PATCH('xxcust_schema','xxcust_table') 3. Table grants must be done through API to avoid invalids. exec AD_ZD.GRANT_PRIVS('SELECT','xxcust_table,'xx_role') 4. To view objects in all editions, add "_ae" to the data dictionary views select * from user_objects_ae; 5. To update seed data tables in Patch edition, execute prepare command. example:  exec ad_zd_seed.prepare('WF_MESSAGES');  The prepare Procedure will creat...
Read more

Oracle Fusion Business Intelligence Roles

Oracle Business Intelligence roles apply to both Oracle Business Intelligence Publisher and Oracle Fusion Transactional Business Intelligence. They grant access to Business Intelligence functionality, such as the ability to run or author reports. These roles are in addition to the roles that grant access to reports, subject areas, Business Intelligence catalog folders, and HCM data. This topic describes the Business Intelligence roles. This table lists the Business Intelligence roles. Business Intelligence Role Description BI Consumer Role Runs Business Intelligence reports. BI Author Role Creates and edits reports. BI Administrator Role Performs administrative tasks such as creating and editing dashboards and modifying security permissions for reports, folders, and so on. BI Publisher Data Model Developer Role Creates and edits Business Intelligence Publisher data models. BI Consumer Role The predefined Transactional Business Intelligence Transacti...
Read more