Using Fusion Middleware Control to Manage WebLogic Server

Overview

Purpose

This tutorial shows you how to use Fusion Middleware Control (FMWC) to manage WebLogic Server 12.1.3 domains.

Time to Complete

Approximately 1 hour

Introduction

This tutorial shows you how to use FMWC to manage different aspects of a WebLogic Server 12.1.3 domain, including:

  • Servers and clusters
  • Application deployments
  • JDBC data sources
  • Users and groups

Hardware and Software Requirements

The following is a list of hardware and software requirements:

  • Web browser
  • Oracle Java SE 1.7.0_15 or later (NOT Java SE 1.8!) (download)
  • Oracle Database 11g or later (Express Edition may work as well but has not been tested) (download)
  • Oracle Application Development Runtime 12.1.3 (provides WebLogic Server 12.1.3, ADF, and JRF required for Fusion Middleware Control) (download)
  • Minimum RAM: 4GB
  • Minimum disk space: 20GB

Prerequisites

Before starting this tutorial, you should:

  • Install all of the software listed in the Hardware and Software Requirements section
  • The database is running
  • Install and configure the general schemas required by ADF using RCU (instructions)
  • Reference: Node Manager tutorial
  • Reference: Configure JDBC Data Source
  • Reference: Using Fusion Middleware Control (FMWC)
  • Created a WebLogic Server domain (NOT ON A SHARED FILESYSTEM) and have domain files set up on all machines where servers run

    Entity Domain Settings
    Mode Development
    Template

    Basic WebLogic Server Domain [wlserver]
    Oracle Enterprise Manager 12.1.3.0 [em]
    Oracle JRF - 12.1.3.0 [oracle_common]
    Allow other default selections

    Admin User weblogic/Welcome1
    AdminServer

    hostname:7001
    Server group: Unspecified

    Node Manager Per-Domain
    Host1: hostname1:5556
    Host2: hostname2:5556
    Credentials: weblogic/Welcome1
    Machines machine1
    Node Manager: Host1:5556
    machine2
    Node Manager: Host2:5556
    Clusters Configured cluster: cluster1
    Servers Two configured servers:
    server1 (machine1) Port 8001
    server2 (machine2) Port 8002
    Both servers are in cluster1
    Server groups: JRF-MAN-SVR, JRF-WS-CORE-SVR, WSM-CACHE_SVR
    Deployments Leave as defaults based on server group selections
    Services Targeting Leave as defaults based on server group selections


  • Started the WebLogic administration server

When your environment is configured, continue with the next topic.

Exploring the Interface

FMWC is a web application that is deployed to the WebLogic administration server. It is based on Oracle Enterprise Manager and provides tools for managing WebLogic Server domains. This first section goes over the interface of the FMWC web application so you can become familiar with its controls. Follow along with the steps below to explore the FMWC interface.

  1. Open a web browser and enter the host name and port address where your administration server is running, followed by the em context to access the FMWC web application.

  2. Login to FMWC with the administrative user you used to create your domain. My login is weblogic / Welcome1.

  3. After logging in, the FMWC home page is displayed. The drop down list in the upper right-hand corner provides a context menu that provides access to the different tools that FMWC provides for managing WebLogic Server domains.

  4. The main domain page that is displayed also provides this same drop down list. The domain control is provided here because the current page that is displayed is at the domain level. When other pages are displayed, this drop down lost control transforms into a control for that level. For example, when the server page is displayed, this control provides management for servers.

  5. The Change Center is displayed in the upper right-hand corner of the page. It provides a drop down list for managing domain changes. My domain is a development domain and is running in Auto-Commit Mode. The change management lock is automatically aquired and my changes are activated as I make them. You can change settings here for how you want change management to work for your domain.

  6. The Change Center also provides a drop down list for managing WLST recordings. FMWC WLST recording works the same way it works within the WebLogic Server administration console. When you use FMWC to make configuration changes in your domain, the WLST commands for those changes are written to a file. You can use the recorded WLST commands as a starting point for writing your own WLST scripts.

  7. The left-hand side of the page provides the Target Navigation tree panel. You use this panel to manage the components of your domain, including applications, servers, clusters, and more.

  8. The upper left-hand corner of the main frame shows a general summary portlet of your domain's administration server and provides a link to open the WebLogic Server administration console. You can move the portlet by clicking its gear icon or by dragging and dropping it on the page. The administration server name is a link. You click the link to view more details about the administration server.

  9. Below the Summary portlet is the Servers portlet. This portlet displays the servers that are configured in the domain, their status, their type, their location, and some useful statistics. Each server name is a link. You click a link to view more details about a server. Note that your screen may look slightly different than mine because I have an extra dynamic cluster configured. This will not affect your experience.

  10. To the right of the Summary portlet is the Clusters portlet. This portlet displays the clusters that are configured in the domain, the number of servers configured in the cluster, and more. Each cluster name is a link. You click a link to view more details about a cluster.

  11. Below the Clusters portlet is the Deployments portlet. This portlet displays the applications that are deployed in the domain, their status, and where they are deployed (targeted). Each application name is a link. You click a link to view more details about an application.

  12. Scroll down to the bottom of the main page to view the Oracle WebLogic Domain Resource Center portlet. This portlet provides helpful information for getting the most out of using FMWC to manage WebLogic Server domains.

