Oracle WebLogic and SOA Management with Oracle Enterprise Manager 12c

Transcription

1 Oracle WebLogic and SOA Management with Oracle Enterprise Manager 12c Page 1 of 68

2 WebLogic & SOA Management Hands-On Lab Lab Overview Objective: The objective of this lab is to provide exercises designed to showcase the new middleware management capabilities in Oracle Enterprise Manager 12c. Functional Coverage: In this lab you will go through the following new features of Oracle Enterprise Manager Cloud Control: A. Patch Automation B. Monitor Health of Oracle Fusion Middleware C. Diagnose a Hung Application with Business Transaction Management and JVM Diagnostics D. Create and Save User-Defined Configuration Search for WebLogic Server E. SOA Wiring Topology to Metrics Drill Down Page 2 of 68

3 A. Patch Automation A: Patch Automation (Estimated Time to Complete Use Case: 20 minutes) Business Case An integral part of your daily administrator duties is to ensure: zero downtime of production applications by applying WebLogic Server patches in rolling mode across managed servers within a WebLogic Cluster, minimize cost, effort, and time related to patching multiple WebLogic Servers via automating the patching process, and avoid human error associated with manually applying WebLogic Server patches. Beginning with Oracle Enterprise Manager Cloud Control 12c Bundle Patch 1 with My Oracle Support (MOS) Plug-in and Fusion Middleware Plug-in , administrators can use the Cloud Control console and the WebLogic Server Management Pack Enterprise Edition to apply one-off patches and Critical Patch Updates (CPUs) to Oracle WebLogic Servers within an Oracle WebLogic Domain. Administrators can choose to apply patches in a rolling manner across all managed servers in their WebLogic Cluster to avoid downtime of their applications. 1. Patch Oracle WebLogic Servers within an Oracle WebLogic Domain 1.1 This lab assumes that you have been given the URL and credentials to log into Enterprise Manager. Log into Enterprise Manager using the credentials sysman/welcome Click Enterprise menu > Click Provisioning and Patching submenu > Click Patches & Updates. Oracle Enterprise Manager 12c offers deep integration with My Oracle Support (MOS) by providing a comprehensive patch management solution from a single console. Page 3 of 68

4 1.3 Oracle understands that not all datacenter machines have connectivity to the Internet, and consequently, connectivity to My Oracle Support. As such, Enterprise Manager supports both online mode (where the Management Service s host machine has connectivity to MOS) and offline mode (where the Management Service s host machine does not have connectivity to MOS). In this demo environment, we do not have connectivity to MOS so are running Enterprise Manager in offline mode. Page 4 of 68

5 1.4 Notice that while we are in offline mode, the Patch Search region on this page is labelled as Software Library Patch Search. If we had MOS connectivity and been in online mode, this region would connect directly to MOS enabling you to search MOS for relevant WebLogic Server patches. However, in offline mode, you have to search for WebLogic Server patches that have already been manually downloaded into the Enterprise Manager Software Library. 1.5 For the purposes of this demo, some WebLogic Server patches have already been uploaded into the Software Library. We ll search the library for two specific patches we need to apply to our WebLogic installations. First, we will search for WebLogic Server patch number Enter patch number from the Patch Name or Number text field in the Software Library Patch Search region and click the Search button. 1.6 We see that the specified WebLogic Server patch was found in the Software Library. Notice that if Enterprise Manager were configured to be connected to My Oracle Support, we could have been able to view the patch s readme as well as obtain other details on the patch such as the bug fixes in the patch, associated Knowledge Base articles, and the number of downloads for the patch. Additionally, because patches are linked to Oracle Forums, if we were in online mode, we d be able to review feedback from other administrators about the patch, including information on the impact and patch workarounds, if any. Page 5 of 68

6 1.7 In order to apply this patch, we need to add it to a Patch Plan. A Patch Plan enables the administrator to accumulate multiple patches and applicable targets in order to roll out the patches across the environment under a single downtime window. Click the Add to Plan drop down list > Select Add to New. Page 6 of 68

