Oracle® Application Management Pack for Oracle E-Business Suite Guide Release 12.1.0.2.0 Part No.
Oracle Application Management Pack for Oracle E-Business Suite Guide, Release 12.1.0.2.0 Part No. E39873-01 Copyright © 2007, 2013, Oracle and/or its affiliates. All rights reserved.
Contents Send Us Your Comments Preface 1 Introduction to the Oracle Application Management Pack for Oracle E-Business Suite Overview................................................................................................................................... 1-1 2 Installing the Oracle Application Management Pack for Oracle E-Business Suite Introduction to Installation.......................................................................................................
5 Credentials Setting Named Credentials....................................................................................................... 5-1 Setting Oracle E-Business Suite Preferred Credentials............................................................5-8 Setting Preferred Credentials for Change Management........................................................ 5-11 6 Preferences Setting Preferences...................................................................................................
Running Scale-Up and Scale-Down Multi-Node Cloning Procedures................................11-19 Running Smart Clone for Oracle E-Business Suite Release 12.2......................................... 11-31 Adding Custom Steps to a Smart Clone Deployment Procedure........................................ 11-38 12 Introduction to Change Management Introduction.............................................................................................................................
Releasing and Sharing a Package......................................................................................... 14-41 Maintaining the File Metadata Repository........................................................................... 14-42 Managing Custom Applications........................................................................................... 14-44 A Target Types Target Types............................................................................................................
Send Us Your Comments Oracle Application Management Pack for Oracle E-Business Suite Guide, Release 12.1.0.2.0 Part No. E39873-01 Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products.
Preface Intended Audience Welcome to Release 12.1.0.2.0 of the Oracle Application Management Pack for Oracle E-Business Suite Guide. This book is intended for database administrators and system administrators who are responsible for performing the tasks associated with maintaining an Oracle E-Business Suite system using the Oracle Application Management Pack for Oracle E-Business Suite. See Related Information Sources on page x for more Oracle E-Business Suite product information.
5 Credentials 6 Preferences 7 Security 8 Monitoring Oracle E-Business Suite 9 Monitoring Configuration 10 Diagnosing Issues 11 Cloning an Oracle E-Business Suite System 12 Introduction to Change Management 13 Patch Manager 14 Customization Manager A Target Types B Pre-validation for Discovery C Supported File Types in Customization Manager D Customization Manager Coding Standards E Validation of Custom Applications: Examples F Known Product Limitations G Third-Party Product License Information Related Info
Oracle Enterprise Manager Cloud Control Basic Installation Guide covers basic installation procedures that help you get started with Enterprise Manager Cloud Control, the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide covers advanced installation procedures that help you install and configure the Enterprise Manager Cloud Control components in more complex environments.
record of changes.
1 Introduction to the Oracle Application Management Pack for Oracle E-Business Suite Overview The Oracle Application Management Pack for Oracle E-Business Suite extends Oracle Enterprise Manager 12c Cloud Control to help monitor and manage Oracle E-Business Suite systems more effectively. The pack integrates Oracle Applications Manager with Cloud Control to provide a consolidated, end-to-end Oracle E-Business Suite management solution.
Enterprise Manager itself allows you to monitor multiple Oracle E-Business systems (both Release 11i and Release 12) from the outside. The Oracle Application Management Pack for Oracle E-Business Suite provides advanced features to monitor and manage Oracle E-Business Suite Release 12 systems as well as Release 11i systems that meet a standard interoperability patch level.
2 Installing the Oracle Application Management Pack for Oracle E-Business Suite Introduction to Installation Oracle Application Management Pack for Oracle E-Business Suite (AMP) extends Enterprise Manager (EM) 12c Cloud Control to help monitor and manage an Oracle E-Business Suite system more effectively. This pack can be used to manage both Oracle E-Business Suite Release 12 and Release 11i systems.
Important: Uninstalling Oracle Application Management Pack for Oracle E-Business Suite is not supported. Please back up the Enterprise Manager repository before applying this management pack. Please contact Enterprise Manager Support if you need more clarification on the backup procedure. System Requirements Ensure that the following requirement has been met: • OS/User Group Requirement: It is recommended that the Oracle E-Business Suite OS user and the Enterprise Manager Agent OS user is the same.
Note: Unlike in a previous release, you do not need to install the Fusion Middleware plug-in on the agent. Installation will occur in the background during discovery. Installing and Deploying the Oracle Application Management Pack for Oracle E-Business Suite For details on deploying the Oracle Application Management Pack for Oracle E-Business Suite on the Oracle Management Server (OMS) and the platform agents, see Oracle Enterprise Manager Cloud Control Administrator's Guide.
E-Business Suite target, the plug-in will not be upgraded on that agent. For example, say in Release 3.1 you had installed the plug-in on an agent exclusively for performing check-in and check-out from source control for Customization Manager. There is no Oracle E-Business Suite target that is being monitored by this agent. During an upgrade to Release 12.1.0.2.0, this agent will not be upgraded to this latest release.
2. Search using the search term Target Type "Oracle Applications Infrastructure Service". 3. From under Oracle Applications Dashboards/Oracle Applications Service Dashboards, select -Oracle Applications Infrastructure Service Dashboard and click the Delete button. Properties in amp.properties file replaced by Preferences The amp.properties file is obsolete with this release of the Oracle Application Management Pack for Oracle E-Business Suite.
• omsPatchStageDir (OMS Stage Directory Location) • MOSEnabled/metalinkEnabled (Connect to My Oracle Support for Patches) Security using Enterprise Manager Privileges and Roles Oracle Application Management Pack for Oracle E-Business Suite now uses the native Enterprise Manager privileges and roles. As noted above, the amp.properties file is obsolete, so its security-related properties are no longer used.
3 Getting Started with the Oracle Application Management Pack for Oracle E-Business Suite Getting Started Once the management pack, or plug-in, has successful deployed on the OMS, you can go to the landing page (called as System Management Page henceforth) of the plug-in by selecting Oracle E-Business Suite from the Targets menu.
System Management Page The System Management page gives you a bird's eye view of all the Oracle E-Business Suite instances that are being monitored. This view includes status, incidents, compliance, and so on. The page has the following sections: Status of Oracle E-Business Suite Targets This section shows the status summary of Oracle E-Business Suite targets being monitored. The pie charts show how many are up, down, or in unknown status.
Oracle E-Business Suite instances are to standards. Navigating from System Management Page You can navigate to the following pages from the system management page through the Administer menu.
4 Discovering Oracle E-Business Suite with Cloud Control Preparatory Steps for Discovery Privileges needed to do discovery To discover an Oracle E-Business Suite, users must have the Add any Target target type privilege. Prerequisites to do discovery • The Oracle E-Business Suite database must be discovered in Enterprise Manager Cloud Control. • The hosts on which the Oracle E-Business Suite is deployed must be discovered in Enterprise Manager Cloud Control.
Note: For an AutoConfig-enabled Release 11i instance, running AutoConfig on the database tier adds the following lines to sqlnet.ora automatically: tcp.validnode_checking = yes tcp.invited_nodes=(11i_HOST) In this case, database discovery or application discovery through Oracle Enterprise Manager will fail because the Oracle E-Business Suite instance database tier listener will reject any connection requests other than from itself.
Adding an Oracle E-Business Suite database: 1. Navigate to Discovery Wizard. 2. Click on the Add Databases button. 3. Select the Oracle E-Business Suite database target. 4. Once added, the database target shows up in the Discovery Wizard. You can now proceed to discover the Oracle E-Business Suite instance. Prevalidating Discovery: Prevalidation allows you to analyze the Oracle E-Business Suite instance and Enterprise Manager Cloud Control to ensure successful discovery.
• Versions of target metadata For more information on these checks, see: Prevalidation Checks for Discovery, page B1. 1. To prevalidate discovery, go to Discovery Wizard. 2. Select the Oracle E-Business Suite database target and click on Prevalidate. 3. Enter the monitoring schema credentials for the database. 4. Click Prevalidate Discovery. 5. A job will be submitted to prevalidate the discovery. The Diagnostics Status column in the Discovery Wizard shows the status of prevalidation as a link.
2. Select the Oracle E-Business Suite database target and click on Discover. 3. Enter the monitoring schema credentials for the database. 4. Click Start Discovery. 5. A job will be submitted to do the discovery. The Diagnostics Status column in the Discovery Wizard will show the status of discovery as a link. You can drill down to get the details. Discovering Oracle E-Business Suite Release 12.2: 1. Set the Normal Host preferred credential where the WebLogic Administration Server is running.
4. Enter the monitoring schema credentials for the database. 5. Enter the username and password for the WebLogic Administration Server. 6. Click Start Discovery. 7. A job will be submitted to do the discovery. The Diagnostics Status column in the Discovery Wizard will show the status of discovery as a link. You can drill down to get the details.
Discovering Oracle E-Business Suite as EM_MONITOR user (Recommended) Oracle E-Business Suite can be discovered and monitored using an EM_MONITOR user which has read-only access to Oracle E-Business Suite tables required for monitoring. By default the EM_MONITOR user is locked so a user would have to unlock it explicitly to use it.
Options for Customizing Discovery 4-8 Parameter Description Applicable Oracle E-Business Suite Releases Customer Group Name All targets discovered for this instance will be grouped under this group. This group will be added to Group: Customer Group Name. All Releases Customer Instance Group Name If the Customer Instance Group Name is provided, then all the targets discovered for this instance and the Customer Instance Group Name will be added to this group.
Parameter Description Applicable Oracle E-Business Suite Releases Delete Removed Targets Whether to delete an Oracle E-Business Suite member target from OMS which was originally discovered and later detached from the Oracle E-Business Suite target hierarchy with a rediscovery. All Releases For example, say you have discovered an Oracle E-Business Suite instance with five nodes. Later you customize the discovery and exclude two nodes.
Configure column corresponding to each node. Customization at apps node level You can exclude Forms and the Apps JVM from being discovered in Release 12. Mapping Aliased Host A host which is uniquely identified by an IP Address can have different alias names in the network. It is possible that the Oracle E-Business Suite context file has one host name while it has been discovered in Cloud Control with a different alias name.
Prerequisites The operating system user who runs command-line discovery must have the full permissions on the OMS ORACLE_HOME. Before running command-line discovery, set the following environment variables: • ORACLE_HOME: This environment variable must be set to OMS Home. • JAVA_HOME: This environment variable must be set to a valid JDK directory. The OMS ORACLE_HOME ships with one under $ORACLE_HOME/jdk.
./ebsdiscovery.sh inputfile=ebsList.txt omscred=omscred.conf logdir=/tmp After the discovery job is started, you can view its status on the Oracle Management Server. From the Oracle Enterprise Manager console, navigate to Enterprise (menu) > Job > Activity. The status of the job is shown in the Status field. Click on the job name link to drill down to details on the discovered Oracle E-Business Suite instance. The ebsList.txt file The ebsList.
(;). For ENCRYPTED_PASSWORD=>, the encrypted password will be used to decrypt the password on successive usage of the ebsList.txt file. To override the old password, change the input and add APPS_PASSWORD key value pair again with the new, changed password. ebsList.txt Parameters The following table describes the ebsList.txt parameters and their valid values.
Key 4-14 Supported Release Valid Values Description Default DISCOVER_WO RKFLOW_SERV ICE 12.0 or higher Y or N Whether to Discover Workflow Service if DISCOVER_WO RKFLOW is Y Y DISCOVER_FOR MS 12.0 or higher Y or N Whether to Discover Forms or not Y DISCOVER_FOR MS_SERVICE 12.0 or higher Y or N Whether to Discover Forms Service if DISCOVER_FOR M is Y Y DISCOVER_SSA 12.0 or higher Y or N Whether to discover SSA Service or not Y DISCOVER_CUS TOM_OBJECTS 12.
Key Supported Release Valid Values Description Default SRVLT_URL_FR OM_CTXFILE 11i Y or N Whether to take Servlet URL from Context file or Not. If this value is N, Value for Servlet url will be "/servlet/oracle.f orms.servlet.List enerServlet" Y ADD_CUSTOM ER_GROUP 12.0 or higher Y or N Shall Add Customer Group N CUSTOMER_IN ST_GRP_NAME 12.0 or higher Text Customer Instance Group Name N/A CUSTOMER_GR P_NAME 12.
Key WLS_ADMIN_P WD Supported Release Valid Values 12.2 or higher Description Password for the WLS admin user Default N/A Customer Groups Created by Discovery Groups are an optional feature in Enterprise Manager that allows the logical organization of targets in accordance to user preference. Command line discovery allows the definition of target groups and placement of Oracle E-Business Suite systems in these groups at time of discovery.
3. Click Delete. By default, the system deletes application server targets (like the HTTP server, OC4J, and so on) when deleting the parent Oracle E-Business Suite target. If you do not want all the application server targets deleted, change the preference. For information on updating preferences, see: Setting Preferences, page 6-1.
5 Credentials Setting Named Credentials In Enterprise Manager, as part of the target type definition, you can define the types of credentials specific to the plug-in target type. Examples could be the user name and password required by the plug-in to connect to a target instance to collect metric data, or to invoke a specific Enterprise Manager job. A named credential is a users' authentication information on a system.
Creating a Named Credential for Oracle E-Business Suite Applications Login Follow these steps in defining this credential: 5-2 1. Specify a name and description for your credential. 2. Select 'Oracle E-Business Suite' as the Authenticating Target Type. 3. Select 'E-Business Suite Application Login Credentials' as the Credential Type. 4. The parameter Scope determines if this named credential is applicable for all instances of Oracle E-Business Suite or to a specific instance.
Creating Named Credentials to Access the Database Follow these steps to create a named credential to access the Oracle E-Business Suite database: 1. Specify a name and description for your credential. 2. Select 'Oracle E-Business Suite' as the Authenticating Target Type. 3. Select 'E-Business Suite Database Credentials' as the Credential Type. 4. The parameter Scope determines if this named credential is applicable for all instances of Oracle E-Business Suite or to a specific instance.
The following examples illustrate creating named credentials for database access. Example: Creating a Named Credential for the Oracle E-Business Suite Database APPS Schema 5-4 1. Specify a name and description for your credential. 2. Select 'Oracle E-Business Suite' as the Authenticating Target Type. 3. Select 'E-Business Suite Database Credentials' as the Credential Type. 4.
Example: Creating a Named Credential for the Oracle E-Business Suite Database APPLSYS Schema Use the following steps to create a credential to access the APPLSYS schema: 1. Specify a name and description for your credential. 2. Select 'Oracle E-Business Suite' as the Authenticating Target Type. 3. Select 'E-Business Suite Database Credentials' as the Credential Type. 4.
5. Define your Credential Properties. Specify the username and password for your APPLSYS schema. Example: Creating a Named Credential for the Oracle E-Business Suite Database System Schema Use the following steps to create the Oracle E-Business Suite Database System Schema credential: 5-6 1. Specify a name and description for your credential. 2. Select 'Oracle E-Business Suite' as the Authenticating Target Type. 3. Select 'E-Business Suite Database Credentials' as the Credential Type. 4.
instances of Oracle E-Business Suite or to a specific instance. So if you choose Target for the scope, you need to select Oracle E-Business Suite Node as the target type and provide the name of the Oracle E-Business Suite target for which this named credential is applicable. 5. Define your Credential Properties. Specify the username and password for your SYSTEM schema. Creating a Named Credential to Monitor the Oracle E-Business Suite Database Create this credential using the following steps: 1.
2. Select 'Host' as the Authenticating Target Type. 3. Select 'Host Credentials' as the Credential Type. 4. The parameter Scope determines if this named credential is applicable for all instances of Oracle E-Business Suite or to a specific instance. So if you choose Target for the scope, you need to select Oracle E-Business Suite Node as the target type and provide the name of the Oracle E-Business Suite target for which this named credential is applicable. 5. Specify the APPL_TOP context. 6.
just a particular instance. To set these credentials, navigate to Setup (menu) > Security > Preferred Credentials in Enterprise Manager. Note: If you wish to perform bulk setup of preferred credentials refer to the section "Setting Preferred Credentials Using EMCLI" in the Oracle Enterprise Manager Cloud Control Upgrade Guide. Setting the Preferred Credentials for the Oracle E-Business Suite Target Type The following table lists the credential sets that are used by the management pack.
To set these credentials, navigate to Setup (menu) > Security > Preferred Credentials in Enterprise Manager. Select Oracle E-Business Suite from the list of target types and click on Manage Preferred Credentials. You either set the default preferred credentials or set them for a specific target instance. Select the appropriate credential set and click on Set. Here you can choose from an existing named credential or create a new credential and set it.
Note: In Release 12.1.0.1.0, these credentials were named "Oracle E-Business Suite Infrastructure". Setting Preferred Credentials for Change Management When using Change Management features, you will need to access Oracle E-Business Suite instances. You can set up credentials for these instances for every user as a one-time setup step instead of entering them every time you need to access an instance. Please note that preferred credentials are not shared across users. To set up credentials: 1.
File Source Mapping. • Oracle E-Business Suite Node - Set the "OS Credentials" credential set. Please refer to section Setting the Preferred Credential Set for Oracle E-Business Suite Node, page 5-10 for information on this credential set. Named Credentials must be created prior to setting up Preferred Credentials.
6 Preferences Setting Preferences Use Preferences in Enterprise Manager to configure some of the features in the management pack. Navigate to the Preferences page from the System Management page through the Administer menu. Set the following: • Maximum Number of Email Addresses for User (required) • Stage Directory (required) This preference, used by Customization Manager, specifies the OMS stage directory for package creation.
Set the following for Patch Manager: • Default Hotpatch in Patch Manager • Default Blackout Minutes in Patch Manager • Default Blackout Hours in Patch Manager • Target Patch Directory Location • Target Stage Directory Location. • Connect to My Oracle Support for Patches For Upgrades from Release 3.1 or 4.0: Properties in amp.properties file replaced by Preferences The amp.properties file used in Release 3.1 and 4.
• ampCloneCommonTopParallelThreads • um_dashboard_no_of_rows (Number of Rows in tables of User Monitoring) • um_session_sampling_interval (Sampling Interval for User Monitoring) • omsPatchStageDir (OMS Stage Directory Location) • MOSEnabled/metalinkEnabled (Connect to My Oracle Support for Patches) Preferences 6-3
7 Security Privileges and Roles for Managing Oracle E-Business Suite Oracle Application Management Pack for Oracle E-Business Suite uses the native Enterprise Manager functionality of privileges and roles for security. Note: In Releases 3.1 and 4.0, security was managed through the amp.properties file and disabled by default. In this release, the amp.properties file is no longer used, and security through privileges and roles is enabled by default.
below. Please note the following in regard to privileges: • The user SYSMAN has all the listed privileges by default. • The use of privileges on a system is enabled by default, which means that a user will not be able to perform an action unless the appropriate privilege(s) are granted to that user. • All target privileges are given against the target "Oracle E-Business Suite".
Target Privileges Name Included Privileges Description Create splice request (none) • To create a request to register a new custom application • To create a request to validate an existing custom application • To create a request to auto-correct an existing invalid custom application • To approve a request to splice an application • To hide and unhide custom applications Approve splice request Create splice request Create Patch Manager request (none) To create a Patch Manager request App
Target Type Level Privileges Name Included Privileges Description Create splice request (none) • To create a request to register a new custom application • To create a request to validate an existing custom application • To create a request to auto-correct an existing invalid custom application • To approve a request to splice an application • To hide and unhide custom applications Approve splice request Create splice request Create Patch Manager request (none) To create a Patch Manager r
Code Name Included Privileges Description EBS_ACP_SUPER_ USER Change Management Super User • Resource privilege "Approve release package request" Role with privileges to create as well as approve all Change Management requests.
Required Privileges and Roles Specific privileges are required to access the relevant containers in the Change Management tab. These are: For rendering this container... Logged-in user must have these privileges Patch Manager Create Patch Manager request Customization Manager Create release package request If the user has ANY of the above privileges, the Change Management home page will be rendered.
Specific Privileges for Features The default roles EBS_SUPER_USER, EBS_ACP_SUPER_USER provide privileges on all targets. If these roles are provided to a particular user, there is no need of providing any specific privileges to that user. If you want to provide specific privileges to a user, follow the instructions in this section, which describes specific privileges for Cloning, Patch Manager, and Customization Manager. There are two types of required privileges: Target Privileges and Resource Privileges.
• Approver: Approve Patch Manager request • Super User: Both All above privileges can be provided either as "Common to All Targets" or "Specific to Target" by adding a target at the bottom of the Target Privilege screen and editing the target-specific privilege.
All above privileges can be provided either "Common to All Targets" or "Specific to Target" by adding a target in Resource Privilege page and selecting the applicable targets.
8 Monitoring Oracle E-Business Suite Navigation and Overview Once discovered, an Oracle E-Business Suite instance will appear in the Oracle E-Business Suite Instances section in the System Management page. You can click on the name of the instance to go to the home page of that instance. Oracle E-Business Suite System Oracle E-Business Suite is discovered as a system. The members of the system include all the nodes and the targets that run on each node.
Topology of the Oracle E-Business Suite The Configuration Topology Viewer provides a visual layout of Oracle E-Business Suite with its child targets. To access the Configuration Topology Viewer, select Members/Topology from the target menu.
Upon service failure, the potential causes of failure, as identified by root cause analysis, are highlighted in the topology view. You can view dependent relationships between services and systems from the Topology tab.
Setting Thresholds for Metrics Metrics collected can be compared to predefined values to check if they are exceeding a critical threshold or a warning threshold. Incidents are generated once the threshold is exceeded. To see the thresholds defined for metrics of any target, select Monitoring/Metric and Collection Settings from the Target menu. Here you can set the Critical/Warning thresholds used to generate incidents. You can also change the collection schedule of the metrics here.
Home Page of the Oracle E-Business Suite System General Section The general section gives the following basic details of the Oracle E-Business Suite instance. Status The status of the Oracle E-Business Suite system, calculated based on the availability of its member targets that contribute to its availability computation. For more information, see: Changing the Availability Computation, page 9-2. Configured Components The count of member targets that fall into the status categories of Up, Down, or Other.
System Name The name of the Oracle E-Business Suite instance. Version The version of the Oracle E-Business Suite instance. Products Installed The number of products installed in the Oracle E-Business Suite system. You can drill down into Oracle Applications Manager to see the details. New Internal System Alerts The number of new System Alerts generated in the Oracle E-Business Suite instance. You can drill down on this number to view the details in Oracle Applications Manager.
has been disabled in the Oracle E-Business Suite system for any reason, then these metrics will not be updated. Availability Status Charts This section has three charts: • Status of the Configured Components • Historic information about the status of the Oracle E-Business Suite instance. You can choose day, week, or month. • Status of the services. Services Oracle E-Business Suite and its member targets provide four major services to its customers.
Critical Components of Services Service Critical components Concurrent Processing • Internal Concurrent Manager • Concurrent Manager • Database • Apps Listener • Concurrent Processing Service • Oracle Workflow Background Engine • Oracle Workflow Agent Listener • Oracle Workflow Notification Mailer • Forms server (OC4J/WLS) • HTTP Server • Database • OACORE Server (OC4J/WLS) • HTTP Server • Database Workflow Service Forms Applications Service Self Service Applications Service
Performance Metrics for Services Service Metric Description Concurrent Processing Service Concurrent Requests Success Rate Successfully completed requests per hour Concurrent Processing Service Concurrent Requests Error Rate Failed requests per hour Forms Service Forms Response Time Average response time of forms in milliseconds Forms Service Forms Requests per Second Average of number of requests processed by the Forms server per second Forms Service HTTP Server Request Throughput Average
Usage Metrics for Services Service Metric Description Concurrent Processing Service Running Requests per Hour Number of requests running per hour Concurrent Processing Service Active Service Processes Number of active services running per hour Forms Service Forms server CPU usage Percentage of CPU used by the Forms server Forms Service HTTP server CPU usage Percentage of CPU used by the HTTP server Forms Service (Socket Mode) Total Memory Utilization Percentage of the total memory used by t
Incidents for Services You can set thresholds for tracking the performance and usage of services. Incidents are generated once the metrics exceeds the threshold. To set the threshold, go to the home page of the service and click on the tab Monitoring Configuration. Click on the link Performance Metrics or Usage Metrics. You can set the warning and critical threshold for performance and usage metrics in the respective pages.
Service Status Information on the Home Page Status Whether the status is up or down System The Oracle E-Business Suite system whose members are providing this service. Performance Incidents Number of performance incidents which are Critical or Warning. You can drill down from here to get the details of the incident. Usage Incidents Number of performance incidents which are Critical or Warning. You can drill down from here to get the details of the incident.
Targets Running on Nodes This section shows the targets running on each node in which the Oracle E-Business Suite is deployed. The data is shown in a hierarchical way with the host as the topmost parent. The nodes running on that host appear as the immediate children. The individual targets running on each node will appear as the child of each node. If the Oracle E-Business Suite instance features Online Patching, only run edition targets will be shown.
Administration of Oracle E-Business Suite Starting and Stopping Services You can start and stop the components running on each node using the Administration menu. Select Administration > Start and Stop Services from the target menu. All the application nodes will be shown with the targets running in them. You can select individual target or a node (which means you are selecting all targets running on that node) and start or stop it.
Privileges need to start and stop services An administrator must have the EM_ALL_ADMINISTRATOR role to run the jobs to start and stop components. In addition, an administrator must have the "Start and Stop Services" privilege to start and stop services. For more information on privileges and roles, see: link : Privileges and Roles for Managing Oracle E-Business Suite, page 7-1.
Configuration of Oracle E-Business Suite You can get the details of how the Oracle E-Business Suite instance is configured by looking at the configuration metrics collected for the Oracle E-Business Suite target. Select Configuration > Last Collected from the target menu. Configuration of all members To see the configuration of each member target of Oracle E-Business Suite you would have to go to the home page of each target and follow the navigation path mentioned above.
Here you can see the links to see the last collected configuration of all member targets grouped as nodes, host, services etc. You can search for any context variable by clicking the Search Context Variable button. You can also search for patches applied and patch set information. Comparing Configurations Comparing configurations is very important while managing Oracle E-Business Suite targets.
different times. The same applies to any member target of Oracle E-Business Suite as well. To compare configurations select Configuration > Compare from the target menu. Incidents for an Oracle E-Business Suite Target Incidents will be raised if any member of the Oracle E-Business Suite system is down or if any metric exceeded its threshold. The incidents region in the Oracle E-Business Suite instance home page gives an overview of the incidents raised for that instance.
Compliance Standards for Oracle E-Business Suite The Oracle Enterprise Manager Compliance Management solution provides the capability to define, customize, and manage Compliance Frameworks and Compliance Standards. It also provides tools to evaluate targets and systems for compliance with business best practices in terms of configuration, security, storage, and so on. Compliance evaluation generates a score for a target which indicates how much the target is compliant with the standard.
Compliance Standard Rules mapped to the standard Severity Turn on ModSecurity Checks if mod security is on. Warning Encrypt Credit Card Data Checks for the encryption of credit card data. Warning Encrypt Credit Card Data Checks if supplemental credit card data is encrypted or not. Warning Encrypt Credit Card Data Checks if enhanced hashing is on or not.
Monitoring User Sessions When a user logs in to Oracle E-Business Suite, the system creates sessions in the database identified by a unique session ID, or SID. All of these user sessions are created using the APPS schema credential. Each database session is associated with an Oracle E-Business Suite application user. This feature enables linking the database session with the corresponding application user for monitoring and troubleshooting purposes.
• Form sessions can be monitored only when the site-level profile Sign-On:Audit Level is set to 'FORM'. The internal name for this profile is 'SIGNONAUDIT:LEVEL'. Top Sessions This page will show four bar charts of database sessions triggered by APPS database user. • Top waiting sessions: sessions waiting for a database event to trigger to proceed further. • Top running SQL statements. • Top CPU consuming sessions. • Top memory intense sessions.
Searching for User Sessions You can search for Oracle E-Business Suite user sessions using Database Session ID - Provide the database session ID and if a match is found with a concurrent program, form or Oracle Application Framework page, the details will be shown with a drilldown facility to the database session details. Oracle E-Business Suite user name - This search shows all the active concurrent programs, Forms, and Oracle Application Framework pages accessed by the user.
Monitoring JVM Usage Note: This feature is not supported for Oracle E-Business Suite Release 12.2 in this release. You can monitor JVM usage parameters which are specific for Oracle E-Business Suite. You can review the following parameters for each of the oacore J2EE containers in which a given Oracle E-Business Suite instance is deployed. 8-24 • Application Module pool - Provides information about all active and leaked application modules.
Setup Steps For Release 12 systems, ensure that you have set up the monitoring configuration for each "oacore" OC4J target as follows: 1. In the section Targets Running on Nodes in the Oracle E-Business Suite instance home page, click on the "oacore" OC4J target. This will take you to the home page of the target. 2. On the home page of the oacore OC4J target, Select Target Setup > Monitoring Configuration in the target menu. 3.
To disable the metric collection, run the following commands: emcli modify_collection_schedule -targetType="oracle_apps_jvm" -targetNames="," -collectionName="LockedAOLJConn" -collectionStatus="Disabled" -preview=N emcli modify_collection_schedule -targetType="oracle_apps_jvm" -targetNames="," -collectionName="AMPoolCount" -collectionStatus="Disabled" -preview=N emcli modify_collection_schedule -targetType="oracle_apps_jvm" -targetNames=",
Obtaining the CA certificate(s) 1. In Microsoft Internet Explorer, connect to the HTTPS URL of the Web site you are attempting to monitor. 2. Double-click the lock icon at the bottom of the browser screen which indicates that you have connected to a secure Web site. The browser displays the Certificate dialog box, which describes the certificate used for this Web site. Other browsers offer a similar mechanism to view the certificate details of a Web site. 3.
Management Server (OMS). You can click on the Refresh icon in the upper right of the Oracle E-Business Suite home page (by the Page Refreshed time stamp) in the Cloud Control console to get updated information. Importing an Oracle E-Business Suite SSL Certificate to the OMS Oracle Application Management Pack for Oracle E-Business Suite invokes REST services deployed on Oracle E-Business Suite using java.net.HttpURLConnection. The User Monitoring and Diagnostics features use REST services.
A Note on Oracle Forms 6i Even though your Oracle Forms configuration may be running in SSL, Cloud Control does not require any additional configuration to monitor Forms. The reason for this is that it uses a different method for determining the Forms Server status which does not require SSL communications with the server.
5. Edit the "URL to measure application response" as appropriate. 6. Click OK. • My Oracle Support (formerly OracleMetaLink) Knowledge Document 123718.1 - A Guide to Understanding and Implementing SSL with Oracle Applications Release 11i • My Oracle Support Knowledge Document 376700.1 - Enabling SSL in Oracle Applications Release 12 • My Oracle Support Knowledge Document 391652.1 - Problem: Accessing Web application gives sun.security.validator.
You can go to the following sections and its subsections in Oracle Applications Manager: • Database • Concurrent Processing • Forms • Workflow • Configurations of all hosts • Configurations of all nodes • Applications Usage • Others Monitoring Oracle E-Business Suite 8-31
Concurrent Processing Dashboard The Concurrent Processing Dashboard provides you with details in concurrent processing in your Oracle E-Business Suite system. The dashboard gives you a complete picture of concurrent processing on your system, both current activities as well as usage statistics. To navigate to the Concurrent Processing Dashboard, select E-Business Dashboard > CP Dashboard from the target menu of the Oracle E-Business Suite target.
Overview Tab The General region lists the status of the Concurrent Processing Service • Status - The status is linked to the Concurrent Processing Service home page. • Active Service Processes - Number of active service processes. • User-defined Concurrent Program Targets - Defining these targets is described in a later section. • Configured Concurrent Managers - The number of configured concurrent managers.
• Type • Status • Incidents • Host The Incidents region lists any incidents that were triggered recently, with the following information for each: • Severity • Metric • Target Name • Target Type • Incident Triggered • Last Value • Last Checked At the bottom of the dashboard are Related Links: The first three links provide metrics on requests and processes: • Hourly Completed Requests • Processes and Requests per Concurrent Manager • Active Concurrent Requests by Application The l
Current Activity Tab The Concurrent Requests by Status region lists the number of requests for each status: • Pending Normal • Pending (Standby) • Scheduled • Inactive (No Manager) • On Hold • Running Click on the number for a status to find out more about the metric trend.
• Requests Warning Rate (%) • Requests Error Rate (%) Click on the number for each statistic to find out more details. The Concurrent Managers by Requests lists all concurrent managers, in order of the number of requests it has in the specified status, either Running or Pending.
• Pending - These are sorted by running time in descending order. • Scheduled - These are sorted by their scheduled start time. The Top Applications region lists the top ten (10) applications for running requests or pending requests, as specified. The Top Users region lists the top ten (10) users by number of running or pending requests, as specified. Usage Tab This tab provides a summary of how the concurrent programs and managers have been utilized over a period of time.
running time are shown. For each program listed, the number of executions, total running time (minutes) and percentage (%) of successful executions are shown. The top ten (10) applications for the following categories are listed: • Number of executions • Number of failed executions The top ten (10) users by total number of requests are also listed, in descending order of number of requests.
User-Defined Targets Tab You can add concurrent managers and programs as targets to monitor. Use this tab to get details about these targets as well as add more custom targets. Concurrent Programs For custom concurrent program targets, the following columns are shown: • Name • Concurrent Program Short Name • Incidents • Host Click on "Show" in the Details column to see the following metrics for the given concurrent program target.
• Long-Pending Requests • Long-Running Requests Use the Add button under Concurrent Programs to add a new program target.
2. For your new target, define the following: • Target Name Prefix - This value is determined by the system based on the instance name and cannot be updated. • Target Name - Enter in a target name "suffix". The actual target name will be composed of the Target Name Prefix (above) and the value of this field. • Target Type - The system automatically provides the value "Custom Oracle Concurrent Program".
3. • (Database) Password • ConnectString For metrics collection, you need to define the thresholds for several metrics. Define instance parameters that will be used to categorize requests for the following: A request will be termed Long Pending if it is in Pending status for longer than the "Long Pending Request Threshold In Minutes". A request will be considered Long Running if it runs for longer than the "Long Running Request Threshold In Minutes" and (1+0.
Metrics Collected The following metrics are collected: Basic Information This page lists metrics for the following: • Requests Completed Successfully • Requests Completed with Warnings • Requests Completed with Errors • Minimum Run Time • Maximum Run Time • Average Run Time Concurrent Requests by Status The numbers for requests in each status below are listed.
Long Pending Requests • Request ID • Concurrent Program Short Name • Concurrent Program Name • Request Start Date • Username • Phase • Status • Pending Time • Concurrent Manager Long Running Requests • Request ID • Concurrent Program Short Name • Concurrent Program Name • Request Start Date • Username • Phase • Status • Running Time • Concurrent Manager • Request ID • Concurrent Program Short Name • Concurrent Program Name Pending Requests 8-44 Oracle Application
• Request Start Date • Username • Phase • Status • Pending Time • Concurrent Manager Requests Completed with Error • Request ID • Concurrent Program Short Name • Concurrent Program Name • Request Start Date • Username • Phase • Status • Execution Time Requests Completed with Warning • Request ID • Concurrent Program Short Name • Concurrent Program Name • Request Start Date • Username • Phase • Status • Execution Time Monitoring Oracle E-Business Suite 8-45
Running Requests • Request ID • Concurrent Program Short Name • Concurrent Program Name • Request Start Date • Username • Phase • Status • Running Time • Concurrent Manager Adding a Concurrent Manager Target You can add a concurrent manager custom target so that the system will collect metrics on activity and usage for requests run by the concurrent manager. 1.
2. For your new target, define the following: • Target Name Prefix - This value is determined by the system based on the instance name and cannot be updated. • Target Name - Enter in a target name "suffix". The actual target name will be composed of the Target Name Prefix (above) and the value of this field. • Target Type - The system automatically provides the value "Custom Oracle Concurrent Manager".
3. • (Database) Password • ConnectString For metrics collection, you need to specify values for three Instance Properties that will be used to categorize requests for the following: A request will be termed Long Pending if it is in Pending status for longer than the "Long Pending Request Threshold In Minutes". A request will be considered Long Running if it runs for longer than the "Long Running Request Threshold In Minutes" and (1+0.
• Process Status Pending Requests • Request ID • Concurrent Program Short Name • Concurrent Program Name • Request Start Date • Username • Phase • Status • Pending Time Running Requests • Request ID • Concurrent Program Short Name • Concurrent Program Name • Request Start Date • Username • Phase • Status • Running Time Monitoring Oracle E-Business Suite 8-49
Concurrent Processing Metrics This section lists the concurrent processing metrics available from the All Metrics page. Navigate to the All Metrics page by selecting Target menu > Monitoring > All Metrics. For each type of metric below, the details listed for each record are shown.
• Total Executions • Errored Executions • Errored Executions (%) Applications by Executions • Application Short Name • Application Name • Total Executions • Successful Executions (%) • Errored Executions (%) Applications by Pending Requests • Application Short Name • Application Name • Number of Pending Requests Applications by Running Requests • Application Short Name • Application Name • Number of Running Requests Programs by Average Running Time • Concurrent Program Name •
Programs by Errored Executions • Concurrent Program Name • User Concurrent Program Name • Total Executions • Total Executions (Errored) • Executions Errored (%) Programs by Executions • Concurrent Program Name • User Concurrent Program Name • Total Executions • Successful Executions (%) • Errored Executions (%) Programs by Total Running Time • Concurrent Program Name • User Concurrent Program Name • Total Executions • Total Running Time • Successful Executions (%) Top Pending R
• User Name • Manager Name • Phase • Status Top Running Requests • Request ID • Program Name • Program Short Name • Request Start Date • Running Time • User Name • Manager Name • Phase • Status Top Scheduled Requests • Request ID • Program Name • Program Short Name • Request Start Date • Scheduled to Run In (Minutes) • User Name • Manager Name • Phase • Status Monitoring Oracle E-Business Suite 8-53
Top Users (Requests Submitted) • User Name • Number of Requests Users by Pending Requests • User Name • Number of Pending Requests Users by Running Requests • User Name • Number of Running Requests Setting Long Running and Long Pending Requests Parameters for Metrics and Incidents Oracle Application Management Pack for Oracle E-Business Suite allows you to define parameters for long running and long pending requests. Follow the procedure below to do so. 1.
Menu, selecting Monitoring, then selecting All Metrics.
9 Monitoring Configuration Configuring Monitoring of Oracle E-Business Suite You can change the configuration with which each Oracle E-Business Suite instance is monitored. You can do two things • Change monitoring schema • Change the availability definition of the Oracle E-Business Suite instance To configure monitoring, go the System Management page and select the Oracle E-Business Suite instance and click Configure.
schema. You can either change the user name or password here and click Next or directly proceed to change the availability computation by clicking Next. Changing the availability computation The status of the Oracle E-Business Suite target is determined by the status of its member targets.
The Available Targets section allows you to search for targets and add them to the availability computation list. You can select target type from the drop down before clicking Go. The Selected Targets section shows the targets which are already in the availability computation list. By default the availability computation list contains all the members of the Oracle E-Business Suite instance. If the Oracle E-Business Suite instance features online patching, you must add targets from both file editions.
10 Diagnosing Issues Diagnosing Issues Pack Diagnostics Oracle Application Management Pack for Oracle E-Business Suite includes a diagnostics feature which can be used to troubleshoot issues by running diagnostic tests. The tests are grouped into the modules listed below. • Cloning • Patch Manager • Customization Manager • User Monitoring To navigate to the diagnostics module, select Pack Diagnostics from the Administer menu in the System Management page.
How to run a diagnostic test To execute a diagnostic test, click on the Create button. This will take you the page where you must provide the details to do the diagnosis. You must enter the following details: Diagnostic Test Details 10-2 Field Description Name A unique name to identify this instance of execution. This name can be later used to search for this instance of execution. Module You can select a specific module or all modules. When you select a module, all tests for that module will be run.
Field Description Show Details You can select the extent of detail you want in the final report. Category Description • All - This option logs all information regardless of whether the diagnostic test completes with success or error. • Error - This option only logs details for those tests that error out. • Generic - Select this option to perform a health check of a specific module. • User Specific - Select this option to diagnose issues faced by the current logged-in user in a specific module.
the Diagnostics dashboard, available from the Pack Diagnostics link on the Oracle Applications page. For more information on running diagnostic tests, see: Running Pack Diagnostics Tests, page 10-1. The following tables list tests related to cloning.
Step Severi ty Test Description Notes/Expected Results/Corrective Measures EBS Warni ng Get the Database Tier Operating System User Name Get the O/S User Name for the database tier. It is useful to know with which operating system user name the source database nodes have been created, as there could be file permissions issues in cloning. Corrective action: AutoConfig needs to be run in the Database Context to get t this value populated in the configuration.
Step Severi ty Test Description Notes/Expected Results/Corrective Measures EBS Warni ng Get key environment variables for Database Context Obtain key environment variables for Database Context, including: Certain database context variables of the source Oracle E-Business Suite instance need to be definitively set with non-null values for the cloning job to proceed successfully.
Step Severi ty Test Description Notes/Expected Results/Corrective Measures EBS Warni ng Get key information required for Apps Context Configvariables Obtain key environment variables for the applications context, including: Certain applications context variables of the source Oracle E-Business Suite instance need to be definitively set with non-null values for the clone job to proceed successfully.
Step Severi ty Test Description Notes/Expected Results/Corrective Measures EBS Critica l Get EBS Perl Version Check Oracle E-Business Suite Perl utility version. Cloning using the management pack requires Oracle E-Business Suite Perl utilities to be at a certain version level for certain cloning flows to function properly. Please make sure that the Perl version on the Oracle E-Business Suite instance is compatible with that in the Agent (see related diagnostic test for the Agent Perl Version).
Step Severi ty Test Description Notes/Expected Results/Corrective Measures EBS Warni ng Get key environment variables for Application Context Obtain key environment variables for the applications context, including: If this diagnostic test fails, rerun AutoConfig on the applications tier. Checks if Oracle E-Business Suite AD Snapshot is valid Verify if the Oracle E-Business Suite AD snapshot is valid.
User-Specific Tests for Cloning Ste p Severi ty Test Description Notes/Expected Results/Corrective Measures EBS Warni ng Check Host Credential for Smart Clone flows Check if the EM User has required preferred credential set for "Operating System Username" and "Operating System Password" in "Oracle E-Business Suite Node" target type for the applications context for Smart Clone flows.
Generic Diagnostic Tests for Patch Manager Ste p Test Group Description Notes/Expected Results/Corrective Measures EM GC Check permissions for OMS Stage directory Determine if a stage directory is defined on the OMS. Determine if the owner has read/write permissions to that directory. Expected results are: the OMS Stage Directory Location, with the OMS user with read/write permissions.
User-Specific Diagnostic Tests for Patch Manager Ste p Test Group Description Notes/Expected Results/Corrective Measures EM GC CheckMetali nkCredential s Verify if username/password credentials are entered for My Oracle Support. Refer to the Oracle Enterprise Manager documentation for instructions on completing this step. EM GC CheckPrivile ge Check if the user currently logged in has authority to patch any instances.
Generic Diagnostic Tests for Customization Manager Ste p Test Group Description Notes/Expected Results/Corrective Measures EM GC CheckOMSSta ge Determine if a stage directory is defined on the OMS. Determine if the owner of the directory has read/write permissions to that directory. Expected results are: the OMS Stage Directory Location and the OMS user with read/write permissions.
Ste p Test Group Description Notes/Expected Results/Corrective Measures EBS Check Customizatio n Manager related AD Patches for 11i Release Verify that certain AD patches have been applied on the Oracle E-Business Suite target. The set of required interoperability patches will vary for the different Oracle E-Business Suite releases (that is, Release 11i , Release 12, and so on). The list of patches is contained in an XML file that might be modified to include or exclude recommended patches.
Ste p Test Group Description EM GC Summary A summary of all of the diagnostic tests that have been executed, in these groups: Successful, Failed, With Warning, Aborted, and Total. Notes/Expected Results/Corrective Measures User-Specific Diagnostic Tests for Customization Manager Ste p Test Group Description Notes/Expected Results/Corrective Measures EBS CheckEBSGlob alCred Check Oracle E-Business Suite Preferred Credentials.
Generic Tests for User Monitoring Test Description Corrective Actions CheckIOPatch es Checks whether the mandatory interoperability patches needed for user monitoring are applied in this Oracle E-Business Suite instance. Apply the mandatory interoperability patches in the Oracle E-Business Suite instance. CheckRESTH ealth User monitoring uses REST services deployed on the Oracle E-Business Suite instance. This test checks if the REST services are accessible or not.
11 Cloning an Oracle E-Business Suite System Cloning an Oracle E-Business Suite System One of the key features of the Oracle Application Management Pack for Oracle E-Business Suite is the ability to clone an Oracle E-Business Suite system automatically using the Smart Clone procedure. The key highlights of the cloning process include: • The Oracle Application Management Pack for Oracle E-Business Suite allows Oracle E-Business Suite systems to be cloned using the Cloud Control provisioning framework.
• Configuring RAC databases • Customizing the listener names is supported if you have the required Oracle E-Business Suite patches applied. • Configuring listeners with SCAN IPs is supported if both the database version and the cluster version are greater than 11.2.0.
Terms The following table lists some cloning terms used in this document. Term Meaning Source Oracle E-Business Suite system being cloned. Target Oracle E-Business Suite system being created as a copy of the source system. Smart Clone The cloning utility in Oracle Application Management Pack for Oracle E-Business Suite. Smart Clone allows you to use a database target cloned using an external solution as an input to its cloning procedures.
For example: 140.87.205.217 adc60002demo.us.oracle.com adc60002demo 2. For Release 12 only: In addition to the above entry in the /etc/hosts file, the applications node context file needs to be changed. Change the s_dbdomain entry in the /appsTier/context/apps/_.xml file to the correct domain name of the database tier. For example, if the database node domain name is idc.oracle.
privileges. The privileges listed below could be granted in many ways depending on the desired level of granularity of privileges to be granted to the user. For more details on granting privileges, please refer to the section "Configuring Security" in the manual Oracle Enterprise Manager Cloud Control Administrator's Guide 12c Release 1. The following outlines one of the ways of granting the required privileges for executing the Smart clone procedure.
4. The following Named Credentials must be defined: • • Host target type • Authentication Target Type: "Host" • Credential Type: "Host Credentials" Oracle E-Business Suite target type Please refer to the section Creating Named Credentials for Oracle E-Business Suite, page 5-1 for instructions on creating the Oracle E-Business Suite Database Credentials.
• • • • Number of parallel threads/processes that will be used while zipping, transferring and unzipping the files under APPL_TOP directory of the applications tier. • Minimum value: 1 • Maximum value: 16 • If the value is empty OR less than 1 OR greater than 16, then the default value of 8 is used. Number of parallel threads/processes that will be used while zipping, transferring and unzipping the files under Tools Oracle Home directory of the applications tier.
Also, note the following regarding zipping of files during the cloning process: • /clone/FMW/FMW_Home.jar will be very large (2.7 GB). • The WebLogic Server home directory (FMW_Home) will NOT be zipped or transferred. Diagnostic Tests For information on diagnostic tests for this feature, see: Diagnostic Tests for Cloning, page 10-3. Running a Single Node to Single Node or Multi Node to Single Node Cloning Procedure for Release 11i and 12.1.
3. Enter general information for the cloning process. This step captures information related to the target database already cloned and discovered in Enterprise Manager. Provide a transaction name for the Clone Name. Choose the source Oracle E-Business Suite you would like to clone from the LOV. Specify the target database which is to be cloned from the source Oracle E-Business Suite's database.
If the target database is a RAC database, the Target Database Details region is rendered differently, as shown in the following figure. Specify whether SCAN is configured in the target database.
4. Enter RAC Target database details, if applicable. This step only applies if the target database is a RAC database. This step is skipped if the target database has the type Single Instance. If the source Oracle E-Business Suite technology stack has the required patches applied for configuring customized names for listeners, then this page will automatically render in such a way that you provide names for the target database listeners by providing the required names in the column "New Listener Name".
Port fields are not populated (for example, if the cluster target instance discovered in Enterprise Manager has not populated these values yet as properties), then you must enter the correct values for these fields. Optionally, check the box "Use Custom SCAN Name and Port" if you want to get the target database configured with the SCAN listener. If you do not check the box "Use Custom SCAN Name and Port" box, then Smart Clone will clone the target database with virtual host names.
In the Available Target System Nodes region, choose the source host that can be used as a reference while cloning the target applications tier. Specify the target host from the LOV where Smart Clone should create the target applications tier. If the source Oracle E-Business Suite system is deployed on a multi-node applications tier, then the Source regions appear as shown below.
the default option. Then choose the source host that can be used as a reference while cloning the target applications tier. Specify the target host from the LOV where Smart Clone should create the target applications tier. For the target system node, click the Specify Details icon to update its properties in the Target Node Summary page. 7. The Target Node Summary page is shown below. The port pool and individual port values are updated from the source instance.
9. Enter Credentials. Smart Clone uses named credentials. You can select and test the named credentials on this page. Named credentials can be created by navigating to the Setup menu, then Security > Named Credentials, and clicking Create. Smart Clone requires the following credentials to be created: • • Application Node OS Credentials and Database Node OS Credentials.
Note: Database schema credentials appear only when the source applications system is on Release 11i and using a non-shared file system. The Credentials page for a Smart Clone procedure where the source applications system is multi-node and the target database is non-RAC is shown in the figure below. This page allows you to enter in and test all required credentials for the nodes.
The Credentials page for a Smart Clone procedure where the source applications system is single node and the target database is RAC is shown in the figure below. On this page you can enter and test the required credentials for all the nodes. 10. Enter values for custom parameters. These would be used in any directive steps you have created. You can create directive steps to be integrated into a deployment procedure.
shipped Smart Clone procedure, see: Adding Custom Steps to a Smart Clone Deployment Procedure, page 11-38. 11. Schedule the deployment. 12. Review your Smart Clone deployment procedure and click Finish.
Running Scale-Up and Scale-Down Multi-Node Cloning Procedures This section describes using Smart Clone for scale-down and scale-up cloning of Oracle E-Business Suite application nodes. This type of procedure is supported for Oracle E-Business Suite Releases 12.0 and 12.1. This procedure is similar to the single-node Smart Clone procedure; the main difference is in specifying the source and target in the "Source/Target" step in the interview process.
"Start a Clone" list. 2. Enter general information for the cloning process. This step captures information related to the target database already cloned and discovered in Enterprise Manager. Provide a transaction name for the Clone Name. Choose the source Oracle E-Business Suite you would like to clone from the LOV. Select the target database which is cloned from the source Oracle E-Business Suite's database.
If the target database is a RAC database, the Target Database Details is rendered differently, as shown in the following figure.
Provide the following for the target database: • Apps Schema Username • Apps Schema Password • System Schema Password Specify whether SCAN is configured in the target database. You can click on Validate Database button or you can leave it to the Next button to perform the same action. 3. Enter RAC Target database details, if applicable. This step only applies if the target database is a RAC database. This step is skipped if the target database is a single instance database.
automatically render so that you provide names for the target database listeners in the required field "New Listener Name". If the source Oracle E-Business Suite technology stack does not have the required patches, then Smart Clone will give default names to the listeners using the naming convention "LISTENER_".
• 5. Details of the services on the nodes Enter target information on the Source/Target step. Choose the type of target. For multi-node cloning, the options are: • Multi-node target with a non-shared file system • Multi-node target with a shared file system Note that when the target has a shared file system that: • The first node in the admin service list is considered the primary service.
If you want to delete a node from a service, select the node to be deleted and click the Delete button. 7. After you add the lists of nodes, you can navigate to the "Common Properties" page. In this page you specify properties such as port data and the applications base directory location.
Common Properties for Shared APPL_TOP When you click the Check Availability button, the port availability on all selected nodes will be checked. This verification is also done when you click OK for the page itself. The port pool and individual port values are updated from the source instance. If there is an invalid value in the port pool from the source instance: following error will be shown: "NOTE: Source Apps portpool context variable (s_port_pool) is invalid: . Setting to default value '0'.
9. Enter Credentials. Smart Clone uses Named Credentials. You can select and test the named credentials on this page. Named credentials can be created by navigating to the Setup menu, then Security > Named Credentials, and clicking Create. Smart Clone requires the following credentials to be created: • • Application Node OS Credentials and Database Node OS Credentials.
Note: Database schema credentials appear only when the source applications system is on Release 11i and using a non-shared file system. The Credentials page for a Smart Clone procedure where the source applications system is multi-node and the target database is non-RAC is shown below. This page allows you to enter and test all required credentials.
The Credentials page for a Smart Clone procedure where the source applications system is single node and the target database is RAC is shown below. This page allows you to enter and test the required credentials. 10. Enter values for custom parameters. You can create directive steps to be integrated into a deployment procedure. For more information on deployment procedures, see the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Deployment Procedure, page 11-38. 11. Schedule the deployment. 12. Review your Smart Clone deployment procedure and click Finish.
What's Next When a multi-node to multi-node applications tier cloning procedure is submitted, then, irrespective of whether it is a "scale-up" or "scale-down" procedure, the admin node is configured first with the given services enabled. Then each node will be configured one after the other, depending on the node details specified in the cloning interview. After all the nodes are configured, the URLs used in accessing Oracle E-Business Suite are redirected to the node on which AutoConfig was last run.
2. Enter basic information for your cloning procedure, including Clone Name, Description, and target and source information. Also enter the source WebLogic Admin Password and the target database APPS credentials. In the case of single-node target database cloning, you will be prompted the TNS_ADMIN of target database. If the target database is a RAC database, a new region of prompts appears to capture RAC-specific information, as shown below.
For the RAC Target DB Node Specific Details: • Virtual Host Name - The virtual host name. Note that the domain name must NOT be appended. • Current Listener Name- The value with which the database instance can be connected. • New Listener Name - If you want to change the existing listener name, enter the new name here. If you want to retain the existing listener name, then enter the current listener name in this field.
You can choose the port pool for run file system and patch file system. You can validate the ports individually for the run file system and the patch file system. In case of port unavailability, an error will list the invalid port information. 4. In the Stage Directories step, enter stage location information. The source stage location is where the source application file system is staged. The target stage is the location where the staged application files are copied.
If you choose Copy, select the Copy Method: • Shared File Copy Option - Choose this option if the stage location is shared across the source and target. Note: Because of a known limitation in Smart Clone for Release 12.2.x, please do not use the 'Shared File Copy' option currently. Instead use 'No Copy' method as they are functionally same. 5. • Remote File Transfer Option - Choose this if the source and target applications file systems are in different hosts.
6. Enter the Schedule information. You can select "Immediate" to submit the Smart Clone run immediately, or you can schedule the Smart Clone run for a future date. 7. 11-36 Review the information you have entered.
In the case of a RAC target database, specific information pertaining to RAC is also displayed. Note on manual steps if the source is a multi-node application tier instance: In the Smart Clone Deployment Procedure for Release 12.2.x , if the source is multi-node application tier instance, then there will be manual steps involved.
figure below illustrates these steps. 1. In the first manual step, a manual step is needed after the RUN File system is configured and started. You must manually login to WebLogic console of the RUN file system and remove the redundant source node entries as described in the manual step information. Then you must confirm your changes in the EM Console. 2. As AutoConfig on the database tier will update the sqlnet.
directive step and add it to a copy of an out-of-the-box deployment procedure, refer to the Oracle Enterprise Manager Cloud Control Administrator's Guide. Create a directive step: 1. From the Enterprise menu, select Provisioning and Patching, then select Software Library. 2. Create a new directive. From the Actions menu, select Create Entity, then select Directives.
3. 11-40 Specify a name and other attributes for the directive.
4. Add parameters for the directive.
5. Select the "Software Library" location and the script to be executed. In the example below, a Perl script is used. 6. Click Next and Save and Upload. Create a copy of the out-of-box Smart Clone deployment procedure: 1. 11-42 From the Enterprise menu, select Provisioning and Patching, then select Procedure Library.
2. Select "Smart Clone" and click "Create Like". 3. Enter a name and other general information.
4. 11-44 On the Procedure Steps tab, select the step before, inside, or after which you want to add the custom step, and click Insert.
5. Give the new step a name and enter additional information for the step.
6. Search for the directive and click Next. 7. Map the parameters as required in the Map Properties step. In our example, a text box will be provisioned in the Smart Clone procedure interview to provide the value for "Parameter 2".
supported in Smart Clone for Release 12.2.x. 8. Save the custom step and then save the procedure.
9. 11-48 You can now submit the newly-created deployment procedure.
12 Introduction to Change Management Introduction Change Management for Oracle E-Business Suite (formerly delivered in the product "Oracle Application Change Management Pack for Oracle E-Business Suite" and abbreviated as "ACP" or "ACMP") provides a centralized view to monitor and orchestrate changes (both functional and technical) across multiple Oracle E-Business Suite systems.
Major Benefits • Simplifies the mechanism of orchestrating changes across multiple Oracle E-Business Suite systems. • Improves user productivity by automating the deployment of changes. • Reduces human errors by providing a standards-based change deployment framework. • Provides notifications to specified users of updates to the Oracle E-Business Suite systems.
requests and historical data. A common change control tracking dashboard is provided for tracking all change requests within Change Management. Auto-approvals are possible if the requestor is a Super Administrator or has the respective approver role with approval target access. All critical changes within Patch Manager and Customization Manager would need to go through the change control mechanism. The main Change Management tab lists recent activity for change approval requests.
The Change Approval Dashboard allows users with the proper privileges to perform the following: • Search for requests as per role access. • Approve or reject a given change control request after viewing details. • Track heuristic data with respect to change control requests for auditing purposes using "Related History". Preferred Credentials for Change Management When using Change Management features, you will need to access Oracle E-Business Suite instances.
• Enter the SMTP information as described below. To set the SMTP information in Oracle Enterprise Manager: The Outgoing SMTP Server information must be entered in Oracle Enterprise Manager. Note: If the SMTP information is not set correctly, notifications will not be sent. 1. Within Oracle Enterprise Manager, navigate to Setup > Notifications > Notification Methods. 2. Set the Outgoing Mail (SMTP) Server value. 3. Enter additional information as needed.
13 Patch Manager Introduction Patch Manager allows you to deploy patches across Oracle E-Business Suite instances from a single console. You can create a patch run definition and run it multiple times on multiple instances and you can copy a patch procedure and modify it to suit your business needs. Also, you can easily access details on patch runs, correct errors if necessary, and continue the patch runs.
• Leverages Oracle Enterprise Manager infrastructure for distributed processing. With Patch Manager, you can • View the readme of a patch with just one click. • Schedule deployments based on the target's time zone. • Schedule deployments of patches immediately or in the future. • Perform a complete series of pre/post health checks when deploying patches. • Track and monitor all patching deployments "Running", "Scheduled", "Saved" and "Succeeded" from a centralized console.
Patch Runs The Patch Runs region of the Patch Manager Home lists the patch runs and their statuses for Oracle E-Business Suite Release 12.1 and earlier. You can perform various actions on a patch run depending on its status: • Review - Review details of the patch run. • Create Like - Copy an existing patch run, in order to change any aspect of the patch run or to run an identical run due to changes in the patch or target. • Edit - If a patch run is in Saved status, you can edit it.
Note that with Release 12.2, the adop patching process in Patch Manager is broken down into two deployment procedures. The first deployment procedure runs the prepare, apply, finalize, and potentially actualize_all phases. The second deployment procedure executes the cutover, cleanup, and potentially fs_clone phases. You can click the New Deployment to begin a new online patching interview.
• Cutover - This icon submits the cutover deployment procedure. It opens a window in which you can schedule the cutover. This feature also ensures the adop session for which you are running is actually the latest. • Requestor - This is the user who requested the patch be applied. • Created By - This is the user who created the interview. • Last Updated - Timestamp indicating when the deployment procedure was last updated.
Prerequisites for viewing Patch Manager logs To access the Patch Manager Log Viewer, you must have your preferred credentials set for the Oracle E-Business Suite Node target(s) of all middle tier hosts. To set these, the navigation in Enterprise Manager is Setup > Security > Preferred Credentials > Oracle E-Business Suite Node. These credentials are required in addition to the credentials needed to use Patch Manager. In addition, you must have been granted the privilege to raise a Patch Manager request.
Abort Deployments This region shows all of the executions of the "Abort an Oracle E-Business Suite Online Patch Cycle" deployment procedure. You can submit a request to run an Abort operation using the Submit Abort icon. This action submits an Abort request like that in the Online Patching region. This action does not compare the adop session ID on the target EBS system against the adop session ID of any patch deployments from EM. This region is hidden by default.
icon. Records can be filtered by status using the "Show" list. The "Pending Patches" button displays all patches that have been applied but not cutover. Running a Patching Procedure (Release 12.1 and earlier) Oracle provides you with patching procedures that are best practices for patching Oracle E-Business Suite. Procedures created by Oracle cannot be edited, but they can be copied using the "Create Like" feature so that you can customize the procedure to fit your environment.
target again. Custom patches, described in the next chapter, will always be moved from the OMS to the target because a developer can change the patch. 3. The following preferences are set to directories under the APPL_TOP by default. In general, you should leave these set to the default locations. You can override the default locations, but ensure that the Target Patch Directory Location is not shared amongst multiple Oracle E-Business Suite instances.
2. • Patch Run Name - Enter a user-friendly name for the patch run. You can search on this name later on. • Description • Justification • Requester - The default value is the user name with which you are signed in. You can change this to another name. • Notification E-mail(s)- Enter the e-mail addresses of users who should be notified of the patch run request. These users could review and approve the request, as appropriate.
the same release level. Once selected, the system name will appear in the Target List with the following: • Applications System Name - The name of the system. • Status - The status of the system (Up or Down). • Applications Release - The release level of the applications system. • Workers - The number of workers available on the system. Note that you can change this value. • Database Version - The release level of the database for the applications system.
The following are shown on the Patch Details page: These are set in the Preferences page. • Target Stage Directory Location - The directory to which zipped patches are downloaded. • Target Patch Directory Location - The directory to which patches are unzipped, and from where the patches are applied. • OMS Stage Directory Location Important: You must have at least 'view' target privilege on the agent(s) of the target hosts.
2. In the Search and Select window, Patch Oracle E-Business Suite, if you are downloading a patch or patches from My Oracle Support, you can search based on the following criteria: • Patch Number • Platform - "Any" returns patches for all platforms, or Generic if patch is not port-specific. If you are searching for a patch for a specific platform, your search results will return a Generic-platform patch if no platform-specific patch exists.
2. In the Search and Select window, you can search based on the following criteria: • Patch Number • Patch Name • Description • Created By • Version • Language The search results will include the following for each patch found: • Patch Number • Patch Name • Version • Language • Description • Created By Choose the desired patches and click Select to return to main window. A listing of patches is given.
• Description - The description of the patch. • Files - The files to be downloaded for the patch. • Order - The order the patches should be applied. Will only be displayed when you have more then one patch selected and don't have merge patches check box checked. • Can Be Re-applied - You can check this box if the patch can be re-applied with no ill effects. In the case of testing, it might be necessary to apply the same patch repeatedly, in which case this box should be checked.
4. Specify Patch Options. Specify details for how the patch should be applied. For more information on many of these options, see: Oracle E-Business Suite Patching Procedures and Oracle E-Business Suite Maintenance Utilities. Patching Procedure Options include the following: • Create Target Backup Before Patching - Adds a pause after system is prepared for backup allowing for a manual backup.
notifies other Enterprise Manager administrators that a maintenance procedure is being performed on the environment. • Disable Archive Mode - Issues an 'alter database noarchivelog' command. • Pause Before AutoPatch Steps - Adds a pause before AutoPatch (adpatch) is run to allow for any necessary manual preparation. AutoPatch (adpatch) is the Oracle Applications DBA (AD) tool that applies patches to an Oracle E-Business Suite system.
• Disable File Generation - Tells adpatch not to run commands normally found in generate driver (nogenerateportion command). AD Administration Options are listed below. These tasks are done to manage database objects (database objects or data in the database related to Oracle E-Business Suite). For example, a patch might add new menu entries or change the setup of a flexfield. • Generate Message Files - Creates new message files after the messages have been loaded into the database.
You can choose to apply the patches immediately or at a later date. If you choose Immediately as the schedule type to have the patches applied immediately. If you choose Later, you can specify the time and date you wish to have the patches applied. Provide the Time Zone, Date and Time. You can specify a Grace Period as well.
The Review Page lets you review your patch run details, target list, patch details, patching options, and schedule. Creating Patch Deployment Procedures for Oracle E-Business Suite Release 12.2 To create a Patch Deployment: 1. 13-20 On the Deployment Details page, enter the details below. • Patch Deployment Name - Enter a user-friendly name for the deployment procedure. You can search on this name later on. • Target System Name • Verify Credentials - Click this button to check your credentials.
• WLS domain credentials • Description • Justification - Enter a justification that can be used by an approver deciding to approve or reject this request for patching. • Requester - The default value is the user name with which you are signed in. You can change this to another name. • Notification Email(s) - Any users listed here will be notified when the patching deployment request is sent to approval management.
You can search for a patch based on the following criteria: • Patch Number • Language • Created By • Platform Note: You must retrieve the desired patch through the Search region even if you have already downloaded the patch to the stage location (the process will not re-download the patch, however). The act of searching will search: 13-22 • Custom patches if a patch number greater than 11 characters has been entered or no patch number has been entered.
Preferences page. Selecting the "Merge Patches" option will merge the patches when running adop later. Selecting the "Check Prerequisites" option will connect to My Oracle Support (MOS), check the prerequisites for all the selected patches, and then check the target system to see if those patches have been applied. You must have "Connect to My Oracle Support for Patches" enabled in the Preferences page to use this option.
Note: For a controlled-release patch, a lock icon appears next to the patch number. Click on the icon to enter a password. Passwords expire after a set duration, so for scheduled deployments further in the future, make sure you have already downloaded the patch and staged it. 3. 13-24 • Platform - The platform for the patch. • Language • Description • Readme • Created By • Replaced By • Patch Name • Product - The short name of the owning product.
With Oracle E-Business Suite Release 12.2 the adop patching process required two deployment procedures. The first deployment procedure runs the prepare, apply, finalize, and potentially actualize_all phases. The second deployment procedure executes cutover, cleanup, and potentially fs_clone. On the options page you determine when each of these deployment procedures are executed.
• Schedule • Indefinite Grace Period For the Prepare phase, specify Pause After Prepare. This option will stop execution of the deployment procedure after the adop prepare phase has been run. A user would then need to manually acknowledge the pause for Enterprise Manager to continue with the next step. For the Apply phase, specify Pause After Apply. This option will stop execution of the deployment procedure after the adop apply phase has been run.
through finalize with the missed prerequisite then restart the original failed deployment procedure. Check the Indefinite Cutover Grace Period box if you want Enterprise Manager to wait an indefinite amount of time if the Enterprise Manager job system cannot start the deployment procedure at the intended time. For the Cutover phase, the Restart Middle Tier is selected by default. When cutover is run, this option controls whether the middle tier is restarted.
The Review Page lets you review your deployment procedure details. Copying a Patch Run You might want to copy an existing patch run to change some aspect of it or to rerun it due to changes in the patch or target. To do this, select the patch run in the Patch Manager Home page and click the Create Like icon. The system will take you through the patch run creation pages as if you were creating a new patch run, but with most values copied from the original patch run.
• The Requester field has a default value of the original requester's user name. Change this value as appropriate. • The new patch run would be scheduled to run immediately by default, because the original run may have been scheduled for a now past date and time. Extending Patch Manager Deployment You can extend Patch Manager procedures using the Deployment Procedure Manager using the steps below.
Logging, Health Checks, and Troubleshooting This section describes logging, health checks, and troubleshooting features within Patch Manager. How to Access Patch Logs The primary way to access log files is using the log viewer in the Patch Logs region of the Patch Manager Home page. See: Patch Logs, page 13-5. Alternatively, you can drill down into the steps within an online patching deployment procedure execution to see the logs. How to Restart Failed Workers For Oracle E-Business Suite Release 12.
How to Change the Patch Run Purge Policy Enterprise Manager periodically purges Patch Manager deployment procedure execution data. As a result, older patch runs may not be accessible in Patch Manager. To change the purging frequency, run the following PL/SQL block connected to the repository as SYSMAN: BEGIN MGMT_JOBS.drop_purge_policy('SYSPURGE_POLICY'); MGMT_JOBS.
14 Customization Manager Introduction Customization Manager automates the process of packaging, releasing and reporting customizations for a single Oracle E-Business Suite instance or multiple Oracle E-Business Suite instances. It provides capabilities to integrate with third-party source control repositories to access customizations that need to be packaged. It also integrates with Patch Manager for deployment of custom patches to one or more Oracle E-Business Suite instances.
format (RTF) for Microsoft Word, PDF, or Microsoft Excel. • Leverages Oracle Enterprise Manager infrastructure for distributed processing. • Provides an interface to manage custom applications across the enterprise.
File Manifest The file manifest contains a list of files to be included in a package. File Metadata Repository The File Metadata Repository stores metadata information of custom files used to create customization packages. This information can be used to manage and catalog customizations within the system. Technology Stack Details The Technology Stack Details for a package is a snapshot of the technology stack properties for the Oracle E-Business Suite instance where the package was compiled.
Applications Standards Validation Customization Manager has a standards checker to check that the files included in a custom package meet certain coding standards. This checker tests all code for standards compliance and cannot be turned on or off. Some standards are mandatory and will result in failure when Customization Manager attempts to build the package. Other standards are recommended, and the standards checker will give a warning but the package will be built.
Important: When using the automatic header update feature with CVS, you must have a $Header placeholder within each source file. The placeholder header must be embedded in the source file before the file is checked in into CVS. Also ensure that you change the file name with the correct case within the $Header before embedding the header in the file. Important: When using Subversion, it is required to use Subversion client version 1.2 or above for automatic header update.
• .msg • .odf • .pdt • .pkb • .pkh • .pks • .pl • .plb • .pls • .sh • .slt • .sql • .tpl • .wft • .wfx • .xdf Adding a Header to Custom RTF Files You can add a header to a custom RTF file by adding it to the file's "Comments" property. For example, in Microsoft Word, navigate to the File menu, select Properties, and enter the header in the Comments field as shown in the figure below.
Uploading Existing Custom Patches You can upload a custom patch to Customization Manager repository: The upload option is provided to upload existing custom patches created in the Customization Manager repository. On upload, a package with status "Succeeded" is created. The status can move to status "Released" or "Obsoleted" as other customization packages. One or more NLS patches can be uploaded for a given package. Once uploaded, the patches can be deployed using Patch Manager.
within the file driver file for selected file types like forms, reports, and so on. If not, then the following error is thrown during patching: "File in patch is not a known Oracle Applications file". Customization Manager takes care of this file driver file requirement automatically. Customization Manager implicitly generates a file driver file for the relevant files in a package. During deployment with Patch Manager, these entries are automatically added to the custom product master file driver file.
Customization Manager Main Page The main page for Customization Manager lists packages that are registered in the system. For each package, the following is given: • Name - The name of the package. • ID - The ID of the package. This is always unique across packages. • Release - The Oracle E-Business Suite release level for the package. • Product - The owning product or custom application. • Type - The type of package. Valid values include AOL, FORMS, PL/SQL, XML Publisher, OAF, and Others.
The following functions are available for a given package (depending on its status and ownership): • Using the procedure specified, deploy the package as a patch job in Patch Manager using the Deploy button. Packages with statuses "Succeeded" or "Released" can be deployed. • Update the package metadata using the Update Metadata button. Packages with the statuses Succeeded or Released only can be updated for metadata changes, provided they are owned by the user currently logged in.
File Source Mapping File Source Mapping captures all the required metadata for retrieving custom files from a source control or file system repository. Creating a File Source Mapping is usually performed once as a setup step. You may create one or more File Source mappings, if required. The main File Source Mapping page allows you to search for a File Source Mapping by name. The table lists each mapping with the following: • Name - The name given to the mapping.
when no package is associated with it. To create a File Source Mapping: Perform the following steps to create your File Source Mapping. Note that for the checkout command, you should follow the checkout command syntax provided on the page. 1. Enter the name for the file source mapping. 2. Enter the host name of the file source mapping. You can select the host from the list of values. 3. Enter the stage path.
Command" option. It is also important to ascertain that the user provided within the "host" credentials has the correct permissions on the given host selected for checkout. 6. Optionally enter the environment script to be run before files are checked out, to set any environment parameters ore preprocessing, if required. 7. Enter a description for your reference. 8. Mark the file source mapping as Public if desired.
• Language • Branch - If your source control system requires it and if %branch% token is included within the checkout command. • Tag - If your source control system requires it and if %tag% token is included within the checkout command. • User Name - If your source control system requires it and a %user_name% token is included within the checkout command. • Password - If your source control system requires it and a %password% token is included within the checkout command.
3. Enter the stage path. The stage path is the location of the directory, with write permissions, to where the files would be checked out. 4. Optionally enter the environment script to be run before files are checked out, to set environment parameters. 5. Enter a description. 6. Mark the file source mapping as Public if desired. If it is marked as Public, all users can view the mapping. However, only the owner and Super Administrators can edit it. 7.
Name Description Related User Interface Page Sample Value %product_cod e% Substitution variable for the product code Create/Update Package - File Listing xxco %file_path% Substitution variable for source path Create/Update Package - File Listing patch/115/import %file_name% Substitution variable for file name Create/Update Package - File Listing Custom_Responsibilities.l dt %version% Substitution variable for version Create/Update Package - File Listing 115.
E-Business Suite Mapping Creating an E-Business Suite Mapping is an optional setup step. This mapping is used if Java or PLD file compilation is required. It is also used for report generation. The E-Business Suite Mapping indicates the Oracle E-Business Suite instance which would be used to compile Java or PLD files or used for report generation.
Select the Create button to create a new mapping. To create an E-Business Suite Mapping: Use the following steps to create an E-Business Suite Mapping. 1. Enter a name for the mapping. 2. Enter the name of the reference Oracle E-Business Suite instance. Options for this instance are automatically discovered by Oracle Application Management Pack for Oracle E-Business Suite. 3. Mark the mapping as Public, if desired.
To create an E-Business Suite Mapping using the "Create Like" option: Select the Create Like button to create an E-Business Suite Mapping by copying the details from an existing E-Business Suite Mapping. This procedure can be used typically to create a mirror copy of the E-Business Suite mapping or create another E-Business Suite Mapping with minor modifications without having to enter all the relevant details about the E-Business Suite Mapping.
• Package Name - Enter a user-friendly name for the package. • Product - Enter the owning product application. This product can be a custom product created in Oracle E-Business Suite (not in Customization Manager). • Package Type - Enter the package type. This value is for your own classification and convenience for searching and cataloging. No validation is performed on this field. • Description - Enter a description for your reference. This description becomes part of the package readme.
#Product,SourcePath,FileName,Version,Type,DestPath,LangCode xxco,java\r12\reporter\cpserver,XXCOCustomCp.java,115.1,java,java /r12/reporter/cpserver,Generic xxco,patch\115\import,XXCOConcprog.ldt,115.9,software ldt,patch/115/import,US xxco,patch\115\import,XXCOMenu.ldt,,software ldt,patch/115/import,US xxco,patch\115\import,XXCOReqGroup.ldt,115.3,software ldt,patch/115/import,US xxco,patch\115\import,XXCOResp.ldt,115.7,software ldt,patch/115/import,US xxco,patch\115\import,XXCOUser.ldt,115.
• File Name - The name of the file. This would be substituted in the "%file_name%" parameter in the checkout command. • Version - Optional. The version of the file. The version is only needed if the checkout command will use the version information. This would be substituted to the "%version%" parameter in the checkout command. • Type - The type of the file. Ensure that correct type is selected for the file entry.
Important: Customization Manager strongly recommends that each file included within a customization package has an Oracle-compliant source header present within the file. The following is a sample Oracle compliant header: $Header: sample.txt 10.1 2012/04/06 09:38 lmathur noship $ The header contains the following elements: 3.
• Enter the E-Business Suite information (Conditionally required). The E-Business Suite mapping information is only required when the package contains at least one Java or PLD file. You can select the Oracle E-Business Suite Mapping from the list provided. • Enter the Package Metadata. You can enter the instructions for package application here. These instructions will become part of the package readme. • Enter Comments.
Manager. Note that this validation is done only if you use the Check Prerequisites button in the Patch Details page when creating a patch run in Patch Manager. Note: Prerequisite information entered here for Release 12 packages is only used in deployment by Patch Manager. • Enter Mailing List information. You can enter e-mail addresses for people who should be sent notifications about the package's creation status on the event of success or failure.
To create a package using the Upload option: If you have any legacy custom patches, the same can be uploaded to the Customization Manager repository in context to a new customization package. Click the Upload button from the package search page to upload an existing custom patch. While uploading a custom patch, the following information is required: • Package Name • The release to which the custom patch belongs to.
Updating a Package To update a package, find the package listing in the main Customization Manager page and select the icon in the Update column. To update a package's definition: 1. 2. Enter general information for the package. The Package ID is an auto-generated unique number and cannot be updated. The Package Name cannot be updated as well. • Release - Choose the release for the package. • Product - Enter the owning product application.
product created in Oracle E-Business Suite (not in Customization Manager). 3. • Source Path - The source directory for the file on the source control system or file system. This would be substituted in the "%file_path%" parameter in the checkout command. • File Name - The name of the file. This would be substituted in the "%file_name%" parameter in the checkout command. • Version - Optional. The version of the file. The version is only needed if the checkout command will use the version information.
For Release 12 (and higher) packages, enter in the prerequisite patch numbers that will be used in validation when the package is deployed through Patch Manager. Note that this validation is done only if you use the Check Prerequisites button in the Patch Details page when creating a patch run in Patch Manager. Note: Prerequisite information entered here for Release 12 packages is only used in deployment by Patch Manager. • 4. Enter in Mailing List information.
• Standards Check Results • Status • Language • Public (Choose whether you want results with only Public packages, no Public packages, or either) • Contains File • Contains File with Version (Used in conjunction with "Contains File") • Updated within (Days) • File Source Mapping Name • Branch • Tag • E-Business Suite Mapping Name • Last Updated By Viewing Package Details View package details by selecting its name in the search results table on the main Customization Manager page.
Saved, Failed, Released, and Obsoleted. • Product • Package Type • E-Business Suite Mapping Name – If applicable. • File Source Mapping Name • Owner • Uploaded: Whether this package was created as a result of a patch upload. • Public: Whether this package is shared across all users. History Details (View Package History) The package history provides a chronological view of all the important events in the lifecycle of a package.
View Log Use the View Log button to view the most recent Oracle Enterprise Manager job details for the package. Download Log Use the Download Log button to download the consolidated log for the package creation. Description Any description entered for the package is shown here. Instructions Instructions entered in the Package Metadata field are shown here.
Technology Stack Details The Technology Stack details for a package provide a snapshot of the technology stack properties for the Oracle E-Business Suite instance where the package was compiled. Patch Manager, when deploying the patch, checks the compatibility of the details specified here with the environment to which the package is being deployed. You can first check Technology Stack compatibility yourself by running "Instance Comparison" reports.
Updating Package Metadata Package metadata can be updated to change the status of the package or to push the file entries metadata in the package to the File Metadata Repository. The "Update Package Metadata" page enables you to do the following: • Change the status of the package. You can release or obsolete a package by changing its status to "Released" or "Obsoleted". Once a package is updated to the "Released" status, it can no longer be updated and becomes accessible to other users.
Standards Checker Results The results of the standards checker can be accessed by clicking on the standards checker status. The standard checker results can also be downloaded as a CSV format file by clicking the Download Results button. To view details about the standard checker validations for a given file, click on the overall status against each file. The details about the standard checker validations include the standard name, result and the message.
Creating a Report To create a report, you can • Select a package from the Package Search results page and click Report • Click Report button on the View Package page, or • Click the Create button on the Package Report page. To create a Standard Report: A Standard report gives you details on a single package, including technology stack requirements and the file manifest. 1. Enter in a user-friendly name for your report. 2. Choose Standard for the Report Type. 3.
6. Click Submit. To create a Comparison Report: A Comparison report allows you to compare two packages. For example, you might want to compare technology stack requirements or versions of the files included in the packages. 1. Enter in a user-friendly name for your report. 2. Choose Comparison for the Report Type. 3. Enter the package name in the Primary Package field. This package must have the status of Succeeded, Released, or Obsoleted. 4. Enter the package name in the Secondary Package field.
To create an Instance Comparison Report: An Instance Comparison report allows you to compare the technology stack properties of a package to the technology stack properties of a given instance. By doing this comparison, you can tell if the package can be properly deployed on the instance. In addition, the report lists any missing entries in the file driver file, and compares files and versions within the package to those of the instance. 1. Enter in a user-friendly name for your report. 2.
6. Click Submit. Viewing a Report To access reports, navigate to the Change Management tab > Package Report, or to the Customization Manager home page > Package Report (under Related Links). In the Package Report search results table, the following is shown for each report: • Name - The name of the report. • Type - The type of the report; either Standard, Comparison, or Instance Comparison. • Primary Package - The primary package on which the report is based.
• Download - Click on the link provided to download a ZIP file containing the report. • Details - Click on the Details icon to view details on the report submission job. This link takes you to the Oracle Enterprise Manager Deployments Status page for the report submission. • Delete - Click on the Delete icon for the report to delete the report. Standard Report Output File The Standard Report output file has three sections: • Package Details - Information pertaining to the package's definition.
• File comparison to report missing files or version differences. • Technology Stack Details - For each given property, this table lists the value for the package and the Oracle E-Business Suite instance, and how they compare to each other.
Maintaining the File Metadata Repository The File Metadata Repository stores metadata information on each file. It can be used as a cataloging repository for all custom files within your enterprise. The File Metadata Repository is also aware of the objects within the custom files. This capability typically applies to SQL scripts and PL/SQL packages where the objects are tables, indexes, sequences, views, and so on.
• PL/SQL spec and body (all formats) • SQL files • Oracle Application Framework XML files • XDF The information on a file can be uploaded to the repository in one of three ways: • By uploading a package's file manifest in CSV format to the repository. • By adding metadata for an individual file manually to the repository. • By updating the metadata for a file already in the repository.
5. Enter the language for the file. 6. Optionally enter a description. 7. Click Submit. To update the metadata for a file already in the File Metadata Repository: 1. Select the Update icon for the file in the Search results table in the main File Metadata Repository page. 2. Update the file name, product, source path, destination path, language, and/or description as desired. 3. Click Submit. You can associate one or more customization objects to a given file in the Related Objects region.
• A custom application "definition" is de-coupled from registration. Once an application is defined, it can be registered on one or more instances. • A user must have the "Approve splice request" privilege to hide and unhide custom applications. By default, hidden custom applications will be invisible. A user can check "show hidden custom applications" box to view the hidden custom applications. To define a new custom application: 1. Navigate to the Custom Applications page.
2. Specify an Application Short Name for your application. Note that only alphanumeric characters are allowed, and letters must be lowercase. The application short name is recommended to be prefixed with "xx". 3. Specify an Application Name for your application. 4. Optionally provide a description. 5. Click Submit to save your work.
2. Select the custom application you wish to discover and click Submit. You can use the Search feature to narrow down the results the table. To validate a custom application: Existing registered applications can be validated. For more information on validation, see: Validation of Custom Applications: Examples, page E-1. 1. Navigate to the Custom Applications page. Click the "Custom Application Requests" link under Related Links. The Custom Application Requests page appears.
2. Enter in the Application Short Name for the application. You can use the LOV provided. Note that the Application Name defaults in. 3. Enter in the Oracle E-Business Suite instance. You can use the LOV provided. Note that the Preferred Credentials need to be set for this Oracle E-Business Suite instance. 4. Select "Generate Readiness Report for Online Patching" if desired.
2. In the Auto-Correct Custom Application page, enter the following: • Custom Application's Schema Password. If you do not enter a value, the application short name is used by default. • Email addresses for users to be notified regarding this request. (Optional) • Justification (Required) 3. Click Submit. 4. You can view your request in the Change Management dashboard, under Change Approval Requests.
14-50 5. Click on the name of the request to view details. 6. You can download the splice log if the corresponding job for your request has been purged and no longer exists in the Enterprise Manager system.
To register a custom application on an Oracle E-Business Suite instance: 1. Navigate to the Custom Applications page. Click the "Custom Application Requests" link at the bottom of the page. The Custom Application Requests page appears. Select a request, and click the Register button. Alternatively, you can also click the Register button on the Custom Application details page. 2. Enter in the Application Short Name for the application. You can use the LOV provided.
To view details of custom application: View details of a custom application by navigating to Custom Applications, selecting the application name, and clicking the View button. Details include: • List of instances where custom application is present with status validated/not validated. If the status is not validated, it is recommended to use the Validate button to launch a validation request. A valid status ensures that custom patches for the given custom application can be applied on that instance.
• List of packages that have been created for the custom application. To track details of a custom application request: A custom application request can be used to register or to validate a custom application on a given instance. 1. Navigate to the Custom Applications page. Click the "Custom Application Requests" link at the bottom of the page. The Custom Application Requests page appears. Select a custom application request from the table and click View. 2. Details for the request will be shown.
To execute a job to register or validate a custom application when the change approval system is enabled: 1. Confirm that the request to execute the job to register or validate the custom application has been approved. To do this, navigate to the Custom Applications page. Click the "Custom Application Requests" link at the bottom of the page. The Custom Application Requests page appears. Approved requests will be listed with the Status "Approved". 2.
A Target Types Target Types The following table lists details of the individual target types shipped in the management pack. Target Types Target Type Applicable Oracle E-Business Suite Release Description Oracle E-Business Suite All releases Target representing entire Oracle E-Business Suite instance. Oracle Applications Service All releases Target representing all the services provided by Oracle E-Business Suite.
A-2 Target Type Applicable Oracle E-Business Suite Release Description Oracle E-Business Suite Node All releases Target representing an individual Oracle E-Business Suite node. Oracle Concurrent Manager All releases Target representing the concurrent manager. Internal Concurrent Manager All releases Target representing the internal concurrent manager. Oracle E-Business Suite Workflow All releases Target representing all the members of the Oracle Workflow infrastructure.
Target Type Applicable Oracle E-Business Suite Release Description Forms Listener for Oracle E-Business Suite 11i 11i Target representing the Forms listener in an Oracle E-Business Suite 11i instance that is running in socket mode. Forms Servlet for Oracle E-Business Suite 11i 11i Target representing the Forms listener in an Oracle E-Business Suite instance that is running in servlet mode.
B Pre-validation for Discovery Prevalidation Checks for Discovery The following table lists the checks used in the prevalidation step of discovery. Category Sub category Description Applicable Releases of Oracle E-Business Suite Apps Context File Number of Context Files A minimum of one (1) context file must be there. For 11i and 12.1.X A minimum of two (2) context files must be there. 12.2 and above Context name should not be empty.
Category DB ContextFi le EMGC Compone nts B-2 Sub category Description Applicable Releases of Oracle E-Business Suite Number of nodes Only one applications node per host. 11i and 12.1.X Only two applications nodes per host: One for the run edition and one for the patch edition. 12.2 and above EBS System Name Oracle E-Business Suite system name must be the same in all context files. For all releases Context variables Mandatory context variables must be there.
Category Sub category Description Applicable Releases of Oracle E-Business Suite OS User Agent OS user and Oracle E-Business Suite OS user must be same or must be in the same OS user group. All releases Preferred credentials Preferred credential must be set for the host in which the run edition WLS admin server is running. 12.
C Supported File Types in Customization Manager Supported File Types The following table lists the supported file types in Customization Manager. You can include files of only these types in your custom packages. The Object Action column lists the action that AutoPatch performs on files of the given type.
C-2 File Type Name Source Extension Description Object Action xls xls Microsoft Excel file copy mmb mmb menu file copy java java Java file compile and deploy under $JAVA_TOP zip zip zipped file copy class class Java class file copy jpg jpg JPEG image file copy bmp bmp bitmap image file copy dbc dbc file used for database connection copy doc doc Microsoft Word document file copy dot dot Microsoft Word template file copy drv drv driver file copy fmx fmx compi
File Type Name Source Extension Description Object Action sql sql SQL script copy and execute as APPS wft wft Workflow Text copy and upload using WFLOAD XML xml Extensible Markup Language file copy BC4J XML xml Oracle Application Framework - BC4J XML file customizations compile and deploy under $JAVA_TOP dll dll dynamic link library copy mmx mmx a kind of menu file copy sym sym always accompanies a dll copy tif tif image file (Tagged Image File Format) copy sh sh Bourne
C-4 File Type Name Source Extension Description Object Action sqlj sqlj SQLJ file copy ini ini Java Parameter File copy xsl (non-dbdrv) xsl XML Style Sheets (not used in database driver) copy create_view sql Create or Replace View Script copy and execute as APPS create_trigger sql Create or Replace Trigger Script copy and execute as APPS create_type sql Create or Replace Type Script copy and execute as APPS create_index sql Create Index Script copy and execute as APPS seed_d
File Type Name Source Extension Description Object Action js js Javascript file copy rpt rpt Oracle Reports file copy jar jar Java archive file copy Pls pls PL/SQL package specification copy and execute as APPS Pks pks PL/SQL package specification copy and execute as APPS so so UNIX shared library copy Jpx jpx BC4J Substitution copy vsd vsd source file for gif files used in translations copy dtd dtd XML Document Type Definition copy xss xss Extensible Style Sheet de
C-6 File Type Name Source Extension Description Object Action mac mac cfg cfg configuration file copy txt txt plain text file copy uix uix user interface XML copy hct hct HRMS fast formula loader control file copy hdt hdt HRMS fast formula loader data file copy pdt pdt HRMS legislative loader data file copy wfx wfx Workflow XML loader files copy csv csv file from which user-needed data is imported copy ear ear an EJB .
File Type Name Source Extension Description Object Action document htm htm used in document patches; HTML files copy document ldt ldt used in document patches; navigation library files copy and upload using FNDLOAD document css css used in document patches; cascading stylesheet file copy and execute using FNDGFU tld tld tag library definition file copy xsd xsd XML Schema provides a means for defining the structure of XML documents copy XMLP XSL notrans xsl XML Publisher (XDO) non-t
C-8 File Type Name Source Extension Description Object Action XMLP PDF notrans pdf XML Publisher (XDO) PDF templates copy XMLP XML notrans xml XML Publisher (XDO) non-translatable XML templates copy XMLP XSD notrans xsd XML Publisher (XDO) non-translatable XML templates copy jspx jspx JSP document copy java_lib jar Java library (for compilation only) Use jar only for compiling; jar is not included into the patch package_spec sql package specification copy and execute as APPS pac
File Type Name Source Extension Description Object Action create_view_o wner sql Create View Owner Script copy and execute as schema owner create_synony m_owner sql Create Synonym Owner Script copy and execute as schema owner plx plx Oracle Forms library file executable copy dat dat ico ico dmp dmp copy exp exp copy fdo fdo copy frm frm copy hlp hlp inc inc copy inp inp copy msb msb Message Dictionary file copy obd obd online help file copy cmd cmd NT Comman
C-10 File Type Name Source Extension Description Object Action fmt fmt Oracle Forms form source text file copy fpp fpp copy fxp fxp copy imp imp copy mk mk make file copy mmt mmt menu text file copy pc pc Pro*C program copy Scr scr script file generated by the Oracle Scripting Script Builder" tool" copy MSI xml Manual Step File copy ttf ttf TrueType font definition file copy conf conf configuration file to be released along the product copy mdl mdl text file c
File Type Name Source Extension Description Object Action coremif coremif XML file that contains schematic information about graphical representation of the structure (RMIM) copy xcfg xcfg ADF XML configuration file copy rts rts resource bundle file for java related tool is Tecate copy x2h x2h X2h format file for ISD copy ppp ppp copy tag tag copy ora ora Net8 configuration files (listener.ora, tnsnames.
File Type Name Source Extension Description Object Action tpl tpl template files copy amx amx standard XML file copy ftg ftg copy rlt rlt copy ctl ctl SQL*Loader file copy rsp rsp Rapid Install response file copy prc prc Palm Pilot application file copy odb odb Oracle Lite database file required from Mobile Applications copy llt llt software gif gif image file (Graphics Interchange Format) copy msg msg FND Message Loader Text copy OAF Component java Oracle Appli
File Types Description Recommended destination path (relative to product top) sql, package_spec,package_body, create_table, alter_table, create_sequence,alter_sequence,crea te_view,create_trigger, create_type create_index,seed_data,create_syno nym,pkh,plb,pls,pkb, create_table_owner,alter_table_own er,create_index_owner, sql_owner,create_view_owner ,create_synonym_owner SQL, PL/SQL files patch/115/sql software ldt All Generic Loader (FNDLOAD) files patch/115/import/; for example, 'patch/115/im
File Types Description Recommended destination path (relative to product top) JRAD/MDS file Oracle Application Framework-related XML files mds/ gif Image files media pm Perl module perl/ Execution Sequence of SQL File Types The following table lists the execution sequence of SQL file types.
File Type Description Order Of Execution package_body Package body 7 seed_data Custom seeded data SQL script 8 create_index Create index script 9 create_index_owner Create index in custom schema 9 create_trigger Create or replace trigger script 10 sql Generic 11 sql_owner Run SQL in custom schema 11 For example, the type create_sequence will execute before the type create_table or create_table_owner.
D Customization Manager Coding Standards Customization Manager Coding Standards for Files Customization Manager has a standards checker to check the that the files included in a custom package meet certain coding standards. This checker tests all code for standards compliance. Some standards are mandatory and will result in failure when Customization Manager attempts to build the package. Other standards are recommended, and the standards checker will give a warning but the package will be built.
Standard Name Description Java Package Path Standard For Java files within a package, the destination path for the Java file must match its package structure. Other File Standards The following table lists standards that if not met, will result in a Warning but the package will still be built. D-2 Standard Name Description Java SOP Check Java files must not use System.out.print Java System.gc() Check Java files must not use System.gc SQL dual reference check SQL files must not use System.
Standard Name Description Drvx file location check Drvx files must be located under one of following directories: patch/[some dir]/driver, admin/template,admin/template/* Driver File Location Standard Driver files must be located under one of following directories: admin/driver,patch/[some dir]/driver, admin/template,admin/template/* LCT File Location Standard LCT files must be located under one of following directories: admin/import,patch/[some dir]/import,upgrade/[some dir]/import,admin/template,ad
D-4 Standard Name Description XDF Location Standard XDF files must be located under one of following directories: admin/xdf,patch/[some dir]/xdf,patch/[some dir]/xdf/aw/US Absolute URL Check Standard Check for absolute URLs Report Printer Def File Report printer files must be located under one of following directories: reports,admin/template,admin/template/* Form Location Standard Form files must be located under one of following directories: forms,admin/template,admin/template/* JAR Location Sta
Standard Name Description Pkg Replace Check Use CREATE OR REPLACE PACKAGE for package creation. Do not omit OR REPLACE Pkg Create IS Check Package creation must not use IS.
D-6 Standard Name Description Admin Dbdrv none check All files under [PROD_TOP]/admin must have only dbdrv: none NLADD Sql Check There should be no [PROD]NLADD.
Standard Name Description Mview Parallel Standard Materialized Views should not be created with parallel command Mview prebuilt Standard Materialized Views must not be created with ON PREBUILT TABLE option Report Location Standard Report files must be located under one of following directories: reports,admin/template,admin/template/* Import stmt Check Java import statements must reference fully qualified Class names Language check in destination path The destination path for a file entry in the p
D-8 Standard Name Description Java class should not extend error Errors are system exceptions. Classes should not extend them. Java files must have rcs_id All Java files must have the following for source control ID: Java class name check All Java files should have a class with a name that is the same as that of the file name. Java empty if check There should be no empty if statements in Java code. An empty if statement finds instances where a condition is checked but nothing is done about it.
Standard Name Description JDBC TimeStamp Compliance The proper column bind type should be used when sending/fetching DATE columns. Do not use Types.TIMESTAMP or OracleTypes.TIMESTAMP. Do not use ~FILE or ~PATH in .drvx files ~FILE and ~PATH cannot be used in a dbdrv: command in a .drvx file, even within checkfile. A .drvx file is not loaded into the database. dbdrv: fdfcmp should not be called The database driver should not call fdfcmp. Files with .
Standard Name Description dbdrv: java UnzipFile.class must have correct syntax Java UnzipFile.class command must contain the following syntax: exec java oracle/apps/ad/jri UnzipFile.class java The file must also have the .zip extension. dbdrv: LoadMap.class must have correct syntax The syntax for LoadMap.class must be as follows: JRAD XML files must have file-version attribute JRAD XML files must have a file-version attribute to indicate the version of the file.
Object Type Description File Types Table A column type must be a built-in type or a user-defined type owned by a non-editioned user. .xdf Table A base column name should be unique within the table within the first 27 bytes. .xdf, .odf Table A base column name may use the # character only to distinguish the column versions; for example, #. .xdf, .odf Table A table must be owned by an Oracle E-Business Suite product schema, not APPS. .
D-12 Object Type Description File Types Synonym A table synonym must point to the editioning view, not to the table. .sql, .pkb, .pls Synonym Do not install synonyms in non-editioned schemas .xdf, .
E Validation of Custom Applications: Examples Validation of Custom Applications: Examples The following table lists examples of issues that might be discovered in validating a custom application. Recommended solutions are also provided. These examples apply only to Oracle E-Business Suite Release 11i.
E-2 Issue Recommendation for Release 11i The file $APPL_TOP/admin/xxcus tprod.txt does not exist. Create or replace file $APPL_TOP/admin/xxcustprod.txt. The contents should be : The file $APPL_TOP/admin/xxcus tterr.txt does not exist. Create or replace file $APPL_TOP/admin/xxcustterr.txt with file : The entry for xxcust is missing in FND_APPLICATION_TL Update FND_APPLICATION_TL with the following sql: %%% Single-product product data file format 11.5.
Issue Recommendation for Release 11i The entry for product xxcust is missing from FND_PRODUCT_INSTA LLATIONS Insert the information about product xxcust in FND_PRODUCT_INSTALLATIONS with following SQL: INSERT INTO FND_PRODUCT_INSTALLATIONS(APPLICATION_ID, ORACLE_ID,LAST_UPDATE_DATE,LAST_UPDATED_BY,CREATI ON_DATE,CREATED_BY, LAST_UPDATE_LOGIN,PRODUCT_VERSION, STATUS,INDUSTRY,TABLESPACE,INDEX_TABLESPACE,TEMPO RARY_TABLESPACE,SIZING_FACTOR, INSTALL_GROUP_NUM,DB_STATUS,PATCH_LEVEL ) VALUES ( 50001, 50001, sy
Issue Recommendation for Release 11i The database is missing user xxcust Create database user xxcust Give appropriate grants to the user by running the necessary SQL statements: • grant create session, alter session to xxcust • grant create type to xxcust • grant create database link to xxcust • grant create any outline, alter any outline, drop any outline to xxcust • grant analyze any to xxcust • grant create sequence, create table to xxcust • grant create cluster to xxcust • grant CREAT
Issue Recommendation for Release 11i Entry for the product xxcust in $APPL_TOP/admin/topfil e.txt does not exist Edit $APPL_TOP/admin/topfile.txt to insert the given below entry at the end: xxcust Please replace with appropriate value. Environment variable XXCUST_TOP not defined Run AutoConfig to generate the environment variable XXCUST_TOP Directory $APPL_TOP/xxcust/11.5.0 does not exist. Create directory $APPL_TOP/xxcust/11.5.0 Directory $APPL_TOP/xxcust/11.5.
E-6 Issue Recommendation for Release 11i File $APPL_TOP/xxcust/11.5.0 /admin/driver/xxcustfile.d rv does not exist. Create file $APPL_TOP/xxcust/11.5.0/admin/driver/xxcustfile.drv with following contents: File $APPL_TOP/xxcust/11.5.0 /sql/XXCUSTNLINS.sql does not exist. Create file $APPL_TOP/xxcust/11.5.0/sql/XXCUSTNLINS.sql with following contents: File $APPL_TOP/xxcust/11.5.0 /admin/sql/XXCUSTNLA DD.sql does not exist. Create file $APPL_TOP/xxcust/11.5.0/admin/sql/XXCUSTNLADD.
F Known Product Limitations Known Product Limitations 1. Use of the native Oracle Enterprise Manager patch mechanism to apply core technology patches (Developer Forms, Application Server, Database or other standalone technologies) against Oracle E-Business Suite managed targets should NOT be done under any circumstances.
F-2 4. Creating copies of the out-of-box cloning procedures is not supported. The "Create Like" feature is provided for customers to extend the cloning functionalities based on their own specific business needs. 5.
G Third-Party Product License Information Third-Party Product License Information This section includes third-party license information for certain third-party products that are part of Oracle Application Management Pack for Oracle E-Business Suite Release 12.1.0.2.0. Oracle acknowledges that the following third-party proprietary and open source software are used in the provided programs covered by this documentation.
See http://www.gnome.ru/projects/vsdump_en.html The Office Open XML experimental support had additional dependencies, with their own licensing: • XML Beans - http://xmlbeans.apache.org/ Apache Licence Version 2.0 - http://www.apache.org/licenses/LICENSE-2.0 • DOM4J - http://www.dom4j.org/ BSD Licence - http://www.dom4j.org/license.html • Jaxen - http://jaxen.org/ Apache Style Licence - http://jaxen.org/license.html • OpenXml4J - http://www.openxml4j.org/ BSD Licence or Apache Licence Version 2.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: 1. You must give any other recipients of the Work or Derivative Works a copy of this License; and 2. You must cause any modified files to carry prominent notices stating that You changed the files; and 3.
the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Office Open XML (OOXML) xsds: These were downloaded as part of the Office Open XML ECMA Specification from These are included within the Apache POI distribution, and are available under compatible licensing terms.
Index A Administration of Oracle E-Business Suite, 8-14 AD Patch Log, 13-30 amp.properties replaced by Preferences, 2-5 APPS password changing, F-2 AutoConfig, 4-1 Availability Status charts, 8-7 C Change approval framework, 7-5, 12-2 Change Management dashboard, 12-2 Changing the APPS password, F-2 Cloning, 11-1 custom steps in deployment, 11-38 diagnostic tests, 10-3 for Oracle E-Business Suite Release 12.
saving a package, 14-29 sharing a package, 14-41 standards checker, 14-4, D-1 updating a package, 14-27 updating package metadata, 14-33 D Deleting an Oracle E-Business Suite instance, 416 Deployment Procedure Manager (Oracle Enterprise Manager), 13-29 Diagnostic tests, 10-1, 12-5 cloning, 10-3 Customization Manager, 10-12 Patch Manager, 10-10 user monitoring, 10-15 Discovery, 4-6 customizing, 4-7 Discovery Wizard, 4-2 log for troubleshooting, 4-7 multiple Oracle E-Business Suite targets, 4-6 preparatory s
diagnostic tests, 10-10 extending deployment, 13-29 features, 13-1 patch run, 13-8 restarting failed workers, 13-30 troubleshooting, 13-31 upgrade considerations, 2-4 Patch run, 13-8 copying, 13-28 Preferences, 2-5, 6-1 Preferred credentials, 5-8, 5-11, 12-4 Prevalidation in discovery, B-1 Privileges, 7-1, 7-7 Change Management, 7-5, 12-2 Provisioning Manager (Oracle Enterprise Manager), 13-29 cloning considerations, 2-4 Patch Manager considerations, 2-4 User monitoring, 8-21 diagnostic tests, 10-15 User s