Now that you have become familiar with the FMWC interface, let's work with WebLogic servers and clusters.

Managing Servers and Clusters

FMWC provides management features for servers and clusters. It enables you to start and stop, monitor, and manage components for servers and clusters.

Your Node Managers should be running on all machines in your domain before starting this section.

Servers

  1. Select server1 in the Servers portlet to display the servers detail page.

    You could have alternatively selected the server in the navigation tree.

    You could also have selected Environment > Servers from the main domain drop down list control and clicked the server on the servers page.

  2. Click Start Up to start server 1. Note that after the server is started you can click Shut Down to stop the server.

  3. The server may take awhile to start. The FMWC console displays a window that shows you the status of the operation. Wait until FMWC informs you that the server has started.

  4. Review the Summary portlet. It provides information about the selected server, including its WebLogic version, state, health, server type, cluster membership, and more. Some of the values can be clicked to get more information.

  5. The server page displays statistics about the components that are running on the server. These values can also be clicked to get more information.

  6. The server page displays a chart that shows some high-level performance figures. You can switch between chart and table views. Servers are not being loaded with requests so there is not much to display.

  7. Scroll down the page. The server page displays the applications that are deployed to the server and some information about each application. You can click each application to get more detailed information.

  8. Scroll further down the page. The server page displays the most requested components that comprise the applications that are deployed to the server and some high-level performance figures. Some components can be clicked for more details.

  9. Experiment with this page for a couple of minutes to see what information you can find. Many of the links pop open a chart that provides a historical account of data. These charts continuously update while they are open. Your experimentation should include experimenting with the different options provided in the drop down context menu.

  10. Repeat these steps with server2. When you are finished, server1 and server2 should both be running.

Next up is managing WebLogic clusters.

Clusters

  1. Select cluster1 in the navigation tree to display the clusters detail page.

  2. The clusters page provides a drop down list that enables you to perform operations at the cluster level. You can also start and stop all of the servers in the cluster by clicking Start Up or Shut Down on this page. When you click the cluster name at the top of the page, it navigates you back to the main clusters page. The up arrow indicates that all of the servers in the cluster are running.

  3. The Summary portlet shows a summary of the cluster's configuration settings.

  4. The Deployments portlet shows a summary of the applications deployed to the cluster and some high-level metrics.

  5. The Response and Load portlet displays a chart of the cluster's activity. This is an aggregate figure that represents all of the servers in the cluster.

  6. The Servers portlet shows the servers that are members of the cluster, their status, server type, location, and some associated metrics. Some values can be clicked for navigating to server resources or viewing more details about metrics.

  7. Explore some other FMWC tools available at this level. These tools are also available at other levels, but may behave slightly differently at each level. Click the WebLogic Cluster drop down list control and select Routing Topology to display an interactive image of the cluster.

  8. FMWC displays a diagram that depicts the topology of cluster1, including the servers of the cluster and the database associated with the cluster.

  9. Click the arrow on the right-hand side of the window to open a panel that enables you to modify what is displayed.

  10. Select JDBC Datasource to show the data sources that are configured for the cluster.

  11. Click Hosts to view the hosts that WebLogic is configured to use.

  12. All IP addresses that are configured for use within the domain are displayed. Your image will look different than mine, depending on your domain configuration settings.

  13. Click the arrow to collapse the pane and return to the diagram view.

  14. Use the zoom control to resize the diagram so you can see it easily.

  15. Now you should see all of the data sources that are configured for cluster1. The data sources are targeted to the cluster so they are shown at this level appropriately.

  16. Select Host in the View By drop down list to show how your cluster is configured across machine boundaries.

  17. Your diagram should look similar to the image below. You should have two machines, with a server running on each machine, and a database connection from each server to the database.

  18. Click the Shot Entire Domain button for another view of the domain's topology.

  19. The display showed only the cluster1 perspective previously. If you have other clusters configured, this view shows them as well. Again, your diagram will be different than mine. In the diagram of my environment, notice that the dyncluster1 servers each have a downward arrow next to them. This indicates that the servers are not running. They also have a connection to the same database, but because the host name is set differently the diagram shows it as a separate database. If you change the View By field back to Middleware, then the view would change to show the cluster configurations.

  20. Click the line that connects your servers to the database to view the JDBC URL of the connection.

  21. Hover your mouse over the ORCL database icon in your diagram, and then over the symbol to view configuration settings for the database.

  22. Repeat the same steps for one of your servers to view its configuration settings.

  23. While the server information window is open, click more to see more information.

  24. Click the icon to expand the server to view its applications. We don't have any applications of our own deployed yet so only internal applications are displayed.

  25. Now let's view the MBean browser. Click the WebLogic Cluster drop down list control and select System MBean Browser.

  26. The MBean browser page opens up to the configuration MBean tree at the cluster1 level. You can alternatively browse through the tree to find any configuration MBean in the domain.

  27. The right-hand pane shows the details of the selected MBean attributes. You can click the Operations tab to view the available operations for the MBean. You can click Show MBean Information for more details. You can also change values on the right-hand side for MBeans with RW access and click Apply to set your changes.