7 1.8 We ll first give this new patch plan a name. Enter a unique name for the plan, for example, Demo Patch Plan, in the Plan Name text field on the Add Patch to Plan dialog. 1.9 Then we will search for the WebLogic Domain to which to apply the patch. Enter riddles_domain in the Search Target Name text field and click the search icon.. Page 7 of 68

8 1.10 Select the Oracle WebLogic Domain target type named /Riddles riddles_domain/riddles_domain from the results table. It should be the first row in the table. Click the Create Plan button A confirmation message appears at the top of the page indicating that the patch plan was completed successfully. Now let s view the plan. Click the View Plan link in the confirmation message. Page 8 of 68

9 1.12 Here we see that the plan contains the one WebLogic Server patch. However, in typical roll outs, the administrator has more than one patch to apply during planned downtime. So let s choose to add another patch to the plan. Click Add Patch button Since we know the patch number for the second patch that we need to apply and we know that it has already been downloaded to the Software Library, let s search the Software Library for the second patch. Click Patch Name or Number link on the Edit Search dialog The second WebLogic Server patch we want to apply as part of this patch plan is patch number Enter patch number from the Patch Name or Number text field on the Edit Search dialog and click the Search button. Page 9 of 68

10 1.15 We see that the specified WebLogic Server patch was found in the Software Library. We ll add it to the existing plan. Click Add to This Plan button from the Patch Search Results page We want to apply this patch to the same domain as we chose earlier. Select the Oracle WebLogic Domain target type named /Riddles _riddles_domain/riddles_domain from the results table. Click the Add Patch to Plan button. Page 10 of 68

11 1.17 We see that the existing patch plan has been modified to include the newly selected patch. So, now two patches will be applied as a result of deploying this patch plan. Let s continue on to view the deployment options of this patch plan. Click on Deployment Options In the How to Patch section of the deployment options page of the patch plan, you can choose to apply the patch plan in either a rolling or parallel fashion. Rolling mode is selected by default if the WebLogic Domain contains a cluster. Rolling mode applies patches across multiple managed servers in a cluster - one managed server at a time. Whereas, parallel mode applies patches on all managed servers at the same time. The benefit of applying patches in a rolling manner is that there would be no downtime incurred to applications deployed to the cluster. In the Customization section of the page, we could optionally choose to customize the procedure being used to apply the patches. For example, if we wanted to run some custom scripts as part of the patching process, we could edit the procedure to reference those additional steps/scripts. In the Rollback section of the page, you Page 11 of 68

12 could choose to enable rollback mode. This rollback feature can be leveraged after patches have already been applied to the domain but have introduced new, unwanted problems. To rollback the offending patches, you would create a new patch plan with the relevant patches to be uninstalled and their associated domain and enable the rollback feature to automatically rollback or deinstall the already applied patches Scroll down the Deployment Options page. Toward the bottom of the Deployment Options page, we can see the types of credentials required for applying patches to a WebLogic Domain - administrator credentials to the WebLogic Domain being patched (such as weblogic/welcome1) as well as Oracle Home credentials for each WebLogic installation (Beginning with Enterprise Manager release 12, we have introduced a new target type for Oracle Home. Because WebLogic software is not installed by Oracle Universal Installer, it does not have an Oracle Home. When you see the label Oracle Home for WebLogic installations, it is referring to its WebLogic Server home location.). In this environment, preferred credentials have already been created for the administrator we are logged in as (sysman). Click the Next button. Page 12 of 68

13 1.20 In order to apply the patches in the patch plan, we must first perform validation checking. Validation allows us to do an upfront pre-requisite check without actually patching the environment. There are two parts to such validation checking. The first part is against My Oracle Support for patch conflicts. Patches are checked for conflicts amongst the patches selected and any patches already applied to the WebLogic installations. If conflicts are detected, we could file Merge requests directly and the process is completely automated without needing to manually file a Service Request with support. If a Merge patch is already available for the conflict set, then we could replace the patches in the patch plan and proceed with the roll out. The second part to validation checking is a real-time check on the domain directly. This analysis involves running checks such as whether the latest version of Smart Update is installed and system space for the target being patched. Since this demo environment is in offline mode, the patch conflict checks are done directly on the target. Any patch conflicts found have to be manually taken care of via the regular service request path. In online mode, however, the entire process can be automated. Click the Analyze button. Page 13 of 68

