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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Click the WebLogic Domain drop down list control and select Deployments.
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.
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.
Do not execute this step. Note that you can stop the application gracefully or forcefully, or place it into administration mode for administration requests.
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.
Click the WebLogic Domain drop down list control and select JDBC Data Sources.
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.
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.
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.
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.
Click the WebLogic Domain drop down list control and select Security > Users and Groups.
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.
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.
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.
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.
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.
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.
symbol to view configuration settings for the database. 
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. 
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. 
Overview