Now that you have learned to manage WebLogic servers and clusters, let's work with application deployments.

Managing Application Deployments

FMWC enables you to manage your Java EE applications, including deployment, redeployment, working with deployment plans, monitoring, and more. Follow these steps to learn how to manage applications.

  1. Click the WebLogic Domain drop down list control and select Deployments.

  2. The top half of the Deployments page displays graphics that show the state of applications that are deployed in the domain.

  3. The bottom half of the page displays a table that lists the applications deployed in the domain and a toolbar of commands you can execute on each application. The toolbar enables you to deploy, redeploy, undeploy, start and stop applications, and more.

  4. Upload the SimpleAuctionWebApp.war file to your machine where the AdminServer is running. Click Deploy to deploy a new application

  5. A deployment wizard guides you through the deployment process. Select the Archive or exploded directory is on the server where Enterprise Manager is running option and enter the location where you uploaded the application file.

  6. Select the Create a new deployment plan when deployment configuration is done option.

  7. Select the Deploy this archive or exploded directory as an application option.

  8. Click Next.

  9. Select cluster1 as the deployment target.

  10. Click Next.

  11. Leave all of the default settings for application name, context root, and distribution fields. Review these values.

  12. Leave all of the default settings for other options.

  13. Click Deploy to deploy the application to cluster1. You are not configuring security or other advanced settings so you do not click Next.

  14. Wait for the application to deploy until you get a Deployment Succeeded status message from FMWC.

  15. Verify that the application is deployed, is in an active state, and is targeted to cluster1.

  16. Expand the application in the console to view more detailed deployment information.

  17. Do not execute this step. Note that you can start the application so that it begins servicing all client requests or only administration requests.

  18. Do not execute this step. Note that you can stop the application gracefully or forcefully, or place it into administration mode for administration requests.

  19. Do not execute this step. Note that you can redeploy or undeploy the application.

  20. Click Fetch Deployment Plan to view the application's plan.

  21. Experiment with the Deployments page for a few minutes.

Now that you have learned to manage application deployments, let's work with JDBC data sources.

Managing JDBC Data Sources