14 1.21 Analysis will take about 10 minutes to complete. To save time, we will review a patch plan that was already successfully analyzed. Click the Patches & Updates link in the upper left corner of the page. Page 14 of 68

15 1.22 Click on the successfully analyzed patch plan named October_Patch_Plan We can see that this patch plan is ready for deployment. Validation was completed and no conflicts were found. We can now proceed to deploy the patch plan in order to actually get the two patches applied to all WebLogic homes in the domain. Click the Deploy button. Page 15 of 68

16 1.24 Deployment is now in progress. We can drilldown to track progress of patch application. Click Show Detailed Progress We can set the status of the patching procedure to automatically refresh at predefined intervals so we can track progress of patch application over time. Select Real Time: 30 Second Refresh from the View Data drop down menu. If we scroll down the page, we can understand the various steps that occur as part of the patching operation. For instance, we first perform some prerequisite checks to ensure targets are supported for patching, credentials are valid, installed Smart Update is of the latest version (if it isn t, we upgrade to the latest version of Smart Update), etc. We then, for a patching operation running in parallel mode, iterate through all the WebLogic homes (starting with the Administration Server home, then the managed servers associated with the selected domain, then other homes within other domains that share binaries with the patched domain) and start a blackout for the target, stop WebLogic Server, apply patch, stop blackout, start WebLogic Server. Lastly, we refresh the configuration data for the impacted WebLogic Servers and store the updated information in the Management Repository such that after patching is completed, the patches just applied appear in the Cloud Control console for that particular home. Page 16 of 68

17 Page 17 of 68

18 1.26 Applying these patches to the three WebLogic Server homes in the selected Domain should take about 22 minutes. When the patching procedure is complete, its status will be listed as Succeeded. To save time, move on to the next use case in this hands-on lab. After completing the next use case, return to this provisioning status page to see that its status is listed as Succeeded. While we just saw how to use the Oracle Enterprise Manager Cloud Control 12c console to apply patches to all WebLogic homes within a domain, we could have instead used the Enterprise Manager Command Line Interface (EMCLI) to further automate the patching operation. Page 18 of 68

19 B. Monitor Health of Oracle Fusion Middleware B: Monitor Health of Oracle Fusion Middleware (Estimated Time to Complete Use Case: 15 minutes) Business Case An integral part of your daily administrator duties is to ensure that your Oracle Fusion Middleware and WebLogic deployments are up and performing as expected. In addition, it is also important to understand relationships between components of the farm/domain in order to understand the impact of problems either upstream or downstream from the problematic component. Having such data easily and quickly available is critical to efficiently managing your Oracle Fusion Middleware software. 2. Monitor Health of Oracle Fusion Middleware 2.1 This lab assumes that you have been given the URL and credentials to log into Enterprise Manager. Log into Enterprise Manager using the credentials sysman/welcome Navigate to the Middleware home page. From any page, Targets -> Middleware: Page 19 of 68

20 2.3 On the Middleware home page, expand the EMGC_GCDomain row in the table. Click on the GCDomain target name 2.4 From the GCDomain Home page, access the WebLogic Domain menu and click on Routing Topology. Page 20 of 68

21 2.5 You can view the routing topology of the domain to understand how the components are configured to communicate with one another. Expand relevant nodes in the topology to understand what they include. How many WebLogic Servers are there in this domain? Are any managed servers in the domain down? How many incidents are there across the topology? Page 21 of 68

22 2.6 Click on the Filter icon and choose to display JDBC data sources Node Types on the topology. Notice how the diagram changes with JDBC data sources visible. Page 22 of 68

23 2.7 Choose to annotate performance metric names and values onto the topology. Notice how the topology changes with the performance data visible. Page 23 of 68

