Cloud Control Upgrade Guide | hidden-facts.info
II Copying ADP Agent Zip or hidden-facts.info Failure. For example,/DATA/oracle/gc_inst/em/EMGC_OMS1/hidden-facts.infoties How Do You It captures the complex relationships among various application building blocks in its Delete the OMS target associated with the OMS The thoughts expressed here are purely my own and have no relation to anything yada, yada yada, blah, blah (you get the picture). I follow. applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, set ORACLE_CONFIG_HOME=C:\win\emgc\gc_ .. complex relationships among various business functions, their associated OMS, verifying status, OMS instance base location, permission, 6- 14,
Click the event of interest to view more information about it. Each is described in the following sections. This option shows events in the context of the selected Business Application. Note that for ease of management, KPIs within RUEI are grouped into categories that can be customized to contain related performance indicators. For example, separate categories could be defined for business and IT-related issues, such as user flow completion, visitor traffic, website availability, and so on.
The procedure to do this is described in Section Events corresponding to these alerts are also shown in the Events Without Incidents view of the Incident Manager. When you click the event of interest, information similar to that shown in Figure is displayed.
If none have been added, then the original message is reported. Please consult the Business Transaction Management Installation Guide for instructions on how to configure this connection. Figure Business Transactions Region For each transaction, it indicates: The transaction's current compliance status. The number of transaction instances started during the period.
A transaction instance starts when an instance of the primary operation flow is started. The number of transaction instances that completed during the period. An instance is considered to have completed when both its start and end messages have been observed, regardless of whether condition alerts occurred. The average amount of time a transaction requires to complete. For each transaction instance, this is calculated as the time from when the instance's start message is observed until its end message is observed.
The maximum amount of time a transaction requires to complete. This is the single highest response time from all transaction instances observed during the period. You can click a transaction to view more information about it. This opens the Transaction Home page, where you can view the following regions: Figure Business Transaction Aggregate Flow Region Description of ''Figure Business Transaction Aggregate Flow Region'' The aggregate flow region provides you with a complete picture of the transaction and helps you understand the flow of work through it.
You can use it to identify and resolve issues related to performance, and to isolate the cause of failing components in a business process. Based on the dependencies revealed by discovery, the services that interact within the transaction are also revealed. Additional information is usually available if you move the cursor over the links that connect operations or the operation itself.
This should allow you to identify bottlenecks, faulty components, slow components, and unusually light or heavy traffic.
Figure Operations Region Description of ''Figure Operations Region'' You can expand an operation to view its corresponding endpoints. For each endpoint, the host name and port for the container where the endpoint resides are also displayed, together with its status and performance data. If you right click an endpoint in the Operations or Business Transaction Aggregate Flow region, you can choose to display the tabs associated with the physical operation. The context menu that is displayed when you right-click an operation also provides the option to access the JVMD view or the Request Instance Diagnostics view: You can see stack frames for executing threads, thread state information, aggregate information about the frequency and cost of method execution, information regarding the holding of Java and DB locks, and details about the objects in the Java heap.
JVMD also stores historical data for each JVM it monitors so that you can view data relating to things that have happened in the past and get a sense for historical trends. The Request Instance Diagnostics view allows you to trace the path of a request in a WebLogic domain and to generate a report of all the metrics associated with a particular instance of the request.
Please see Chapter 16, "Getting Detailed Execution Information," for additional information about these views. This will open a new window with the Business Transaction Management console providing extended information about the selected transaction.
The first time you open this window you will need to provide a valid BTM user name and password. Figure Business Transaction Management Console The following sections describe the Tabs display as they apply to a given transaction; similar information is displayed if you look at tabs for a physical operation.
It contains the following elements: A Status pane indicating the overall compliance for the transaction. A Measurement and Baselines pane detailing the number of started and completed transactions, average response times, and maximum response times. If baselines have been defined for the transaction, these are shown as gray lines. A map of the transaction detailing average response times for each transaction link.
Place the cursor over each service icon to obtain detailed performance information for that service. The thickness of the arrows indicates throughput.
The Delay analysis pane, which you can use in conjunction with the map pane, provides a graphical rendering of the proportion of the overall response time that is spent in each hop link of the transaction. Each colored area of the grid corresponds to a transaction link. Clicking within a colored region highlights its corresponding link in the map and displays the percentage of the response time taken up by that hop.
At the bottom of this pane, a graph shows the average and maximum response times, and the number of started transactions. Clicking within the pane displays a vertical red line that shows how the colored proportions correspond to message traffic flows. A grid view showing the logical and physical operations that make up the transaction, and the following instruments for each: It contains the panes described in Table Table Panes Within Analysis Tab Pane Description Performance Provides data about started transactions, completed transactions, condition alerts, average response time, and maximum response time.
The data is displayed in graphic form as well as using a grid view. Conditions Provides information about condition alerts that have been triggered in a given time period: Conditions must have been defined for this information to be collected and displayed. Consumer Usage Displays performance information segmented by consumer for the given time period: Consumers must have been defined and consumer segmentation enabled for this information to be collected and displayed.
The client address is the machine host name from which the request was sent. The table lists all client addresses that sent requests, and displays the aggregated performance measurements associated with each client address. Segmentation by client IP address must be enabled for this data to be collected and displayed. The display distinguishes between warning alerts and failure alerts. The graph shows aggregate measurements for violation alerts.
The grid view lists more detailed information: SLAs must have been created for this information to be collected and displayed. Custom Charting Lets you set up a customized chart and table similar to the Performance pane, but with instruments of your choosing.
Click Choose Instruments, and select the instruments you want displayed in the chart and table. You can select multiple instruments. Custom Breakdown You can set up a custom table of numeric instruments segmented in various ways. Click Choose Instruments and select the instruments that you want displayed in the table. Click Choose Segments and select how you want to segment the measurements. You can select multiple segments.
Business Transaction Management issues the following types of alerts: Service level agreement alerts issued when a deviation occurs from the standards of performance you have defined for a transaction. Condition alerts issued when a condition is satisfied. Conditions can test for faults, specific property values, or a missing message. System alerts issued to provide information about the health of the monitoring infrastructure.
The grid view shows the following information for each alert: To obtain more information about a given alert, click the Inspector icon to open an inspector window. Service level agreement alerts are also reported as events in Incident Manager. For more information on accessing these events, see Section A transaction usually executes many times in a given period. If you have enabled transaction instance logging or if you have enabled fault monitoring, Business Transaction Management tracks the flow of messages included in the transaction and maps these to particular transaction instances.
It assembles the messages for a transaction instance in the following cases: When an alert is generated as a result of a fault, or a condition being met. When you explicitly ask for assembly. Once a transaction instance is assembled, you can use the Instances tab to access detailed performance information for that instance. You can also use the Message Log tab to search for messages containing particular property values. Viewing Aggregate Information In the Instances tab, The ID column of the table lists both instances that have been assembled these have an ID value assigned and instances that have not been assembled these are blank.
Information for each instance shows when it was captured, what the overall response time for the transaction instance was, and values for properties if you have created these. The Show instances filtering control allows you to list instances that have occurred in a set time period or to show only assembled instances. Which instances you choose to assemble depends on what interests you.
For example, you might want to assemble an instance with an unusually slow response time; or you might want to assemble an instance with an unexpected property value. If you are capturing a very large set of messages, you might want to use the Message Log tab to search for a smaller set of messages, based on property values, and then assemble one or more of these.
Inspecting an Assembled Instance You can assemble an instance by clicking the Inspector magnifying glass icon for the instance. This opens a Transaction Instance Inspector. It consists of three parts: The top part of the inspector shows the name of the transaction, the time the assembled instance started executing, its ID, the number of message exchanges, the total messages exchanged, and the response time between the starting and ending messages.
Any warnings or faults are also shown. Move the cursor over the operation name to view the service type, endpoint name, host name, and port. Right clicking an operation allows you to view JVM diagnostics. A grid view shows detailed information for each message included in the transaction instance.
The view includes property values if these have been defined. Right clicking a row allows you to view JVM diagnostics. Clicking the magnifying glass tear-off control for any operation, opens a Message Content inspector window, and displays the contents of the selected message if you have enabled message content logging for that operation.
If instance logging is enabled, you can view information about each message logged in a specified time period, as well as the value of any property associated with a message. You can also use the Message Log Search tool to search for a message or messages that contain property values of interest.
If message content logging is enabled, you can view information about each message logged in a specified time period, as well as its content. In this case, in addition to searching for messages based on property values, you can also search based on the content of any message element free text search.
Business Transaction Management logs message content or instance and property values only if you have done the following: Enabled monitoring for the transaction. Enabled the appropriate type of logging for the transaction instance or message.
Selected one or more operations for message logging. Logged information is stored according to storage settings that you define when you create the transaction. Viewing Message Content The Message Log tab uses a grid view to display a list of messages, showing the arrival time of the request message, the service that includes the selected operation, the location of the endpoint that implements the service, the operation messageand the type of operation.
If there are any properties associated with the operation, their values are shown in additional columns whose title is the property name.
If you have message content logging enabled, double clicking on any message shows you the contents of the message. The set of messages shown in the grid varies depending on the setting of the filters shown at the top of the tab. These allow you to see the following: All operations or specific operations chosen from a drop down list.
Any response, only successful operations, only failures. Messages that arrived within a time interval denoted by the last specified time period, since a certain time, or between two given times. You can use these controls to narrow the selection of messages shown in the grid. After you change filter settings, click Search again to repopulate the grid.
You can further restrict your search by using the Message Search tool accessed from the Choose Content This allows you to search for messages based on their property values or, if message content is enabled, based on message content. This tool is described in the next section. Searching for Messages You can find messages belonging to the current transaction, by clicking the Choose Content This brings up a dialog that includes three areas to use for specifying search criteria: As you enter property, ECID, and free-text values, a search expression is constructed in the text box at the top of the dialog.
To clear the text box and start over, press Clear. Additional information about using Oracle query language to construct your query is available at the following location: Then click Search to repopulate the grid according to your newly defined search criteria. These steps are outlined below. Prepare Database Clusters The first step that should be taken prior to a Level 3 Cloud Control implementation is the configuration of the Primary and Standby database clusters.
The instructions in this document assume that primary and standby clusters have already been configured. A Level 3 setup provisions a standby cluster on the same site as the primary cluster.
The standby cluster provides protection against failure of the entire primary database cluster. By configuring the standby database environment on identical hardware to the primary environment, it is possible to run Cloud Control at full capacity in the event of a failover to the standby.
We configured 2 clusters as follows: Primary and Standby clusters both running Oracle Enterprise Linux 5. If possible, it is recommended to use a SCAN address as it allows for the addition and removal of database cluster nodes without reconfiguration of the OMS database connections.
Prepare Repository Database During the installation of Cloud Control the installer will prompt the user to specify a database to be used as the Cloud Control repository.
If your planned configuration uses a RAC database as a repository, it is recommended to create your RAC database prior to the installation of Cloud Control. This approach - as opposed to installing using a single instance database and then converting to RAC - helps to reduce the overall steps and time taken to complete the configuration. We created a database to be used as the primary Cloud Control repository on the primary database cluster with the name emrep.
This database consisted of the emrep1 and emrep2 instances. It is recommended that these options are enabled when the database is created as by doing so it is possible to avoid having to reconfigure the database when creating and managing the Standby Database later on. For further information and recommendations on the prerequisites for creating the repository database on RAC refer to the following documentation: When creating a highly available OMS tier, more than one management service must be configured.
We had a pair of Linux servers that would be used as OMS servers. These were configured as follows: Both servers running Oracle Enterprise Linux 5. In our example, we staged the installation media and started the installer on the host named oms1.
We chose to create a new Enterprise Manager System using Advanced installation. In Step 5 in the installer, we chose not to install any additional plug-ins at this time. In Step 6 we specified passwords for the WebLogic Domain and Node Manager 9 11 In Step 7 we provided the login credentials for the repository database that we created. Entering a cluster database instance in Step 7 will prompt for the modification of the database connect string. By using the SCAN address to connect to the database it is possible for nodes to be added and removed from the RAC cluster without having to subsequently change the connect string that the OMSs use.MOMO Sothanaigal - Micset
As we are using a cluster database on Oracle Database 11g Release 2, we modified the connect string to specify the SCAN address as follows: This helps to simplify the load balancer setup later on. In Step 10, we configured ports as follows during the installation process: Of these ports, the following are relevant for the SLB configuration later on: The information presented on this screen should be noted.
This can be done by issuing the emctl status oms details command from the OMS server: OMS Console is locked. To ensure secure communication between Cloud Control components, it is recommended to use HTTPS for all agent-oms and browser-oms traffic. As this is the case no further action needs to be taken here. In our case we used the following URL: After Step 1, the Cloud Control topology is as follows: In a highly available Cloud Control configuration, multiple OMS servers are present and users and agent should connect to the OMSs via a load balancer which is able to direct traffic to available management services.
The table below summarizes the F5 objects that were created during the SLB setup: Create Health Monitors Health Monitors check the status of a service on an ongoing basis, at a set interval. If the service being checked does not respond within a specified timeout period, or the status of the service indicates that the performance has degraded, the system automatically takes it out of the pool and will choose other members of the pool.
The Health Monitors were configured using the settings in the table below: These were created with the default settings for a TCP Profile.
Oracle® Enterprise Manager Cloud Control | hidden-facts.info
Each pool can have its own unique characteristic for a persistence definition and the load-balancing algorithm used. The preferred setting of the load balance algorithm for all Cloud Control pools is Least Connections Member. We created pools on the load balancer as follows: Without a Persistence Profile such as this, user sessions could span multiple OMSs, and require the Cloud Control user to login multiple times.
We created a Persistence Profile with the following attributes: Creating Persistence Profile for Secure Console The final load balancer configuration step was to define our virtual servers. A virtual server, with its virtual IP Address and port number, is the client addressable hostname or IP address through which members of a load balancing pool are made available to a client. After a virtual server receives a request, it directs the request to a member of the pool based on a chosen load balancing method.
We created virtual servers for the Secure Console and Secure Upload services using the settings in the table below: This can be seen from the output of an emctl status agent command: All rights reserved Agent Version: Number of XML files pending upload: Available disk space on upload filesystem: Collections enabled Last attempted heartbeat to OMS: This is done with the following command: In order to add them to the Cloud Control environment they should each have an agent installed.
We installed the agents by navigating to Setup Add Target Add Targets Manually and adding the Hosts using the Add Host Targets wizard After the repository hosts are added, the repository itself can be added as a database target by navigating to Targets Databases and using the add target wizard.
As part of this flow, we were prompted to also add the cluster target for the primary database cluster. Configure Software Library In a highly available Cloud Control installation, the Software Library needs to be accessible from each host that will be used as a management service. Because the Software Library is a critical part of Cloud Control infrastructure, the filesystem on which it is placed should be highly available.
At this point we also mounted the filesystem on oms2 using the same mountpoint. Deployment Procedures automate common provisioning and patching operations and are orchestrated and managed from the Cloud Control console.
The following steps outline the procedure that we followed to execute the Add Management Service Deployment Procedure. This was done using the same procedure as was used for deploying the agents onto the database repository servers in Step 3. It runs a series of pre-requisite checks on the target Management Service host and performs a clone of the primary Management Service to add a second OMS.
This showed that there were no pending updates to apply and we were therefore running the latest version of the Deployment Procedure. After ensuring that the latest version is being used, the Deployment Procedure can be accessed by navigating to Enterprise Provisioning and Patching Procedure Library and selecting the Add Management Service Deployment Procedure. We ran the Deployment Procedure by clicking on the Launch button 21 23 The Deployment Procedure provided a guided workflow for adding the new Management Service.
The Deployment Procedure asked for confirmation that prerequisites such as configuration of the Software Library and Load Balancer were completed. As all of these tasks were done in prior steps, we checked the boxes to acknowledge we had performed the setup. The next step of the installer wizard prompts for the destination host and install location for the second OMS.
At this step it was also necessary to provide login credentials for both the source server first OMS host and the target server new OMS host. We setup and used some Host Named Credentials for this step. As we used a shared directory we didn t need to specify source and target staging locations on this step.
We were also asked to provide ports for the new OMS. Notification Method must have been configured from the Setup Notifications Notification Methods page for this. When submitted, the procedure completes the process of adding the second OMS by cloning the software homes from the source server to the target server.
In the event that we should lose one of the OMSs, the Load Balancer will stop directing traffic to it and application availability will be maintained. We are now protected from the loss of a database node in the Repository tier or a Management Service node in the OMS tier.