FMWC enables you to manage your JDBC data sources, including creating, modifying, managing life cycle operations, and more. Follow these steps to learn how to manage JDBC data sources.

  1. Click the WebLogic Domain drop down list control and select JDBC Data Sources.

  2. The JDBC Data Sources page displays and shows the data sources that are configured in the domain. Your display will look different than mine.

  3. Click Create and Generic Data Source to create a new data source.

    If you already have a data source that you want to use as a starting point for creating a new data source, then you can select it and click Create Like to start the JDBC data source wizard with the original settings in place.

  4. Enter JDBC data source properties the way that you normally would, including its name, driver class name, and JNDI name.

  5. Click Next.

  6. Click Generate URL and Properties to enter database settings.

  7. Enter the settings that match your database, including host name, port number, database name, database user name and password, and click OK.

  8. Click Test Database Connection to see if your settings are correct.

  9. Verify that your test is successful.

  10. Click Next.

  11. If you are creating an XA data source like I am, then there are no global transaction settings to enter and you click Next. If you created a non-XA data source, then set the support level for global transactions and click Next.

  12. Target your data source. I chose to target my data source to cluster1.

  13. Clik Next.

  14. Review your data source settings prior to creating it to make sure everything is correct.

  15. Click Create to create the data source in your domain.

  16. The list of data sources in the domain is displayed again. If you successfully created your data source, then it is included in the list. You should see a confirmation message that informs you of the status of your creation task. Notice that if you select the row for your data source that the toolbar above the list becomes active with commands you can perform on your data source.

  17. Click your data source to go to its configuration page.

  18. Take note of the available tabs for managing your data source. Take a few minutes to experiment on your own with each tab.

  19. Click the Control tab to display your data source as it is deployed across the domain. If you deployed it to a cluster then you should see an instance of your data source on each server in the cluster. Select one of the rows in the list. The toolbar above the list activates for that data source instance. Experiment for a few minutes with some of the actions you can perform on your data source.

Now that you have learned to manage JDBC data sources, let's work with WebLogic users and groups.

Managing Users and Groups

FMWC enables you to manage the users and groups in the identity store configured for the domain. FMWC-enabled domains are based on Oracle Platform Security Services (OPSS) instead of the default security framework configured in the WebLogic Server domain. When a WebLogic domain is OPSS-enabled, OPSS is not used to configure the identity store for authentication. OPSS depends on the authentication providers configured in the WebLogic domain's security realm to determine the identity store to use for other OPSS security features, such as authorization. OPSS supports multiple authentication providers. For your domain, the WebLogic default authentication provider should be configured, which is associated with the WebLogic embedded LDAP server.

Follow these steps to learn how to manage users and groups.

  1. Click the WebLogic Domain drop down list control and select Security > Users and Groups.

  2. The Users and Groups configuration page is displayed, with the Users tab preselected. A list of users configured for the domain is displayed.

  3. Click Create to create a new user.

  4. Enter the user name and password for the user. If multiple authentication providers are configured, then you can select the authentication provider (identity store) in which to store the user. Choose the DefaultAuthentictor provider and click Create.

  5. Click the Groups tab to create a new group.

  6. The list of groups that are configured in the domain are displayed.

  7. Click Create to create a new group.

  8. Enter appadmin as the new group name and click OK.

  9. Click your new group to modify it.

  10. Click the Membership tab to give the appadmin group a parent group.

  11. Select Administrators in the Available section and click the icon to move the group into the Chosen section. This effectively makes the appadmin group a member of the Administrators group. After assigning the jsmith user to the appadmin group, jsmith will effectively be a WebLogic administrative user.

  12. Click Save.

  13. Click Users and Groups in the breadcrumb trail to return to the main page.

  14. Click the Users tab to modify your new user.

  15. Click your new user to change its group membership.

  16. Click the Groups tab.

  17. Select appadmin in the Available section and click the icon to move the group into the Chosen section. This effectively makes jsmith a member of the appadmin group, which in turn also makes jsmith a member of the Administrators group.

  18. Click Save.

  19. Test your configuration. The jsmith user should now be a WebLogic administrative user, with privileges to configure the domain. Open a new web browser tab and open the WebLogic administration console.

  20. Login with the user name and password for your new user.

  21. If you configured everything successfully, then you will log into the WebLogic administration console as the jsmith user. The upper right-hand corner of the page should welcome the jsmith user.

  22. FMWC is the primary tool for managing OPSS-based security. In addition to managing users and groups, FMWC enables you to manage the entire security infrastructure of an OPSS-enabled domain. Experiment for a few minutes on your own with FMWC's security management features.

Congratulations! Now you know how to manage WebLogic Server domains with FMWC.

Summary

In this tutorial, you learned to use FMWC to manage WebLogic Server 12.1.3 domains.

Resources

Credits

  • Lead Curriculum Developer: Mark Lindros

To navigate this Oracle by Example tutorial, note the following:

Topic List:
Click a topic to navigate to that section.
Expand All Topics:
Click the button to show or hide the details for the sections. By default, all topics are collapsed.
Hide All Images:
Click the button to show or hide the screenshots. By default, all images are displayed.
Print:
Click the button to print the content. The content that is currently displayed or hidden is printed.

To navigate to a particular section in this tutorial, select the topic from the list.