24 2.8 Change the layout of the topology to a Top Down layout. Notice how the topology changes with the top-down view. Page 24 of 68

25 2.9 Determine the host name, Oracle Home, Middleware Home and Domain Home for a managed server (e.g. EMGC_OMS1 managed server) displayed in the topology without leaving the topology view. Hover over the EMGC_OMS1 target, a dialog box will appear with the target name. From this popup, you can determine additional information on the managed server such as the host that it is installed on, some configuration attributes as well as performance statistics. Click more in the lower right hand corner to gain quick and easy access to additional information for that target. Page 25 of 68

26 Properties for the EMGC_OMS1 target are now visible. Additional information is displayed such as the managed server s version, Oracle Home, and Middleware Home. Click the other tabs on this popup to review additional information for this target. Page 26 of 68

27 2.10 Filter the topology to find specific information - for example, to find a particular application deployed to the domain. Click on the binoculars icon, input EMGC in the Name field and select Application Deployment as the Type. Click Find. Page 27 of 68

28 2.11 View the results of the filtering. Notice how a table appears which identifies all application deployments with EMGC in the name. Also notice how the topological diagram has been adjusted such that all but the EMGC application deployments are grayed out Let s drilldown to the emgc application deployment home page from this routing topology view. Hover over the target emgc, and right mouse click. Select Home to go to the Home Page for that target Let s personalize or change the layout of the Home page by doing the following: Change the layout. Add more data to the page (i.e. an availability summary chart and a performance metric chart). Page 28 of 68

29 Click on the Personalization icon next to the timestamp for when the page was last refreshed. You will see new boxes appear to either change the layout or add content Choose Change Layout. Select the two columns above wide area layout. Notice how the page changes. Page 29 of 68

30 2.15 Add more data to the page. Choose Add Content in the lower area. A dialog box appears. Select to add Most Requested to show the most requested Servlets, JSP and Web Services for a Server or Deployment. Click Close. Page 30 of 68

31 2.16 To lock in your personalizations, click Close. Page 31 of 68

32 2.17 This is your newly personalized application deployment home page. These personalization changes apply to all home pages of the application deployment target type for the user that you are currently logged in as Now that we have personalized our application deployment home page, let s drill down beyond the home page to review performance information for the emgc application deployment. While Enterprise Manager provides predefined performance views for managed targets, it also enables each administrator to customize these default views to suit their unique needs. Page 32 of 68

33 To navigate to the out-of-box performance summary for this application deployment, access the Application Deployment menu, click Monitoring to expand a submenu, and then click Performance Summary The default Performance Summary page appears displaying a series of performance metrics being monitored for the application as well as related metrics for the managed server to which it is deployed and the host machine on which the managed server is installed. JSP and Servlet related metrics as well as datasource metrics are also displayed. From this page, you can very quickly gauge the application s health and correlate performance data across metrics as well as targets over the past 24 hours. Page 33 of 68

34 2.20 In order to diagnose performance issues or gain additional insight into the application s performance, you may want to customize this default view to show more information. For instance, you may want to add additional performance metrics to the page so that you can correlate more data with the current metrics shown. Click Show Metric Palette in the upper right-hand corner to add more metric charts to the page. The Metric Palette appears on the far right-hand side. It displays a series of metric category folders which contain various performance metrics. Expand the Deployment Work Manager Metrics folder and select the Work Manager Stuck Threads metric. Notice how the page to the left of the Metric Palette changes - it immediately refreshes and the new performance chart appears. Next drag and drop Work Manager Pending Requests metric onto the same chart. Click Hide Metric Palette. Page 34 of 68

35 2.21 When you modify the charts on the page, you may want to save such changes so that the next time you logon to Oracle Enterprise Manager Cloud Control, the customizations are still available. You can do that by clicking Save Charts in the upper left-hand side of the page. The Save Charts dialog box appears. Provide a name for the new chart set and click OK. When the Confirmation dialog box appears indicating that the chart set has been saved, click OK. The new chart set then appears in the Chart Set dropdown menu. Page 35 of 68

36 2.22 Besides saving a chart set based on customizations to the Performance Summary page, you can also save performance baselines. This is helpful when you know that during a particular point in time your application had heavy load and peak performance, you can save that as a baseline against which to compare future performance levels. To create a baseline, click Overlay menu and then Create Baseline The Create Baseline dialog box appears. Specify a baseline name and click OK. When the Confirmation dialog box appears indicating that the baseline was created successfully, click OK. Page 36 of 68

37 2.24 The newly saved baseline appears in the Overlay menu for future comparison operations You can also customize the timeframe for the data shown on the Performance Summary page. By default the data displayed is that collected over the past 24 hours. However, you can change this default to be the data from the past 7 days, past 2 hours, past 15 minutes, or even customize the timeframe completely via a calendar selection. Click the calendar icon to enter the exact date and time for which you would like to see performance data. Edit the default settings for Start Date/Start Time and End Date/End Time and click OK. Page 37 of 68

38 Notice how the Performance Summary page refreshes to only show data between the time range specified. This customization is quite useful when problems occur in the past and you need to quickly access and correlate historical performance data. Page 38 of 68

39 2.26 Besides correlating performance metrics across related targets (i.e. application to its underlying managed server to its underlying host) on the Performance Summary page, you can also correlate the same metrics across different applications. So if you have an application deployed to a staging environment and the same application deployed to a production environment, there may be times when you want to compare the performance between the two applications. Perhaps the application in production is having problems but the application in staging is not and you want to correlate the performance data across the two environments. Click the Overlay menu and then Another Application Deployment. Notice from the Overlay menu that you can also compare current performance data with past performance data as well. Page 39 of 68

40 2.27 The Search and Select: Targets dialog box appears. Select another application deployment (e.g. EMGC_GCDomain/GCDomain/EMGC_OMS1/empbs) in the table and click Select. Page 40 of 68

41 Notice how the page refreshes and the newly added application s performance data appears in the charts alongside the existing application s performance data. Page 41 of 68

42 C. Diagnose a Hung Application with Business Transaction Management and JVM Diagnostics C: Diagnose a Hung Application with Business Transaction Management and JVM Diagnostics (Estimated Time to Complete Use Case: 15 minutes) Business Case An integral part of your daily administrator duties is to ensure that business transactions are monitored as they flow across tiers. In addition, it is also important to trace transactions across containers as well as to the database and vice versa. In this use case a hung application is diagnosed first using Business Transaction Management and then using JVM Diagnostics to identify the root cause of a specific failed transaction. This can ultimately reduce problem resolution time through integrated features in transaction and JVM monitoring which provide root cause findings in context of the failed or slow performing transaction. 3. Monitor Health of Oracle Fusion Middleware 3.1 This lab assumes that you have been given the credentials to log into BTM. Log into BTM using the credentials weblogic/welcome1. Page 42 of 68

43 3.2 Click on the Operational Health Summary link under Dashboards. This page gives us a roll-up of key metrics for our system and transactions. The indicators will quickly tell us if something is wrong, and the associated number will tell us the actual number of issues. 3.3 Click on Top 10 Services. The Top 10 services dashboard has four tables with the top 10 services in terms of load, uptime issues, response time and faults. This is a good starting point for further analysis, since it gives a good view of the worst performers. Page 43 of 68

44 3.4 Double-click on purchasingclient in the Most Load dashboard. From the dashboards we can drill down into the services detail pages and get a more detailed summary of alerts, dependencies and associated transactions. 3.5 Click on Top 10 Transactions. The Top 10 Transactions dashboard is similar to the previous one, but with relevant tables and metrics from a transaction standpoint. Page 44 of 68

45 3.6 Click on purchasingclient_orderapplication_jsp_action_submit_order. This dashboard also allows us to drill down, in this case into the details for the selected transaction. The transaction drill down page allows you to get information on dependencies, alerts and it also contains a graphical topology view with performance metrics for the selected transaction. The instance tab provides access to individual instances where associated messages can be assembled and sequenced. 3.7 Click on the Instances tab. Select an instance (e.g. customer=epsilon Enterprises) and click on the magnifying glass next to it. In addition to all the aggregates and averages, BTM also offers the ability to look at individual transactions. When we select assemble, BTM will collect all messages related to the transaction. Page 45 of 68

46 3.8 A message should appear asking you to wait for the instance to be assembled. In the inspector we can see and analyze what components were involved, if there were failures or slowdowns. You can also see the Execution Context ID (ECID), which is a global unique identifier of the execution of a particular request in which the originating component participates. You can use the ECID to correlate error messages from different components. 3.9 Double-click on a row with operation type request-response. BTM will even allow us to look at the message itself, both the header and payload, providing invaluable information in context to potential issues and problems. Page 46 of 68

47 3.10 Navigate back to the original screen. From the View drop-down menu select Search Message Log. We can use message logs to diagnose an issue. A customer, Epsilon Enterprises, has called in, complaining about some orders that don t seem to be going through and are getting lost somewhere. Page 47 of 68

48 3.11 Click on Choose Content. In the customer field, enter Epislon Enterprises, select matching and click OK. Change the time drop-down to 1 Hour and click Search. We ll start the diagnostics by looking for all messages related to the customer name We can see a few messages related to this customer and a couple stick out as having a much longer response time than the others. Let s take a look at one of them. Select one of messages with a long response time then expand the View drop-down menu. Select Related Transactions and then select the purchasingclient_orderapplication_jsp_action_submit_order transaction. Now that we have found a suspicious message, we can use this to look at the relevant transaction. Page 48 of 68

49 3.13 In the transaction inspector, we can see that something is wrong in the PurchasingService. Click on the magnifying glass to look at the message content. We can now see in the response that something is wrong with the outbound service endpoint URL, most likely a typo in the service name. Page 49 of 68

50 3.14 Navigate back to the Message Log Search screen. Click on Choose Content and in the customer field, enter Hotel, select containing and click OK. Now we re going to diagnose an issue associated with a hung application. Page 50 of 68

51 3.15 Change the time drop-down to 1 Hour and click Search. We can see that the messages for Hardware Hotels seem to take very long response times, so let s take a closer look at one From the View drop-down menu, select Related Transactions and then select purchasingclient_orderapplication_jsp_action_submit_order. Page 51 of 68

52 3.17 Like in the previous example we ll investigate the associated transaction. In the transaction inspector we can see that something seems to be wrong in the SubmitOrderQSService. Click on the magnifying glass to get to the message content and then click on View XML for the Response. Page 52 of 68

53 3.18 We ll open up the message content to see if there are any clues in there. As we can see in the message response, a java exception is thrown because of a time-out Go back to the transaction instance inspector and right click on the SubmitOrderQSService. Click on Launch JVM Diagnostics. Since this seems to be a Java related issue we ll use the click-out from the transaction instance inspector to go to the JVM Diagnostics page in Oracle Enterprise Manager 12c Cloud Control. This way we ll set the context to when the transaction occurred. Page 53 of 68

54 3.20 Click on Live Thread Analysis. We remember from the message log search that this transaction wasn t the only one affected, so we ll go to the live analysis to see what s going on Click on one of the stuck threads (e.g. [STUCK] ExecuteThread... ). It looks like we have some stuck threads here and we can click on one of the threads to see the stack. Page 54 of 68

55 3.22 Click on the callsocketwithtimeout and Browse Local Objects. Expand frame objects, Method local, impl. In most cases just identifying the bad code would be enough, but let s continue to drill down into the heap since this is a network call and we might be interested in the connection details. Drilling down into the heap we can see that the port we re trying to connect to is Page 55 of 68

56 3.23 Scroll down and expand Method Local (java.net.socket) > impl > address. We can see the hostname we re trying to connect to, which happens to be localhost in this demo. We now know why the transaction seems to be hanging and we have information host and port information we can use for further investigation of this network issue. Page 56 of 68

57 D. Create and Save User-Defined Configuration Search for WebLogic Server D: Create and Save User-Defined Configuration Search for WebLogic Server (Estimated Time to Complete Use Case: 5 minutes) Business Case Oracle Enterprise Manager collects a vast amount of configuration information about each target. Using that information to answer complex questions can be accomplished quickly and easily using Oracle Enterprise Manager s configuration search capability. You have been asked by the middleware manager for a list of Oracle WebLogic Servers running on Linux which are not using the Sun JVM version 1.6.0_24. Use Oracle Enterprise Manager Cloud Control s compound configuration search to provide this information to the middleware manager. 4. Create and Save User-Defined Configuration Search for WebLogic Server 4.1 This lab assumes that you have been given the URL and credentials to log into Enterprise Manager. Log into Enterprise Manager using the credentials sysman/welcome Click on the Enterprise menu and then click on Configuration and select Search. Notice the several predefined configuration searches that Oracle Enterprise Manager offers for Oracle WebLogic Server: Deployed Applications, Data Sources, Web Modules, EJB Modules, and Ports. What we are introducing in this release is the ability to create your own custom configuration search. Page 57 of 68

58 4.3 Click on the Create button to create a new configuration search. 4.4 Select Target Type as Oracle WebLogic Server. Page 58 of 68

59 4.5 Under the section labelled Commonly Used Search Criteria, select Server Information from the Configuration Item drop down list. Under the section labelled Server Information enter Sun for the Java VM Vendor text field (operator=contains) and enter 1.6.0_24 for the Java Version text field. For the Java Version text field change the operator to be is not instead of contains. Click Search when done. 4.6 You will see all WebLogic Servers not using the Sun JVM version 1.6.0_24 across all host servers. Next we can narrow it down to the Linux platform only. Select the Add Relationships button. Page 59 of 68

60 4.7 From the Search And Select Related Target Types to Oracle WebLogic Server dialog, select the Destination Target Type of Host and click the Go button. Select the Relationship Type of Hosted By and click the OK button. 4.8 Select the Add Properties button next to Host (Oracle WebLogic Server ->Hosted By->Host). Page 60 of 68

61 4.9 Expand Operating System and select Name. Click the OK button. Page 61 of 68

62 4.10 Enter Linux and verify contains is selected for Name. Click the Search button You will now see all WebLogic Servers not using the Sun JVM version 1.6.0_24 across all Linux platform servers. Now let s save it so we can use it again. Click the Save As button.. Page 62 of 68

63 4.12 Enter a meaningful name for your custom configuration search (e.g. Smith Oracle WebLogic Servers on Linux without Sun JVM 1.6.0_24). Click the OK button Click the Back button to return to the search home page. Select your newly created Search and click the Run button. Page 63 of 68

64 4.14 You will now see all WebLogic Servers not using the Sun JVM version 1.6.0_24 across all Linux platform servers. Page 64 of 68

65 E. SOA Wiring Topology to Metrics Drill Down E: SOA Wiring Topology to Metrics Drill Down (Estimated Time to Complete Use Case: 5 minutes) Business Case Visibility into the structure of deployed SOA applications and the relationships of the contained components. In-context drill-down into relevant lower level metrics for SOA administrators and architects to investigate performance behaviors. 5. SOA Wiring Topology to Metrics Drill Down 5.1 This lab assumes that you have been given the URL and credentials to log into Enterprise Manager. Log into Enterprise Manager using the credentials sysman/welcome From the Targets menu select Middleware. Go to the SOA Infrastructure target page from the Middleware targets page. Use the /Farm01_FOD_domain / FOD_domain /soa_server1/soa-infra target. Page 65 of 68

66 5.3 From the Deployed Composites select the OrderBookingComposite. 5.4 Click on the Topology tab to view the embedded wiring topology that shows how components within the composite are wired together. Page 66 of 68

67 5.5 Click on the Dynamic sub-tab to look at components which had active invocations. 5.6 Right-click on the OrderProcessor BPEL process and select the Open option to open the BPEL functional views. Page 67 of 68

68 5.7 Browse this view to unfold and examine the BPEL activity metrics. Page 68 of 68