PK
)Eoa, mimetypeapplication/epub+zipPK )E iTunesMetadata.plist\
When you install Oracle Fusion Middleware, you install the binary files, such as executable files, jar files, and libraries. Then, you use configuration tools to configure the software. This chapter provides information you need to get started managing Oracle Fusion Middleware, including information about the tools you use.
This chapter includes the following sections:
Getting Started Using Oracle Enterprise Manager Fusion Middleware Control
Getting Started Using Oracle WebLogic Server Administration Console
Getting Started Using the Oracle WebLogic Scripting Tool (WLST)
Getting Started Using the Fusion Middleware Control MBean Browsers
Basic Tasks for Configuring and Managing Oracle Fusion Middleware
After you install and configure Oracle Fusion Middleware, you can use the graphical user interfaces or command-line tools to manage your environment.
Oracle offers the following primary tools for managing your Oracle Fusion Middleware installations:
Oracle Enterprise Manager Fusion Middleware Control. See Section 2.2.
Oracle WebLogic Server Administration Console. See Section 2.3
The Oracle Fusion Middleware command-line tools. See Section 2.4.
The Fusion Middleware Control MBean Browser. See Section 2.5.
Note that you should use these tools, rather than directly editing configuration files, to perform all administrative tasks unless a specific procedure requires you to edit a file. Editing a file may cause the settings to be inconsistent and generate problems.
Both Fusion Middleware Control and Oracle WebLogic Server Administration Console are graphical user interfaces that you can use to monitor and administer your Oracle Fusion Middleware environment. You can install Fusion Middleware Control and the Administration Console when you install most Oracle Fusion Middleware components.
Note the following:
If you install a standalone Oracle WebLogic Server, Fusion Middleware Control is not installed. Only the Administration Console is installed.
If you install Oracle JDeveloper, neither Fusion Middleware Control or the Administration Console are installed. They can be installed if you install Oracle Fusion Middleware Application Developer.
You can perform some tasks with either tool, but for other tasks, you can only use one of the tools. Table 2-1 lists some common tasks and the recommended tool.
Table 2-1 Comparing Fusion Middleware Control and WebLogic Server Administration Console
Task | Tool to Use |
---|---|
Manage Oracle WebLogic Server |
Use: |
Create additional Managed Servers |
Fusion Middleware Control |
Clone Managed Servers |
WebLogic Server Administration Console |
Cluster Managed Servers |
Fusion Middleware Control |
Start and stop Oracle WebLogic Server |
Fusion Middleware Control or WebLogic Server Administration Console |
Add users and groups |
WebLogic Server Administration Console if using the default embedded LDAP; if using another LDAP server, use the LDAP server's tool |
Manage Data Sources |
Use: |
Create data sources |
Fusion Middleware Control or WebLogic Server Administration Console |
Create connection pools |
Fusion Middleware Control or WebLogic Server Administration Console |
Manage JMS Resources |
Use: |
Create JMS queues |
WebLogic Server Administration Console |
Configure advanced queuing |
WebLogic Server Administration Console |
ADF Applications |
Use: |
Deploy ADF applications |
Fusion Middleware Control |
Java EE applications |
Use: |
Deploy Java EE applications |
WebLogic Server Administration Console or Fusion Middleware Control |
Security |
Use: |
Configure and manage auditing |
Fusion Middleware Control |
Configure SSL |
WebLogic Server Administration Console for Oracle WebLogic Server Fusion Middleware Control for Java components and system components. See Chapter 6. |
Change passwords |
WebLogic Server Administration Console |
Manage Components |
Use: |
View and manage log files |
Fusion Middleware Control for most log files WebLogic Server Administration Console for the following logs: DOMAIN_HOME/servers/server_name/logs/access.log DOMAIN_HOME/servers/server_name/data/ldap/log/EmbeddedLDAP.log DOMAIN_HOME/servers/server_name/data/ldap/log/EmbeddedLDAPAccess.log |
Change ports |
WebLogic Server Administration Console for Oracle WebLogic Server and Java components For some system components, Fusion Middleware Control. See the administration guide for the component. |
Manage Oracle HTTP Server |
Fusion Middleware Control |
Start and stop components |
Fusion Middleware Control |
Start and stop applications |
Fusion Middleware Control |
Fusion Middleware Control is a Web browser-based, graphical user interface that you can use to monitor and administer your domain. It can manage an Oracle WebLogic Server domain with its Administration Server, one or more Managed Servers, clusters, the Oracle Fusion Middleware components that are installed, configured, and running in the domain, and the applications you deploy.
Fusion Middleware Control organizes a wide variety of performance data and administrative functions into distinct, Web-based home pages for the domain, servers, components, and applications. The Fusion Middleware Control home pages make it easy to locate the most important monitoring data and the most commonly used administrative functions—all from your Web browser.
The following topics are discussed in this section:
To display Fusion Middleware Control, you enter the Fusion Middleware Control URL, which includes the name of the host and the administration port number assigned during the installation. The following shows the format of the URL:
http://hostname.domain:port/em
The port number is the port number of the Administration Server. By default, the port number is 7001. The port number is listed in the following file:
DOMAIN_HOME/config/config.xml
For some installation types, such as Web Tier, if you saved the installation information by clicking Save on the last installation screen, the URL for Fusion Middleware Control is included in the file that is written to disk (by default to your home directory). For other installation types, the information is displayed on the Create Domain screen of the Configuration Wizard when the configuration completes.
To display Fusion Middleware Control:
Enter the URL in your Web browser. For example:
http://host1.example.com:7001/em
The following shows the login page:
Enter the Oracle Fusion Middleware administrator user name and password and click Login.
The default user name for the administrator user is weblogic
. This is the account you can use to log in to Fusion Middleware Control for the first time. The password is the one you supplied during the installation of Oracle Fusion Middleware.
At any time while using the Fusion Middleware Control Console, you can click Help at the top of the page to get more information. From that menu, You can select the following: in the Help window to browse the list of help topics, or click Search to search for a particular word or phrase.
Help Contents, which lists the contents of Help.
Page Reference, which provides context-sensitive help for the current page.
How Do I?, which links to tutorial information in the documentation.
Documentation Library, which links to the library on the Oracle Technology Network.
User Forums, which links to Discussion Forums on the Oracle Technology Network.
Oracle Technology Network, which links to the Oracle Technology Network.
Fusion Middleware Control displays the target navigation pane on the left and the content pane on the right. For example, when you first log in to Fusion Middleware Control, the domain home page is displayed on the right.
From the target navigation pane, you can expand the tree and select an Oracle WebLogic Server domain, an Oracle WebLogic Server Managed Server, a component, an application, or a Metadata Repository.
When you select a target, such as a Managed Server or a component, the target's home page is displayed in the content pane and that target's menu is displayed at the top of the page, in the context pane. For example, if you select a Managed Server, the WebLogic Server menu is displayed. You can also view the menu for a target by right-clicking the target in the navigation pane.
The following figure shows the target navigation pane and the home page of an Managed Server. Because a Managed Server was selected, the dynamic target menu listed in the context pane is the WebLogic Server menu.
In the preceding figure, the following items are called out:
WebLogic Domain Menu provides a list of operations that you can perform on the domain. The WebLogic Domain menu is always available.
Change Center shows the changes made and allows you to lock and edit the configuration, release the configuration, activate changes, undo all changes, and change preferences. It also allows you to start and stop recording your session, and view the recording.
Target Navigation Pane lists all of the targets in the domain in a navigation tree.
Content Pane shows the current page for the target. When you first select a target, that target's home page is displayed.
Dynamic Target Menu provides a list of operations that you can perform on the currently selected target. The menu that is displayed depends on the target you select. The menu for a specific target contains the same operations as those in the Right-Click Target Menu.
Right-Click Target Menu provides a list of operations that you can perform on the currently selected target. The menu is displayed when you right-click the target name in the target navigation pane. In the figure, even though the WebLogic Server is selected and its home page is displayed, the right-click target menu displays the operations for a metadata repository because the user has right-clicked the metadata repository.
The menu for a specific target contains the same operations as those in the Dynamic Target Menu.
Target Name is the name of the currently selected target.
Target Information Icon provides information about the target. For example, for a domain, it displays the target name, the version, and the domain home.
Context Pane provides the name of the target, the name of the current user, the host name, and the time of the last page refresh, as well as the Refresh icon.
View lets you expand or collapse the navigation tree.
Help provides help for Fusion Middleware Control.
The username lets you change accessibility preferences.
Logout logs you out of Fusion Middleware Control.
Refresh indicates when the page is being refreshed. Click it to refresh a page with new data. (Refreshing the browser window refreshes the page but does not retrieve new data.)
Log out logs you out for Fusion Middleware Control.
In addition, from Fusion Middleware Control, from the home pages of targets such as the Administration Server or Managed Servers, you can access the WebLogic Server Administration Console.
Table 2-2 describes some common ways you can navigate within Fusion Middleware Control.
Table 2-2 Navigating Within Fusion Middleware Control
To: | Take This Action: |
---|---|
View all of the targets in the domain |
From the View menu, select Expand All. |
Operate on the domain |
Select the WebLogic Domain menu, which is always available at the top left of Fusion Middleware Control. |
Operate on a target |
Right-click the target in the target navigation pane. The target menu is displayed. Alternatively, you can select the target and use the dynamic target menu in the context pane. |
Return to the target's home page |
Click the target name at the top left-hand corner of the context pane. |
Refresh a page with new data |
Click the Refresh icon in the top right of the context pane. |
Return to a previous page |
Click the breadcrumbs, which appear below the context pane. The breadcrumbs appear when you drill down in a target. For example, choose Logs from the WebLogic Server menu, then View Log Messages. Select a log file and click View Log File. The breadcrumbs show: Log Messages > Log Files > View Log File: logfile_name |
View the host on which the target is running |
Select the target in the target navigation pane and view the host name in the target's context pane. You can also view the host name by clicking the Target Information icon. |
View a server log file |
Right-click the server name in the target navigation pane. Choose Logs, and then View Log Messages to see a summary of log messages and to search log files. |
To access Fusion Middleware Control and perform tasks, you must have the appropriate role. Fusion Middleware Control uses the Oracle WebLogic Server security realm and the roles defined in that realm. If a user is not granted one of these roles, the user cannot access Fusion Middleware Control.
Each role defines the type of access a user has. For example, a user with the role Admin has full privileges. A user with the role Operator has privileges to perform essential day-to-day operations. A user with the role Monitor has privileges only to view the configuration.
For more information, see "Users, Groups, and Security Roles" in the Securing Resources Using Roles and Policies for Oracle WebLogic Server.
When you log in to Fusion Middleware Control, the first page you see is the domain home page. You can also view this page at any time by selecting Home in the WebLogic Domain menu.
The following figure shows the domain home page:
The WebLogic Domain menu is displayed at the top of the page. From this menu, you can monitor and configure the domain.
The WebLogic Domain menu is always displayed, even if you have selected other entities.
You can view the routing topology by selecting Routing Topology from the WebLogic Domain menu. The Topology Viewer provides you with a high-level view of the topology, including Managed Servers, deployed applications, and the routing configuration. See Section 10.3 for information about using the Topology Viewer.
From the target navigation pane, you can drill down to view and manage the components in your domain.
For example, to view and manage Oracle HTTP Server, take the following steps:
In the target navigation pane, expand Web Tier.
Select the Oracle HTTP Server instance, for example, ohs1.
The home page for the Oracle HTTP Server ohs1 is displayed, as shown in the following figure:
From the HTTP Server menu, you can perform many administrative tasks, such as starting, stopping, and monitoring Oracle HTTP Server.
For more information about monitoring components, see Section 10.1.4.
Oracle WebLogic Server Administration Console is a Web browser-based, graphical user interface that you use to manage an Oracle WebLogic Server domain. It is accessible from any supported Web browser with network access to the Administration Server.
Use the Administration Console to:
Configure, start, and stop WebLogic Server instances
Configure WebLogic Server clusters
Configure WebLogic Server services, such as database connectivity (JDBC) and messaging (JMS)
Configure security parameters, including creating and managing users, groups, and roles
Configure and deploy Java EE applications
Monitor server and application performance
View server and domain log files
View application deployment descriptors
Edit selected run-time application deployment descriptor elements
To display the Administration Console:
Enter the following URL in a browser:
http://hostname:port_number/console
The port number is the port number of the Administration Server. By default, the port number is 7001.
The login page is displayed.
Log in using the user name and password supplied during installation or another administrative user that you created.
Oracle WebLogic Server Administration Console is displayed as shown in the following figure:
Alternatively, you can access the Administration Console from Fusion Middleware Control, from the home pages of targets such as the Administration Server or Managed Servers.
Before you make configuration changes, lock the domain configuration, so you can make changes to the configuration while preventing other accounts from making changes during your edit session. To lock the domain configuration:
Locate the Change Center in the upper left of the Administration Console screen.
Click Lock & Edit to lock the configuration edit hierarchy for the domain.
As you make configuration changes using the Administration Console, you click Save (or in some cases Finish) on the appropriate pages. This does not cause the changes to take effect immediately. The changes take effect when you click Activate Changes in the Change Center. At that point, the configuration changes are distributed to each of the servers in the domain. If the changes are acceptable to each of the servers, then they take effect. If any server cannot accept a change, then all of the changes are rolled back from all of the servers in the domain. The changes are left in a pending state; you can then either edit the pending changes to resolve the problem or revert to the previous configuration.
You can also lock the configuration by using the WLST command, startEdit:
startEdit()
For more information about the startEdit command and the stopEdit command, which releases locks, see "startEdit" and "stopEdit" in the WLST Command Reference for WebLogic Server.
The Oracle WebLogic Scripting Tool (WLST) is a command-line scripting environment that you can use to create, manage, and monitor Oracle WebLogic Server domains. It is based on the Java scripting interpreter, Jython. In addition to supporting standard Jython features such as local variables, conditional variables, and flow-control statements, WLST provides a set of scripting functions (commands) that are specific to WebLogic Server. You can extend the WebLogic scripting language to suit your needs by following the Jython language syntax.
The following topics describe using WLST to manage Oracle Fusion Middleware components:
You can use WLST commands with Java components. You can use them in the following ways:
Interactively, on the command line
In script mode, supplied in a file
Embedded in Java code
For example, to invoke WLST interactively, and connect to the WebLogic Server, use the following commands:
WL_HOME/server/bin/setWLSEnv.sh WL_HOME/common/bin/wlst.sh connect('username', 'password', 'localhost:7001')
To display information about WLST commands and variables, enter the help command. For example, to display a list of categories for online commands, enter the following:
wls:/base_domain/serverConfig> help('online') help('activate') Activate the changes. help('addListener') Add a JMX listener to the specified MBean. help('adminHome') Administration MBeanHome. help('cancelEdit') Cancel an edit session. help('cd') Navigate the hierarchy of beans. help('cmo') Current Management Object. . . .
To monitor the status, you use the WLST state
command, using the following format:
state(name, type)
For example to get the status of the Managed Server wls_server1, use the following command:
wls:/WLS_domain/serverConfig> state('wls_server1', 'Server') Current state of 'wls_server1' : RUNNING
For more information about WLST, see WLST Command Reference for WebLogic Server.
Many components and services, such as Oracle Application Development Framework, Diagnostic Framework, MDS, and SSL and logging, provide custom WLST commands.
To use those custom commands, you must invoke the WLST script from the Oracle Common home. Do not use the WLST script in the WebLogic Server home.
Oracle Application Development Framework
Oracle Metadata Services
Diagnostic Framework
Dynamic Monitoring Service (DMS)
Logging
Secure Sockets Layer (SSL)
Oracle JRF
Oracle Web Services
Oracle Web Services Manager
System components, such as Oracle HTTP Server
You can use WLST commands with system components. The following component is a system component:
Oracle HTTP Server
For system components, you can only the use the WLST commands listed in Table 2-3. See WLST Command Reference for WebLogic Server for information about whether a command can be invoked in online or offline mode.
Table 2-3 WLST Commands for System Components
WLST Command | Description | For more information: |
---|---|---|
create |
Creates an instance of the system component with defaults |
The create command in WLST Command Reference for WebLogic Server |
displayLogs |
Displays the messages in a log file |
The displayLogs command in WLST Command Reference for Infrastructure Components and Section 11.3.1.2 |
displayMetricTableNames |
Displays the names of the DMS metric tables |
The displayMetricTableNames command in WLST Command Reference for Infrastructure Components |
displayMetricTables |
Displays the contents of the DMS metric tables |
The displayMetricTables command in WLST Command Reference for Infrastructure Components |
dumpMetrics |
Displays the available DMS metrics. |
The dumpMetrics command in WLST Command Reference for Infrastructure Components |
listLogs |
Lists the log files. |
The listLogs command in WLST Command Reference for Infrastructure Components and Section 11.3.1.2 |
nmKill |
Shuts down and instance |
The nmkill command in WLST Command Reference for WebLogic Server and Section 4.3.2.2. |
nmServerStatus |
Returns the status on an instance |
The nmServerStatus command in WLST Command Reference for WebLogic Server |
nmStart |
Starts an instance |
The nmStart command in WLST Command Reference for WebLogic Server and Section 4.3.2.2. |
shutdown |
Stops a system component instance. |
The shutdown command in WLST Command Reference for WebLogic Server and Section 4.3.2.2. |
start |
Starts a system component instance. |
The start command in WLST Command Reference for WebLogic Server and Section 4.3.2.2. |
state |
Returns the state of a system component instance |
The state command in WLST Command Reference for WebLogic Server and Section 2.4 |
To use these commands, you must invoke the WLST script from the Oracle common home in which the component has been installed. Do not use the WLST script in the WebLogic Server home. The script is located at:
(UNIX) ORACLE_HOME/oracle_common/common/bin/wlst.sh (Windows) ORACLE_HOME\oracle_common\common\bin\wlst.cmd
To monitor the status of a system component, you use the WLST state
command, using the following format:
state(component_ame, SystemComponent)
In online mode, you can use the cmo variable to invoke MBean operations that provide even more functionality. For more information about the cmo variable, see "Changing the Current Management Object" in Understanding the WebLogic Scripting Tool.
A managed bean (MBean) is a Java object that represents a JMX manageable resource in a distributed environment, such as an application, a service, a component or a device.
MBeans are defined in the Java EE Management Specification (JSR-77), which is part of Java Management Extensions, or JMX, a set of specifications that allow standard interfaces to be created for managing applications in a Java EE environment. For information about JSR-77, see:
http://java.sun.com/j2ee/tools/management/
You can create MBeans for deployment with an application into Oracle WebLogic Server, enabling the application or its components to be managed and monitored through Fusion Middleware Control.
Fusion Middleware Control provides a set of MBean browsers that allow to you browse the MBeans for an Oracle WebLogic Server or for a selected application. You can also perform specific monitoring and configuration tasks from the MBean browser.
The MBeans are organized into three groups: Configuration MBeans, Runtime MBeans, and Application-Defined MBeans.
For more information about MBeans, see "Understanding WebLogic Server MBeans" in Developing Custom Management Utilities Using JMX for Oracle WebLogic Server.
The following topics describe how to view or configure MBeans:
You can view the System MBean Browser for many entities, including an Oracle WebLogic Server domain, an Administration Server, a Managed Server, or an application. You can search for an MBean, filter the list of MBeans, and refresh the list of MBeans in the MBean navigation tree.
To view the System MBean Browser specific to a particular Oracle WebLogic Server Managed Server and to configure and use the MBeans:
From the target navigation pane, expand the domain.
Select the Managed Server.
From the WebLogic Server menu, choose System MBean Browser.
The System MBean Browser page is displayed.
Expand a node in the MBean navigation tree and drill down to the MBean you want to access. Select an MBean instance.
If you do not know the location of an MBean, you can search for the MBean:
Click the Find icon at the top of the MBean navigation tree.
For Find, select MBean Name.
You can also select Attributes, Operations, or JMX syntax.
Enter the name of the MBean and click the arrow.
To view the MBean's attributes, select the Attributes tab. Some attributes allow you to change their values. To do so, enter the value in the Value column.
To view the available operations, select the Operations tab. To perform an operation, click the operation. The Operations page appears. Enter any applicable values and click Invoke.
For more information, see the Fusion Middleware Control online help.
You can view, configure, and use the MBeans for a specific application by taking the steps described in Section 2.5.1, and drilling down to the application. As an alternative, you can navigate to an application's MBeans using the following steps:
From the target navigation pane, expand Application Deployments.
Select the application.
From the Application Deployments menu, choose System MBean Browser.
The System MBean Browser page is displayed, along with the MBean information for the application.
To view the MBean's attributes, select the Attributes tab. Some attributes allow you to change their values. To do so, enter the value in the Value column.
To view the available operations, select the Operations tab. To perform an operation, click the operation. The Operations page appears. Enter any applicable values and click Invoke.
To manage the Oracle WebLogic Server and Java components, you can use WLST, Oracle WebLogic Server Administration Console, or Fusion Middleware Control.
To manage system components, you can use WLST, or Fusion Middleware Control.
See:
|
During the Oracle Fusion Middleware installation, you must specify a password for the administration account. Then, you can use this account to log in to Fusion Middleware Control and the Oracle WebLogic Server Administration Console for the first time. You can create additional administrative accounts using the WLST command line or the Oracle WebLogic Server Administration Console.
You can change the password of the administrative user using the command line or the Oracle WebLogic Server Administration Console, as described in the following topics:
Changing the Administrative User Password Using the Command Line
Changing the Administrative User Password Using the Administration Console
For more information about users, roles, and changing passwords, see "Understanding Users and Roles" in the Securing Applications with Oracle Platform Security Services
To change the administrative user password or other user passwords using the command line, you invoke the UserPasswordEditorMBean.changeUserPassword method, which is extended by the security realm's AuthenticationProvider MBean.
For more information, see the changeUserPassword method in the MBean Reference for Oracle WebLogic Server.
To change the password of an administrative user using the Oracle WebLogic Server Administration Console:
Navigate to the Oracle WebLogic Server Administration Console. (For example, from the home page of the domain in Fusion Middleware Control, select To configure and managed this WebLogic Domain, use the Oracle WebLogic Server Administration Console.)
From the Domain Structure pane, select Security Realms.
The Summary of Security Realms page is displayed.
Select a realm, such as myrealm.
The Settings for the realm page is displayed.
Select the Users and Groups tab, then the Users tab. Select the user.
The Settings for user page is displayed.
Select the Passwords tab.
Enter the new password, then enter it again to confirm it.
Click Save.
Node Manager allows you to perform common operations, such as starting and stopping, for a Managed Server using the Administration Console or Fusion Middleware Control.
This section describes the following topics:
If a Managed Server contains other Oracle Fusion Middleware products, such as Oracle JRF, the Managed Servers environment must be configured to set the correct classpath and parameters. By default, Node Manager is configured when you install Oracle Fusion Middleware.
However, if you do not select automatic configuration, you must provide this environment information through the start scripts, such as startWebLogic and setDomainEnv, which are located in the following directory:
DOMAIN_HOME/bin
If the Managed Servers are started by Node Manager (as is the case when the servers are started by the Oracle WebLogic Server Administration Console or Fusion Middleware Control), Node Manager must be instructed to use these start scripts so that the server environments are correctly configured. Specifically, Node Manager must be started with the property StartScriptEnabled=true
.
There are several ways to ensure that Node Manager starts with this property enabled. As a convenience, Oracle Fusion Middleware provides the following script, which adds the property StartScriptEnabled=true
to the nodemanager.properties file:
(UNIX) ORACLE_COMMON_HOME/common/bin/setNMProps.sh. (Windows) ORACLE_COMMON_HOME\common\bin\setNMProps.cmd
For example, on Linux, execute the setNMProps script and start Node Manager:
ORACLE_COMMON_HOME/common/bin/setNMProps.sh DOMAIN_HOME/bin/startNodeManager.sh
When you start Node Manager, it reads the nodemanager.properties file with the StartScriptEnabled=true
property, and uses the start scripts when it subsequently starts Managed Servers. Note that you need to run the setNMProps script only once.
Also note that when the StartScriptEnable property is set to true, the Node Manager reads the startWebLogic script, which in turns reads the setDomainEnv script. As a result, you must make any tuning changes by editing the setDomainEnv script. Any changes that are performed using the command line or Administration Console will not be implemented when Node Manager starts the servers. For example, if you use the Administration Console to change the server start arguments, those changes are written to config.xml, but the Node Manager ignores these settings and uses those in setDomainEnv.
See "Using Node Manager" in the Administering Node Manager for Oracle WebLogic Server for other methods of configuring and starting Node Manager.
If you created a domain that included Oracle JRF and you configured Node Manager as "per domain", you can configure Node Manager to use the Oracle Platform Security Services Keystore Service. Take the following steps:
Configure the Keystore Service, as described in "Keystore Management with the Keystore Service" in Securing Applications with Oracle Platform Security Services.
Configure Node Manager by editing the following file:
nodemanager.properties
In the file, specify the following properties:
KeyStores=CustomIdentityAndDemoTrust CustomIdentityKeyStoreType=KSS CustomIdentityKeyStoreFileName=kss://system/keystore_name CustomIdentityKeyStorePassPhrase= keystore_passphrase CustomIdentityAlias= key store alias CustomIdentityPrivateKeyPassPhrase= keystore_private_key_passphrase
Oracle Platform Security Services Keystore Service is not supported for a "per host" Node Manager. In certain circumstances, however, a "per host" Node Manager will attempt to load the keystore service. To prevent that, you must specify UseKSSForDemo=false
in the following file:
ORACLE_HOME/oracle_common/common/nodemanager/nodemanager.properties
The following provides a summary of the steps you need to take to configure and manage a basic Oracle Fusion Middleware environment after you have installed the software:
Configure Oracle WebLogic Server and components, such as Oracle HTTP Server. See Planning an Installation of Oracle Fusion Middleware.
Configure Node Manager. See Section 2.8.
Configure SSL. See Chapter 6.
Create and manage metadata repositories, including the MDS Repository. See Section 13.2.
Deploy an application. See Chapter 9.
Configure load balancing. You can configure load balancing between different components or applications. See the High Availability Guide.
Back up your environment. See Chapter 15.
Monitor your environment and manage log files. See Chapter 10 and Chapter 11.
Expand your environment. See Chapter 18.
This guidje also describes other tasks that you may need to perform, depending on your Oracle Fusion Middleware environment.
Note: The procedures in this book for the most part assume that you are using the standard installation topology, which consists of a domain that contains an Administration Server and a cluster containing two Managed Servers.For more information about the standard topology, see "Understanding the Oracle Fusion Middleware Infrastructure Standard Installation Topology" in Installing and Configuring the Oracle Fusion Middleware Infrastructure. |
This appendix includes information about using Oracle Fusion Middleware accessibility options.
It includes the following sections:
If you are installing on a Windows computer, you can install and configure Java Access Bridge for Section 508 Accessibility:
Download Java Access Bridge from the following URL:
http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html
Install Java Access Bridge.
Copy the access-bridge.jar
and jaccess-1_4.jar
files from your installation location to the jre/lib/ext
directory.
Copy the WindowsAccessBridge.dll
, JavaAccessBridge.dll
, and JAWTAccessBridge.dll
files from your installation location to the jre/bin
directory.
Copy the accessibility.properties
file to the jre/lib
directory.
The following sections provide information on the benefits of running Fusion Middleware Control in accessibility mode, as well as instructions for enabling accessibility mode:
In Fusion Middleware Control, you can enable screen reader support. Screen reader support improves behavior with a screen reader. This is accomplished by adding accessibility-specific constructs to the HTML, and by altering some navigation elements on the pages.
To enable screen reader mode in Fusion Middleware Control:
Choose the user name at the right top of the page, then Accessibility.
The Accessibility Preference page is displayed.
Select any of the following options:
I use a screen reader: Accessibility-specific constructs are added to improve behavior with a screen reader.
I use high contrast settings: The fonts use a high contrast.
I use large fonts: The fonts are larger than normal.
Show me the Accessibility Preference dialog when I log in: When you log in, the Accessibility Preference page is displayed.
Click Apply.
A confirmation dialog box is displayed.
Click OK.
Click Enterprise Manager at the top of the page to return to the page you last visited.
When you select screen reader support, Fusion Middleware Control renders the Web pages so that they can be read by a screen reader. For example, each node in the navigation tree includes a Select button.
The following figure shows the navigation pane and the Administration Server Performance Summary after enabling screen reader support:
Throughout Fusion Middleware Control, charts are used to display performance data. For most users, these charts provide a valuable graphical view of the data that can reveal trends and help identify minimum and maximum values for performance metrics.
However, charts do not convey information in a manner that can be read by a screen reader. To remedy this problem, you can configure Fusion Middleware Control to provide a complete textual representation of each performance chart. When you enable screen reader mode, Fusion Middleware Control displays the information in tables, instead of charts.
To view a representation of the data in a table, instead of a chart, without enabling screen reader mode, click Table View below a chart.
This section describes the keyboard navigation in Fusion Middleware Control.
Much of the keyboard navigation is the same whether or not you use screen reader mode.
Generally, you use the following keys to navigate:
Tab key: Move to the next control, such as a dynamic target menu, navigation tree, content pane, or tab in a page. Tab traverses the page left to right, top to bottom. Use Shift +Tab to move to the previous control.
Up and Down Arrow keys: Move to the previous or next item in the navigation tree, menu, or table. Down Arrow also opens a menu.
Left and Right Arrow keys: Collapse and expand an item in the navigation tree or a submenu.
Esc: Close a menu.
Spacebar: Activate a control. For example, in a check box, spacebar toggles the state, checking or unchecking the box. On a link, spacebar navigates to the target of the link.
Enter: Activate a button.
Table E-1 shows some common tasks and the keyboard navigation used.
Table E-1 Keyboard Navigation for Common Tasks
Task | Navigation |
---|---|
Move to next control, such as navigation tree or menu |
Tab |
Move to previous control, such as navigation tree or menu |
Shift+Tab |
Move to navigation pane |
Tab until navigation tree has input focus |
Move down the navigation tree |
Down Arrow |
Move up the navigation tree |
Up Arrow |
Expand a folder |
Right Arrow |
Collapse a folder |
Left Arrow |
Open a menu |
Down Arrow |
Move to the next item in a menu |
Down Arrow |
Move to the previous item in a menu |
Up Arrow |
Select a menu item |
Enter |
Open a submenu |
Right Arrow |
Close a submenu |
Left Arrow |
Move out of a menu |
Esc |
Activate a button |
Enter |
Open a tab in a content pane |
Tab to the content pane, Tab to the tab to get input focus, then Enter to select the tab |
Select an item, such as Message type in Log Messages screen |
Spacebar |
Select a row in a table |
Tab to the header of the table, then Down Arrow to move to a row |
Select a cell in a table |
Tab to the header of the table, then Tab until you reach the cell you want to select, then Enter |
Table E-2 shows the keyboard navigation for the Topology Viewer. The navigation from one node to another is based on the geometry of the topology.
Table E-2 Keyboard Navigation for Topology Viewer
Task | Navigation |
---|---|
Navigate into the topology |
Tab, until you have reached a node. |
Navigate nodes based on geometry |
Arrow keys |
In a top-to-bottom orientation, navigate to a destination link |
Ctrl+Shift+Down Arrow |
In a top-to-bottom orientation, navigate to a source link |
Ctrl+Shift+Up Arrow |
In a left-to-right orientation, navigate to a destination link |
Ctrl+Shift+Right Arrow |
In a left-to-right orientation, navigate to a source link |
Ctrl+Shift+Left Arrow |
In a top-down orientation, when on a link, navigate to other links. The focus moves to another link based on the geometry. |
Right Arrow or Left Arrow |
In a left-to-right orientation, when on a link, navigate to other links. The focus moves to another link based on the geometry. |
Up Arrow or Down Arrow |
Move into or out of a group node |
Shift+Arrow |
Simulate a mouse click on the node. This can bring up a popup or it can navigate to another page. |
Enter |
Simulate a mouse over. Typically, this brings ups a popup. |
Shift+Enter |
Simulate a right-mouse click. Typically, this brings up a context menu. |
m |
Expand or contract a node subtree |
e |
Expand or contract a group. Note that if you use Shift+Arrow to move into a group, the group automatically expands. |
g |
Pan up or down, left or right |
Ctrl+Arrow keys |
Zoom in |
Ctrl+Alt+Plus Key(+) |
Zoom out |
Ctrl+Alt+Minus Key(-) |
Move out of a menu. |
Esc |
This preface introduces the new and changed administrative features of Oracle Fusion Middleware that are described in this guide, and provides pointers to additional information.
This edition of the guide contains bug fixes and other corrections.
The following topics introduce the new and changed features of Oracle Fusion Middleware and other significant changes that are described or referred to in this guide, and provides pointers to additional information. This book is the new edition of the formerly titled Oracle Fusion Middleware Administrator's Guide.
Redefining of the Oracle home and elimination of the Middleware home. See "New And Deprecated Terminology for 12c" in Understanding Oracle Fusion Middleware.
OPMN is no longer used in Oracle Fusion Middleware. Instead, system components are managed by the WebLogic Management Framework, which includes WLST, Node Manager and pack and unpack. See "What Is the WebLogic Management Framework" in Understanding Oracle Fusion Middleware.
Support for a "per domain" Node Manager. See "What Is Node Manager?" in Understanding Oracle Fusion Middleware.
Oracle Web Cache is no longer part of Oracle Fusion Middleware.
Changes in moving from a source to a target environment:
Because of the redefining of Oracle home and elimination of Middleware home, some of the parameters to the scripts have changed. See Section A.1.1.
Support for moving a standalone domain. See Section 19.3.5.
Support for moving the Oracle home and binary files using storage-level cloning tools. See Section 19.3.3.
A move plan for Oracle Coherence. See Table A-15.
A move plan for Oracle Web Services Manager. See Table A-18.
Support for moving Oracle Data Integrator.
The OPSS Keystore Service is introduced. See Section 7.1.1.3.
SSL procedures for Oracle WebLogic Server have been updated. See Section 6.5.1.
Fusion Middleware Control supports cross-component wiring. See Section 3.3.
Oracle Fusion Middleware has introduced service tables, which provide a way for service providers to publish endpoint information about their services, and clients of these services to query and bind to these services. See Section 3.1.
Updated procedures for backup and recovery, including procedures for recovering a standalone domain. See Chapter 17.
Enhanced support for querying diagnostic incidents. See Section 12.4.2.3.
Support for creating aggregated incidents. See Section 12.4.6.2.
Support for extended log format for access logs. See Section 11.1.1.
This appendix provides the URLs needed to access Oracle Fusion Middleware components.
Table C-1 shows the URLs to access components after installation.
The URLs in the table are shown with the default ports. The components in your environment might use different ports. To determine the port numbers, from the WebLogic Domain menu in Fusion Middleware Control, select Port Usage.
This chapter provides an introduction to backing up and recovering Oracle Fusion Middleware, including backup and recovery recommendations for Oracle Fusion Middleware components.
It contains the following sections:
The installations of an Oracle Fusion Middleware environment are interdependent in that they contain configuration information, applications, and data that are kept in synchronization. For example, when you perform a configuration change, information in configuration files is updated. When you deploy an application, you might deploy it to all Managed Servers in a domain or cluster.
It is, therefore, important to consider your entire Oracle Fusion Middleware environment when performing backup and recovery. You should back up your entire Oracle Fusion Middleware environment at once, then periodically. If a loss occurs, you can restore your environment to a consistent state.
The following topics describe concepts that are important to understanding backup and recovery:
See Also: Understanding Oracle Fusion Middleware for conceptual information about Oracle WebLogic Server domains, the Administration Server, Managed Servers and clusters, and Node Manager. |
The failure of an Administration Server does not affect the operation of Managed Servers in the domain but it does prevent you from changing the domain's configuration. If an Administration Server fails because of a hardware or software failure on its host computer, other server instances on the same computer may be similarly affected.
If an Administration Server for a domain becomes unavailable while the server instances it manages—clustered or otherwise—are running, those Managed Servers continue to run. Periodically, these Managed Servers attempt to reconnect to the Administration Server. For clustered Managed Server instances, the load balancing and failover capabilities supported by the domain configuration continue to remain available.
When you first start a Managed Server, it must be able to connect to the Administration Server to retrieve a copy of the configuration. Subsequently, you can start a Managed Server even if the Administration Server is not running. In this case, the Managed Server uses a local copy of the domain's configuration files for its starting configuration and then periodically attempts to connect with the Administration Server. When it does connect, it synchronizes its configuration state with that of the Administration Server.
A Managed Server maintains a local copy of the domain configuration. When a Managed Server starts, it contacts its Administration Server to retrieve any changes to the domain configuration that were made since the Managed Server was last shut down. If a Managed Server cannot connect to the Administration Server during startup, it can use its locally cached configuration information—this is the configuration that was current at the time of the Managed Server's most recent shutdown. A Managed Server that starts without contacting its Administration Server to check for configuration updates is running in Managed Server Independence (MSI) mode. By default, MSI mode is enabled. However a Managed Server cannot be started even in MSI mode for the first time if the Administration Server is down due to non-availability of the cached configuration.
Configuration changes are updated in a Managed Server during the following events:
On each Managed Server restart, the latest configuration is retrieved from the Administration Server. This happens even when Node Manager is down on the node where the Managed Server is running. If the Administration Server is unavailable during the Managed Server restart and if the MSI (Managed Server Independence) mode is enabled in the Managed Server, it starts by reading its local copy of the configuration and synchronizes with the Administration Server when it is available. By default MSI mode is enabled.
Upon activating every administrative change such as configuration changes, deployment or redeployment of applications, and topology changes, the Administration Server pushes the latest configuration to the Managed Server. If the Managed Server is not running, the Administration Server pushes the latest version of the configuration to the Managed Server when it does start.
The following shows a simplified view of the Oracle Fusion Middleware directory structure when you have installed and configured the Oracle Fusion Middleware Infrastructure:
To back up your Oracle Fusion Middleware environment, you can use:
File copy utilities such as copy, xcopy, tar, or jar. Make sure that the utilities:
Preserve symbolic links
Support long file names
Preserve the permissions and ownership of the files
For example:
On Windows, for online backups, use copy; for offline backups, use copy, xcopy, or jar. Do not use Winzip because it does not work with long filenames or extensions.
Note that for some versions of Windows, any file name with more than 256 characters fails. You can use the xcopy command with the following switches to work around this issue:
xcopy /s/e "C:\Temp\*.*" "C:\copy"
See the xcopy help for more information about syntax and restrictions.
On Linux and UNIX, for online and offline backups, use tar.
Oracle Recovery Manager (RMAN) to back up database-based metadata repositories and any databases used by Oracle Fusion Middleware. With RMAN, you can perform full backups or incremental backups. See Oracle Database Backup and Recovery User's Guide for information about using RMAN to back up a database.
If you want to retain your backups for a longer duration, you may want to back up to tape, for example using Oracle Secure Backup.
You can also configure Oracle WebLogic Server to make backup copies of the configuration files. This facilitates recovery in cases where configuration changes need to be reversed or in the unlikely case that configuration files become corrupted. When the Administration Server starts, it saves a .jar file named config-booted.jar that contains the configuration files. When you make changes to the configuration files, the old files are saved in the configArchive directory under the domain directory, in a .jar file with a sequentially numbered name such as config-1.jar. However, the configuration archive is always local to the Administration Server host. It is a best practice to back up the archives to an external location.
You can back up your Oracle Fusion Middleware environment offline or online:
An offline backup means that you must shut down the environment before backing up the files. When you perform an offline backup, the Administration Server, all Managed Servers in the domain should be shut down.
Back up the environment offline immediately after installation and after applying any patches or upgrades.
An online backup means that you do not shut down the environment before backing up the files. To avoid an inconsistent backup, do not make any configuration changes until the backup is completed. To ensure that no changes are made in the WebLogic Server domain, lock the WebLogic Server configuration, as described in Section 2.3.2.
You can perform backups on your full Oracle Fusion Middleware environment, or on the run-time artifacts, which are those files that change frequently.
To perform a full backup, you should back up the static files and directories, as well as run-time artifacts, which are described in Section 15.3.2.
Backup artifacts include static files and directories and run-time artifacts.
Static files and directories are those that do not change frequently. These include:
The Oracle home (ORACLE_HOME). An Oracle home consists of product homes, such as the WebLogic Server home and an Oracle Common home. It can also contain the user_projects directories, which contains Oracle WebLogic Server domains, which are not static files.
OraInventory
On Linux and UNIX, the oraInst.loc file, which is located in the following directory:
(Linux and IBM AIX) /etc (Other UNIX systems) /var/opt/oracle
On Linux and UNIX, the oratab file, which is located in the following directory:
/etc
The beahomelist file, which is located at:
(UNIX) user_home/bea/beahomelist
(Windows) C:\bea\beahomelist
On Windows, the following registry key:
HKEY_LOCAL_MACHINE\Software\oracle
In addition, for system components, such as Oracle HTTP Server, you must back up the following Windows Registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
Run-time artifacts are those files that change frequently. Back up these files when you perform a full backup and on a regular basis. Run-time artifacts include:
Domain directories of the Administration Server and the Managed Servers (by default, a domain directory resides in Oracle home, but it can be configured by the user to point to a different location.)
In most cases, you do not need to back up Managed Server directories separately because the Administration Server contains information about all of the Managed Servers in its domain.
Application artifacts, such as .ear or .war files that reside outside of the domain.
You do not need to back up application artifacts in a Managed Server directory structure because they can be retrieved from the Administration Server during Managed Server startup.
Database artifacts, such as the MDS Repository.
Any database-based metadata repositories used by Oracle Fusion Middleware. You use Oracle Recovery Manager (RMAN) to back up an Oracle database.
Persistent stores, such as JMS Providers and transaction logs, which reside by default in the user_projects directory, but can be configured in a different location.
This section outlines the recommended strategy for performing backups. Using this strategy ensures that you can perform the recovery procedures in this book.
Perform a full offline backup: This involves backing up the entities described in Section 15.3.2. Perform a full offline backup at the following times:
Immediately after you install Oracle Fusion Middleware
Immediately before upgrading your Oracle Fusion Middleware environment
Immediately after an operating system software upgrade
Immediately after upgrading or patching Oracle Fusion Middleware
Perform an online backup of run-time artifacts: This involves backing up the run-time artifacts described in Section 15.3.2. Backing up the run-time artifacts enables you to restore your environment to a consistent state as of the time of your most recent configuration and metadata backup. To avoid an inconsistent backup, do not make any configuration changes until backup completes. Perform an online backup of run-time artifacts at the following times:
On a regular basis. Oracle recommends that you back up run-time artifacts nightly.
Prior to making configuration changes to a component.
After making configuration changes to a component.
Prior to deploying a custom Java EE application to a Managed Server or cluster.
After a major change to the deployment architecture, such as creating servers or clusters.
Perform a full or incremental backup of your databases: Use RMAN to backup your databases. See the Oracle Database Backup and Recovery User's Guide for information about using RMAN and for suggested methods of backing up the databases.
Recovery strategies enable you to recover from critical failures that involve actual data loss. Depending on the type of loss, they can involve recovering any combination of the following types of files:
Oracle software files
Configuration files
Oracle system files
Windows Registry keys
Application artifacts
You can recover your Oracle Fusion Middleware environment while Oracle Fusion Middleware is offline.
To recover your Oracle Fusion Middleware environment, you can use:
File copy utilities such as copy, xcopy, or tar
When you restore the files, use your preferred tool to extract the compressed files:
On Windows, for online recovery, use copy; for offline recovery, use copy, xcopy, or jar.
Note that for some versions of Windows, any file name with more than 256 characters fails. You can use the xcopy command with the following switches to work around this issue:
xcopy /s/e "C:\Temp\*.*" "C:\copy"
See the xcopy help for more information about syntax and restrictions.
Do not use Winzip because it does not work with long filenames or extensions.
On Linux and UNIX, use tar.
Ensure that the tool you are using preserves the permissions and timestamps of the files.
Oracle Recovery Manager (RMAN) to recover database-based metadata repositories
You can recover your Oracle Fusion Middleware environment in part or in full. You can recover the following:
The Oracle home
WebLogic Server domains
The WebLogic Server Administration Server
WebLogic Server Managed Servers
A component, such as Oracle HTTP Server
WebLogic Server cluster
Deployed applications
Note the following key points about recovery:
Your Oracle Fusion Middleware environment must be offline while you are performing recovery.
Rename important existing files and directories before you begin restoring the files from backup so that you do not unintentionally override necessary files.
Although, in some cases, it may appear that only one or two files are lost or corrupted, you should restore the directory structure for the entire element, such as a domain, rather than just restoring one or two files. In this way, you are more likely to guarantee a successful recovery.
Recover the database to the most current state, using point-in-time recovery (if the database is configured in Archive Log Mode). This is typically a time right before the database failure occurred.
The following sections describe backup and recovery recommendations for specific Oracle Fusion Middleware components:
Backup and Recovery Recommendations for Oracle WebLogic Server
Backup and Recovery Recommendations for Oracle JRF Installations
Backup and Recovery Recommendations for Web Tier Installations
Backup and Recovery Recommendations for Oracle Data Integrator
For the steps you take to back up your environment, see Section 16.3. For the steps you take to recover your environment, see Chapter 17.
The following sections describe backup and recovery recommendations for Oracle WebLogic Server:
Backup and Recovery Recommendations for Oracle WebLogic Server
Backup and Recovery Recommendations for Oracle WebLogic Server JMS
This section describes the Oracle WebLogic Server data that must be backed up and restored.
Database Repository Dependencies
Oracle WebLogic Server does not, by default, depend on any database repository. However, applications deployed on Oracle WebLogic Server may use databases as data sources. To back up a database, see the Oracle Database Backup and Recovery User's Guide.
Backup Recommendations
Back up the Oracle home and the domain.
Recovery Recommendations
Depending on what has failed, you may need to recover the following:
The domain: See Section 17.2.2.
The Administration Server configuration: See Section 17.2.4.
A Managed Server: See Section 17.2.5.
A cluster: See Section 17.2.7.
Applications: See Section 17.2.8.
If you use Whole Server Migration, the leasing information is stored in a table in a database. If you recover Oracle WebLogic Server, you should discard the information in the leasing table. (For more information about Whole Server Migration, see "Whole Server Migration" in Administering Clusters for Oracle WebLogic Server.)
After a loss of host, you may need to recover the following:
The WebLogic domain. See Section 17.3.1.
The Administration Server host: See Section 17.3.3.
The Managed Server host: See Section 17.3.4.
This section describes the Oracle WebLogic Server JMS data that must be backed up and restored.
Database Repository Dependencies
Only if JMS is database-based
Backup Recommendations
Back up the domain.
If you are using a database-based JMS, back up the database using RMAN.
If you are using file-based JMS, use storage snapshot techniques for taking consistent online backups. Alternatively, you can use a file system copy to perform an offline backup.
Recovery Recommendations
Recover the domain.
If the JMS persistent store is file-based, recover it from backup. If the JMS persistent store is database-based, recover the database to the most recent point in time, if needed. Note the following:
Always try to keep JMS data as current as possible. This can be achieved by using the point-in-time recovery capabilities of Oracle Database, recovering to the most recent time (in the case of database-based persistence) or using a highly available RAID-backed storage device (for example, SAN/NAS).
If you are using a file-based JMS, you can use storage snapshots to recover.
If, for whatever reason, you need to restore JMS data to a previous point in time, there are potential implications. Restoring the system state to a previous point in time not only can cause duplicate messages, but can also cause lost messages. The lost messages are messages that were enqueued before or after the system restore point time, but never processed.
Use the following procedure before recovery to drain messages in the JMS queue after persistent-store recovery to avoid processing duplicate messages:
Note: Do not drain and discard messages without first being certain that the messages contain no data that must be preserved. The recovered messages may include unprocessed messages with important application data, in addition to duplicate messages that have already been processed. |
Log into the Oracle WebLogic Server Administration Console.
Before recovery, configure JMS server to pause Production, Insertion, and consumption operations at boot time to ensure that no new messages are produced or inserted into the destination or consumed from the destination before you drain stale messages. To do this:
Expand Services, then Messaging, and then click JMS Servers.
On the Summary of JMS Servers page, click the JMS server you want to configure for message pausing.
On the Configuration: General page, click Advanced to define the message pausing options. Select Insertion Paused At Startup, Production Paused At Startup, and Consumption Paused At Startup.
Click Save.
Use the following procedure after recovery:
After recovering the persistent store, start the Managed Servers.
Drain the stale messages from JMS destinations, by taking the following steps:
Expand Services, then Messaging, and then JMS Modules.
Select a JMS module, then select a target.
Select Monitoring, then Show Messages.
Click Delete All.
Resume operations, by taking the following steps:
Expand Services, then Messaging, and then JMS Servers.
On the Summary of JMS Servers page, click the JMS server you want to configure for message pausing.
On the Configuration: General page, click Advanced. Deselect Insertion Paused At Startup, Production Paused At Startup, and Consumption Paused At Startup.
Click Save.
If the store is not dedicated to JMS use, use the Oracle WebLogic Server JMS message management administrative tool. This tool can perform import, export, move, and delete operations from the Administration Console, MBeans, and WLST.
For applications that use publish and subscribe in addition to queuing, you should manipulate topic subscriptions in addition to queues.
For the steps to recover the domain, see Section 17.2.2 and Section 17.3.1.
The following topics describe backup and recovery recommendations for components that are installed with more than one type of installation:
Backup and Recovery Recommendations for Oracle Web Services Manager
Backup and Recovery Recommendations for Oracle Platform Security Services
This section describes the Oracle Web Services Manager data that must be backed up and restored.
Database Repository Dependencies
If a database-based MDS Repository is used, Oracle Web Services Manager uses a partition in the MDS schema.
Backup Recommendations
Back up the Oracle Web Services Manager domain.
If Oracle Web Services Manager uses a file-based MDS Repository, back it up using a file copy mechanism. If it uses a database-based MDS Repository, back up the database using RMAN.
Recovery Recommendations
Restore the Oracle Web Services Manager Managed Server.
If Oracle Web Services Manager uses a file-based MDS Repository, restore it from the backup. If it uses a database-based MDS Repository, recover the database to the most recent point in time, if needed.
For the steps to recover components, see Section 17.2.6. For the steps specific to recovering from loss of host, see Section 17.3.5.
This section describes the Oracle Platform Security Services data that must be backed up and restored.
Database Repository Dependencies
If a database-based Oracle Platform Security Repository is used, Oracle Platform Security uses a partition in the OPSS schema.
If an Oracle Internet Directory based Oracle Platform Security repository is used, Oracle Platform Security uses Oracle Internet Directory.
Backup Recommendations
Back up the Administration Server domain, including the following files:
DOMAIN_HOME/config/fmwconfig/jps-config.xml DOMAIN_HOME/config/fmwconfig/jps-config-jse.xml DOMAIN_HOME/config/fmwconfig/cwallet.sso DOMAIN_HOME/config/fmwconfig/bootstrap/cwallet.sso DOMAIN_HOME/config/fmwconfig/keystores.xml DOMAIN_HOME/config/config.xml DOMAIN_HOME/config/fmwconfig/ids_config.xml DOMAIN_HOME/config/fmwconfig/system-jazn-data.xml (if present) DOMAIN_HOME/config/fmwconfig/jps_mbeans.xml
Back up Oracle Internet Directory if Oracle Platform Security uses an Oracle Internet Directory based repository.
Backup the database containing the OPSS schema if Oracle Platform Security uses a database-based repository.
Recovery Recommendations
Restore the jps-config.xml file.
If Oracle Platform Security uses a database-based repository, restore the database to the most recent point in time.
For the steps to recover components, see Section 17.2.6. For the steps specific to recovering from loss of host, see Section 17.3.5.
The following sections describe backup and recovery recommendations for Web Tier installations:
This section describes the Oracle HTTP Server data that must be backed up and restored.
Database Repository Dependencies
None
Backup Recommendations
For Oracle HTTP Server in a standalone domain, back up the domain. For Oracle HTTP Server in a WebLogic Server domain, back up the domain.
Recovery Recommendations
For Oracle HTTP Server in a standalone domain, restore the domain that contains Oracle HTTP Server, as described in Section 17.2.3. For loss of host, restore the domain, as described in Section 17.3.2 and make configuration changes as described in Section 17.3.5.5.1 or Section 17.3.5.5.2.
For Oracle HTTP Server in a WebLogic Server domain, restore the domain, as described in Section 17.2.2. For loss of host, restore the domain as described in Section 17.3.1 and make configuration changes as described in Section 17.3.5.5.2.
This section describes the Oracle Data Integrator data that must be backed up and restored.
Database Repository Dependencies
ODI_REPO schema
Backup Recommendations
Back up the Oracle home, domain if Oracle Data Integrator is installed in a domain, and the ODI_Oracle_Home/oracledi/agent folder for each machine where a standalone agent is installed.
Back up the database containing Oracle Data Integrator schema.
Recovery Recommendations
Recover the database to the most recent point in time, if needed.
Depending on the extent of the failure and the type of Oracle Data Integrator installation, restore the Managed Server or the Oracle home, or both.
If your environment contains the Oracle Data Integrator Standalone Agent, restore the Oracle home, as described in Section 17.2.1.
If your environment contains Oracle Data Integrator for Developers, restore the Oracle home, as described in Section 17.2.1.
If your environment contains Oracle Data Integrator deployed in a Managed Server, restore the Managed Server, as described in Section 17.2.5.
For the steps to recover Oracle Data Integrator from loss of host, see Section 17.3.5.6.
The following assumptions and restrictions apply to the backup and recovery procedures in this book. Also see the restrictions listed in Section 16.2.
Only the user who installs the product or a user who has access privileges to the directories where Oracle Fusion Middleware has been installed should be able to execute backup and recovery operations.
If a single Managed Server and Administration Server run on different hosts and the Managed Server is not in a cluster, you must use the pack and unpack commands on the Managed Server to retrieve the correct configuration.
See Also: If you are using Cold Failover Cluster or Disaster Recovery, refer to the Oracle Fusion Middleware Disaster Recovery Guide for additional information. |
This part provides information about how to find information about the cause of an error and its corrective action, to view and manage log files to assist in monitoring system activity and to diagnose problems and how to monitor Oracle Fusion Middleware.
Part V contains the following chapters:
Administering Oracle Fusion Middleware
12c (12.1.2)
E36206-04
December 2014
Describes how to manage Oracle Fusion Middleware, including how to start and stop Oracle Fusion Middleware, how to configure and monitor components, how to back up and recover your environment and how to move from a source environment to a target environment.
Oracle Fusion Middleware Administering Oracle Fusion Middleware, 12c (12.1.2)
E36206-04
Copyright © 2009, 2014, Oracle and/or its affiliates. All rights reserved.
Primary Author: Helen Grembowicz
Contributing Author: Vinaye Misra
Contributors: Mike Blevins, Nick Fry, Greg Cook, Harry Hsu, Christine Jacobs, Srini Indla, Pavana Jain, Rama Kalava, Gopal Kirsur, Kenneth Ma, Dan MacKinnon, Manoj Nayak, Mark Nelson, Praveen Sampath, Sunita Sharma
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
This chapter describes how to view and change Oracle Fusion Middleware port numbers, such as port numbers used by Oracle WebLogic Server or Oracle HTTP Server.
It contains the following sections:
Many Oracle Fusion Middleware components and services use ports. Most port numbers are assigned during domain creation. As an administrator, it is important to know the port numbers used by these services, and to ensure that the same port number is not used by two services on your host.
For some ports, you can specify a port number assignment during domain creation.
See Also: Appendix D for a list of port numbers. Refer to the installation guide for directions on overriding port assignments during installation. |
You can view the port numbers currently in use with the command line or Fusion Middleware Control, as described in the following topics:
To view the port numbers for Oracle WebLogic Server, you can use the WLST get
command, with an attribute. For example, to get the Administration Port, use the following command:
wls:/WLS_domain/serverConfig> get('AdministrationPort') 9002
You can view the port numbers of the domain, the Administration Server, Managed Servers, or components, such asOracle HTTP Server, using Fusion Middleware Control.
For example, to view the ports of a domain:
From the navigation pane, select the domain.
From the WebLogic Domain menu, choose Monitoring, then Port Usage.
The Port Usage page is displayed, as shown in the following figure:
Optionally, you can filter the ports shown by selecting a Managed Server from Show.
The Port Usage detail table shows the ports that are in use, the IP Address, the component, the channel, and the protocol.
You can also view similar pages for the Administration Server, Managed Servers, and components, such as Oracle HTTP Server, by navigating to the target and choosing Port Usage from the target's menu.
You can change the port numbers for some Oracle Fusion Middleware components, using Fusion Middleware Control, Oracle WebLogic Server Administration Console, or the command line.
Note: You can change a port number to any number you want, if it is an unused port. You do not have to use a port in the allotted port range for the component. See Appendix D for information on allotted port ranges. |
This section provides the following topics:
For information about changing other ports, see:
"Overview of Node Manager Configuration" in the Administering Node Manager for Oracle WebLogic Server for information about changing the Node Manager port.
You can change the non-SSL (HTTP) listen port and the SSL (HTTPS) listen port for a WebLogic Server Administration Server or a Managed Server using the Oracle WebLogic Server Administration Console or WLST, as described in the following topics:
See Administering Server Environments for Oracle WebLogic Server for more information about changing Oracle WebLogic Server ports.
To change the non-SSL (HTTP) listen port and the SSL (HTTPS) listen port for a WebLogic Server Administration Server or a Managed Server using the Oracle WebLogic Server Administration Console:
Navigate to the server.
The Settings for server_name page is displayed.
Select the Configuration tab. On the General tab, change the number of the Listen Port or SSL Listen Port.
If the server is running, restart the server.
If other components rely on the Oracle WebLogic Server listen ports, you must reconfigure those components.
To change the non-SSL (HTTP) listen port and the SSL (HTTPS) listen port for a WebLogic Server Administration Server or a Managed Server using the WLST command line. You must run the commands in offline mode; that is, you must not be connected to a server.
For example to change the Administration Server HTTP listen port to port 8001, use the following WLST commands:
readDomain("oracle/config/domains/domain_name")
cd("servers/AdminServer")
cmo.setListenPort(8001)
updateDomain()
To change the Oracle HTTP Server Listen ports (non-SSL or SSL), there are often dependencies that must also be set.
The following topics describe how to modify the Oracle HTTP Server HTTP or HTTPS Listen port:
Enabling Oracle HTTP Server to Run as Root for Ports Set to Less Than 1024 (UNIX Only)
Changing the Oracle HTTP Server Non-SSL Listen Port in a WebLogic Server Domain
Changing the Oracle HTTP Server SSL Listen Port in a WebLogic Server Domain
Changing the Oracle HTTP Server Listen Ports in a Standalone Domain
On a UNIX system, if you are changing the Listen port to a number less than 1024, perform these steps before you change the Oracle HTTP Server Listen port.
By default, Oracle HTTP Server runs as a non-root user (the user that installed Oracle Fusion Middleware). On UNIX systems, if you change the Oracle HTTP Server Listen port number to a value less than 1024, you must enable Oracle HTTP Server to run as root, as follows:
Log in as root.
Run the following commands in the Oracle home:
cd ORACLE_HOME/ohs/bin
chown root .apachectl
chmod 6750 .apachectl
To change the Oracle HTTP Server non-SSL (HTTP) Listen port, follow the procedures in the following tasks. Note that, on a UNIX system, if you are changing the Listen port to a number less than 1024, you must first perform the steps in Section 5.3.2.1.
To change the Oracle HTTP Server Listen port using Fusion Middleware Control:
From the navigation pane, expand Web Tier, then select the Oracle HTTP Server instance.
From the Oracle HTTP Server menu, choose Administration, then Ports Configuration.
Select the Listen port that uses the HTTP protocol, then click Edit.
Change the port number, then click OK.
Restart Oracle HTTP Server. (From the Oracle HTTP Server menu, choose Control, then Restart.)
To change the Oracle HTTP Server SSL (HTTPS) Listen port, follow the procedures in the following tasks. Note that, on a UNIX system, if you are changing the Listen port to a number less than 1024, you must perform the steps in Section 5.3.2.1.
To change the Oracle HTTP Server SSL Listen port using Fusion Middleware Control:
From the navigation pane, expand Web Tier, then select the Oracle HTTP Server instance.
From the Oracle HTTP Server menu, choose Administration, then Ports Configuration.
Select the Listen port that uses the HTTPS protocol, then click Edit.
Change the port number, then click OK.
Restart Oracle HTTP Server. (From the Oracle HTTP Server menu, choose Control, then Restart.)
To change the Oracle HTTP Server non-SSL and SSL Listen Ports, modify the following files:
DOMAIN_HOME/config/fmwconfig/components/OHS/instances/component_name/httpd.conf DOMAIN_HOME/config/fmwconfig/components/OHS/instances/component_name/admin.conf DOMAIN_HOME/config/fmwconfig/components/OHS/instances/component_name/ssl.conf
If your environment includes an Oracle Database that functions as a metadata repository, and you want to change the listener port number for that database, perform the procedure in this section.
First, determine if it is necessary to change the listener port number. If you are concerned that you have another database on your host using the same port, both databases can possibly use the same port.
Note that multiple Oracle Database 10g and Oracle Database 11g databases can share the same Oracle Net listener port. If you are using an Oracle Database as a metadata repository on the same host that contains another Oracle Database 10g or Oracle Database 11g database, they can all use port 1521. There is no need to change the listener port number.
Note: To run two listeners that use the same key value on one host, refer to Section 5.3.3.1, "Changing the KEY Value for an IPC Listener" |
The procedure consists of the following tasks:
Stop all components that use the Metadata Repository. See Chapter 4 for instructions.
On the metadata repository host:
Ensure that the ORACLE_HOME and ORACLE_SID environment variables are set.
Stop the metadata repository listener:
lsnrctl stop
Edit the listener.ora
file, which is located at:
(UNIX) ORACLE_HOME/network/admin/listener.ora (Windows) ORACLE_HOME\network\admin\listener.ora
Under the LISTENER
entry, update the value for PORT
. Save the file.
Edit the tnsnames.ora
file. The default location is:
(UNIX) ORACLE_HOME/network/admin/tnsnames.ora (Windows) ORACLE_HOME\network\admin\tnsnames.ora
Make the following changes to the file:
Update the PORT
value in each entry that applies to MDS Repository.
Add an entry similar to the following:
newnetport = (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp) (HOST = hostname) (PORT = port)))
In the example, hostname
is the fully qualified host name and port
is the new port number.
Start the metadata repository listener:
lsnrctl start
Using SQL*Plus, log in to the metadata repository as the SYSTEM user with SYSDBA privileges and run the following command:
SQL> ALTER SYSTEM SET local_listener='newnetport' scope=spfile;
Using SQL*Plus, restart the metadata repository:
SQL> SHUTDOWN SQL> STARTUP
(UNIX) DOMAIN_HOME/bin/startComponent.sh OID1 (Windows) DOMAIN_HOME\bin\startComponent.cmd OID1
Change the system data source to use the new port number for the metadata repository. To do so, you can use Fusion Middleware Control:
In the Change Center, click Lock & Edit.
In the navigation pane, expand select the domain.
The WebLogic Domain page is displayed.
From the WebLogic Domain menu, select JDBC Data Sources.
The Summary of JDBC Data Sources page is displayed.
Select the data source you want to change.
The JDBC Data Source page is displayed.
Select the Connection Pool tab.
To change the database port, modify the Database URL field. For example:
jdbc:oracle:thin:@hostname.domainname.com:1522/orcl
Click Save.
Restart the servers that use this data source. (Click the Targets tab to see the servers that use this data source.)
It is not possible to run two listeners at the same time that are configured to use the same KEY value in their IPC protocol address. By default, the metadata repository listener has its IPC KEY value set to EXTPROC. Hence, if your computer has another IPC listener that uses the EXTPROC key, you should configure the metadata repository listener to use some other key value such as EXTPROC1.
To change the KEY value of an IPC listener:
Stop the listener (ensure that your ORACLE_HOME environment variable is set first):
lsnrctl stop
Edit the listener.ora
and tnsnames.ora
files. In each file, find the following line:
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
Change it to the following:
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
Restart the listener:
lsnrctl start
This chapter describes procedures for starting and stopping Oracle Fusion Middleware, including the Administration Server, Managed Servers, and components.
It contains the following sections:
Starting and Stopping Oracle WebLogic Server Administration and Managed Servers
Starting and Stopping Your Oracle Fusion Middleware Environment
Oracle Fusion Middleware is a flexible product that you can start and stop in different ways, depending on your requirements. In most situations, you can use Fusion Middleware Control, Oracle WebLogic Server Administration Console, or the WLST commands to start or stop Oracle Fusion Middleware components.
These tools are completely compatible and, in most cases, can be used interchangeably. For example, you can start a J2EE component using WLST and stop it using Fusion Middleware Control.
You can start Oracle WebLogic Server Administration Servers using the WLST command line. You can start and stop Managed Servers using scripts, the WLST command line, the WebLogic Server Administration Console, or Fusion Middleware Control. The following sections describe how to start and stop WebLogic Servers using the WLST command line, Fusion Middleware Control, or both:
You can start and stop the Oracle WebLogic Server Administration Server using the WLST command line or a script. When you start or stop the Administration Server, you also start or stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.
For example, to start an Administration Server, use the following script:
DOMAIN_HOME/bin/startWebLogic.sh
To stop an Administration Server, use the following script:
DOMAIN_HOME/bin/stopWebLogic.sh username password [admin_url]
By default, Node Manager is configured when you configure Oracle Fusion Middleware. If Node Manager is not configured, it is very important to change the Node Manager property StartScriptEnabled
to True
. If this property is set to False
you will encounter errors or problems when starting Managed Servers configured for use by Oracle Fusion Middleware components. See Section 2.8.1 for more information.
You can start Node Manager using the WLST command line or a script.
To start Node Manager, use the following script:
(UNIX) DOMAIN_HOME/bin/startNodeManager.sh (Windows) DOMAIN_HOME\bin\startNodeManager.cmd
To stop Node Manager, close the command shell in which it is running.
Alternatively, after having set the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. For more information, see stopNodeManager in the WLST Command Reference for WebLogic Server.
You can start and stop Managed Servers using Fusion Middleware Control or WLST commands and scripts, as described in the following topics:
Fusion Middleware Control and the Oracle WebLogic Server Administration Console use Node Manager to start Managed Servers. If you are starting a Managed Server that does not contain Oracle Fusion Middleware products other than Oracle WebLogic Server, you can start the servers using the procedure in this section.
However, if the Managed Server contains other Oracle Fusion Middleware products, such as Oracle JRF, you must first configure Node Manager, as described in Section 2.8.1.
To start or stop a WebLogic Server Managed Server using Fusion Middleware Control:
From the navigation pane, expand the domain.
Select the Managed Server.
From the WebLogic Server menu, choose Control, then Start Up or Shut Down.
Alternatively, you can right-click the server, then choose Control, then Start Up or Shut Down.
You can use a script or WLST to start and stop a WebLogic Server Managed Server.
For example, to start a WebLogic Server Managed Server, use the following script:
(UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url (Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url
When prompted, enter your user name and password.
To stop a WebLogic Server Managed Server, use the following script:
(UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url username password (Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url username password
For information about using WLST to start and stop Managed Servers, see "Managing the Server Life Cycle" in Understanding the WebLogic Scripting Tool.
You can enable the Administration Server and Managed Servers to start without prompting you for the administrator user name and password.
For the Administration Server, create a boot.properties file:
Create the following directory:
DOMAIN_HOME/servers/AdminServer/security
Use a text editor to create a file called boot.properties in the security directory created in the previous step, and enter the following lines in the file:
username=adminuser password=password
For each Managed Server:
Create the following directory:
DOMAIN_HOME/servers/server_name/security
Copy the boot.properties file you created for the Administration Server to the security directory you created in the previous step.
Restart the Administration Server and Managed Servers, as described in Section 4.2.1 and Section 4.2.3.
Note: When you start the Administration Server or Managed Server, the user name and password entries in the file are encrypted.For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible in order for the entries to be encrypted. |
For more information, see "Boot Identity Files" in Administering Server Startup and Shutdown for Oracle WebLogic Server.
If you want a WebLogic Server instance to start automatically when you boot a Windows host computer, you can set up the server as a Windows service. For complete information, see "Setting Up a WebLogic Server Instance as a Windows Service" in Administering Server Startup and Shutdown for Oracle WebLogic Server.
However, that chapter describes the process for a standalone Oracle WebLogic Server installation. When Oracle WebLogic Server is part of an Oracle Fusion Middleware environment, you must set the environment to include references to ORACLE_COMMON. To do that, the script that you create is slightly different from that in "Example Script for Setting Up a Server as a Windows Service". The following shows the correct script:
echo off SETLOCAL set DOMAIN_NAME=myWLSdomain set USERDOMAIN_HOME=d:\Oracle\config\domains\myWLSdomain set SERVER_NAME=myWLSserver set PRODUCTION_MODE=true set JAVA_OPTIONS=-Dweblogic.Stdout="d:\Oracle\config\domains\myWLSdomain\ stdout.txt" -Dweblogic.Stderr="d:\Oracle\config\domains\myWLSdomain\stderr.txt" set ADMIN_URL=http://adminserver:7501 set MEM_ARGS=-Xms40m -Xmx250m call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd call "d:\Oracle_home\wlserver\server\bin\installSvc.cmd" ENDLOCAL
You can start and stop components using the command line, the WebLogic Server Administration Console, or Fusion Middleware Control, depending upon the component. The following topics describe how to start and stop components using Fusion Middleware Control and the command line:
To start or stop a component:
From the navigation pane, navigate to the component.
Select the component, such as OHS.
From the dynamic target menu, choose Control, then Start Up or Shut Down.
If a component is a Java component, you use WLST commands to start and stop the component. If a component is a system component, you can use scripts to call WLST commands to start and stop the components, as described in the following topics:
To start and stop Java components, use the WLST startApplication
and stopApplication
commands:
startApplication(appName, [options]) stopApplication(appName, [options])
For example, to start Oracle Web Services Manager Policy Manager, use the following command:
startApplication("wsm-pm")
If a component is a system component, you can use scripts to call WLST commands to start and stop the components or you can use WLST commands:
To start and stop system components using scripts, use the startComponent and stopComponent scripts. You can use this method for Oracle HTTP Server in a standalone domain or a WebLogic Server domain.
The scripts are located in
(UNIX) DOMAIN_HOME/bin (Windows) DOMAIN_HOME\bin
To start or stop a component using these scripts, use the following syntax:
./startComponent.sh component_name [storeUserConfig] [showErrorStack] ./stopComponent.sh component_name [storeUserConfig] [showErrorStack]
In the syntax:
component_name
: The name of the component instance, such as ohs1.
storeUserConfig
: When specified, the script will prompt you for the user name and password. Then, it will ask you if you want to store the user configuration in a properties file. If you specify y
, it creates a user configuration file and an associated key file. The user configuration file contains an encrypted user name and password. The key file contains a secret key that is used to encrypt and decrypt the user name and password. The following shows the names and location of the properties files:
user_home/.wlst/nm-key-domain_name.props user_home/.wlst/nm-cfg-domain_name.props
After you have stored the information in the properties file, when you run the scripts subsequently, you will not be prompted for a user name and password.
showErrorStack
: Provides more detailed error information, including all of the messages in the error stack. Specify this option if you need to determine the cause of errors.
For example, to start an Oracle HTTP Server instance called ohs1:
./startComponent.sh ohs1
You can also use these scripts to start and stop system components remotely. In that case, the scripts read the configuration to determine the location of the component.
To start system components using WLST commands, you can use one of the following methods:
The nmstart command. You can use this method for Oracle HTTP Server in a standalone domain or a WebLogic Server domain.
For example, to start the Oracle HTTP Server component OHS1, use the following WLST commands:
nmConnect(domainName='domain_name', username='username', password='password') nmstart(serverName='OHS1', serverType='OHS')
The WLST start command. You can use this method for Oracle HTTP Server in a standalone domain.
For example, to start the Oracle HTTP Server component OHS1, use the following WLST commands:
connect('username','password','hostname:port') start('OHS1')
To stop system components using WLST commands, use the WLST nmkill command.
For example, to kill the Oracle HTTP Server component OHS1, use the following WLST commands:
nmKill(serverName='ohs1', serverType='OHS')
To decide which method to use, note the following:
If you are using a WLST script, use the WLST commands.
To quickly start and stop system components interactively, use the scripts.
To start and stop system components remotely, use the scripts.
If Fusion Middleware Control is configured for a domain, it is automatically started or stopped when you start or stop an Oracle WebLogic Server Administration Server, as described in Section 4.2.1.
You can start and stop applications using Fusion Middleware Control, the WebLogic Server Administration Console, or the WLST command line. The following topics describe how to start and stop applications using Fusion Middleware Control and the command line:
To start or stop a Java EE application using Fusion Middleware Control:
From the navigation pane, expand Application Deployments.
Select the application.
From the Application Deployment menu, choose Control, then Start Up or Shut Down.
To start or stop a Java EE application with the WLST command line, use the following commands:
startApplication(appName, [options]) stopApplication(appName, [options])
The application must be fully configured and available in the domain. The startApplication
command returns a WLSTProgress object that you can access to check the status of the command. In the event of an error, the command returns a WLSTException. For more information about the WLSTProgress object, see "WLSTProgress Object" in Understanding the WebLogic Scripting Tool.
This section provides procedures for starting and stopping an Oracle Fusion Middleware environment. An environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple Managed Servers, Java components, system components, including Identity Management components, and a database used as a repository for metadata. The components may be dependent on each other. Therefore, it is important to start and stop them in a particular order.
To start an Oracle Fusion Middleware environment:
Start the database that hosts the metadata schemas. The following steps illustrate one method for starting the database.
Navigate to the location of the database. For example, the database may reside on a different host than Oracle Fusion Middleware.
Set the ORACLE_HOME environment variable to the Oracle home for the database.
Set the ORACLE_SID environment variable to the SID for the database (default is orcl
.)
Start the Net Listener:
ORACLE_HOME/bin/lsnrctl start
Start the database instance:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> startup
SQL> quit
For more information about starting an Oracle Database, see the Oracle Database Administrator's Guide.
Start the Oracle WebLogic Server Administration Server as described in Section 4.2.1.
Start Node Manager as described in Section 4.2.2.
Start any Oracle Identity Management components, such as Oracle Internet Directory, which form part of your environment.
Start the Oracle WebLogic Server Managed Servers as described in Section 4.2.3.2.
Note: The start up of a Managed Server will typically start up the applications which are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.
Start all other system components, such as Oracle HTTP Server:
(UNIX) DOMAIN_HOME/bin/startComponent.sh component_name (Windows) DOMAIN_HOME\bin\startComponent.cmd component_name
To stop an Oracle Fusion Middleware environment:
Stop system components, such as Oracle HTTP Server. You can stop them in any order:
(UNIX) DOMAIN_HOME/bin/stopComponent.sh component_name (Windows) DOMAIN_HOME\bin\stopComponent.cmd component_name
Stop the Oracle WebLogic Server Managed Servers, as described in Section 4.2. Any applications deployed to the server are also stopped.
Stop any11g Oracle Identity Management components, such as Oracle Internet Directory, which form part of your environment.
Stop the Administration Server as described in Section 4.2.1.
Stop Node Manager as described in Section 4.2.2.
Start the database that hosts the metadata schemas. The following steps illustrate one method for stopping the database.
Navigate to the location of the database. For example, the database may reside on a different host than Oracle Fusion Middleware.
Set the ORACLE_HOME environment variable to the Oracle home for the database.
Set the ORACLE_SID environment variable to the SID for the database (default is orcl
).
Stop the database instance:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> shutdown
SQL> quit
Stop the Net Listener:
ORACLE_HOME/bin/lsnrctl stop
For more information about stopping an Oracle Database, see the Oracle Database Administrator's Guide.
This section contains the following special topics about starting and stopping Oracle Fusion Middleware:
There are special considerations and procedures for starting and stopping High Availability environments, such as:
Oracle Fusion Middleware Cold Failover Cluster
Oracle Application Server Disaster Recovery
See the High Availability Guide for information about starting and stopping in high-availability environments.
If you find that the Oracle Database instance is taking a long time to shut down, you can use the following commands to force an immediate shutdown:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> SHUTDOWN IMMEDIATE;
An immediate database shutdown proceeds with the following conditions:
No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
Any uncommitted transactions are rolled back. (If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name.)
Oracle does not wait for users currently connected to the database to disconnect. Oracle implicitly rolls back active transactions and disconnects all connected users.
The next startup of the database will not require any instance recovery procedures.
For more information about shutting down an Oracle Database, Oracle Database Administrator's Guide in the Oracle Database documentation library
Oracle Fusion Middleware is a comprehensive family of products ranging from application development tools and integration solutions to identity management, collaboration, and business intelligence reporting. This chapter provides an introduction to Oracle Fusion Middleware.
It includes the following sections:
Oracle Fusion Middleware is a collection of standards-based software products that spans a range of tools and services: from Java EE and developer tools, to integration services, identity management, business intelligence, and collaboration. Oracle Fusion Middleware offers complete support for development, deployment, and management.
For information about Oracle Fusion Middleware concepts, see Understanding Oracle Fusion Middleware.
Oracle Fusion Middleware provides the following components:
Oracle WebLogic Server, an enterprise-ready Java application server that supports the deployment of mission-critical applications in a robust, secure, highly available, and scalable environment.
Oracle HTTP Server, which provides a Web listener for Java EE applications and the framework for hosting static and dynamic pages and applications over the Web. Based on the proven technology of the Apache HTTP Server, Oracle HTTP Server includes significant enhancements that facilitate load balancing, administration, and configuration.
Oracle Web Services Manager, which provides a way to centrally define and manage policies that govern Web services operations, including access control (authentication and authorization), reliable messaging, Message Transmission Optimization Mechanism (MTOM), WS-Addressing, and Web services management. Policies can be attached to multiple Web services, requiring no modification to the existing Web services.
Oracle Platform Security, which provides enterprise product development teams, systems integrators, and independent software vendors (ISVs) with a standards-based, portable, integrated, enterprise-grade security framework for Java Standard Edition (Java SE) and Java Enterprise Edition (Java EE) applications.
Oracle Platform Security provides an abstraction layer in the form of standards-based application programming interfaces (APIs) that insulate developers from security and identity management implementation details. With Oracle Platform Security, developers do not need to know the details of cryptographic key management or interfaces with user repositories and other identity management infrastructures. When you use Oracle Platform Security, in-house developed applications, third-party applications, and integrated applications benefit from the same uniform security, identity management, and audit services across the enterprise.
This chapter describes how to monitor Oracle Fusion Middleware using Fusion Middleware Control, Oracle WebLogic Server Administration Console, and the command line.
It describes the following sections:
Monitoring the health of your Oracle Fusion Middleware environment and ensuring that it performs optimally is an important task for the administrator.
Oracle Fusion Middleware provides the following methods for monitoring the status of your environment:
Fusion Middleware Control: You can monitor the status of Oracle WebLogic Server domains, clusters, servers, Java components, system components, and applications. Navigate to the entity's home page, for example, to the home page for an Oracle HTTP Server instance.
Oracle WebLogic Server Administration Console: You can monitor the status of Oracle WebLogic Server domains, clusters, servers, Java components, and applications. From the Administration Console, navigate to the entity's page. See "Overview of the Administration Console" in Understanding Oracle WebLogic Server for information on monitoring using the console.
The command line: You can monitor the status of your environment using the WLST state command.
To monitor the status of Java components, use the WLST state
command, with the following format:
state(name, type)
For example, to get the status of the Managed Server server1, use the following command:
wls:/mydomain/serverConfig> state('server1','Server') Current state of "server1": SUSPENDED
To monitor the status of system components, use the WLST state
command, with the following format:
state('component_name')]
For example, to view the status ohs1, use the following command:
state('ohs1')]
Most of the monitoring tasks in this chapter describe how to monitor using Fusion Middleware Control or the command line.
The following topics provide more detail:
You can view the status of a domain, including the servers, clusters, and deployments in the domain from the domain home page of Fusion Middleware Control:
From the WebLogic Domain menu, select Home.
The domain home page is displayed, as shown in the following figure:
This page shows the following:
A general summary of the domain, along with a link to the Oracle WebLogic Server Administration Console
Information about the servers, both the Administration Server and the Managed Servers, in the domain
Information about the clusters in the domain
Information about the deployments in the domain
A Resource Center, which provides links to more information
For information about monitoring an Oracle WebLogic Server domain using the Oracle WebLogic Server Administration Console, see "Overview of the Administration Console" in the Understanding Oracle WebLogic Server. The Administration Console provides details about the health and performance of the domain.
You can view the status of a WebLogic Server Administration Server or Managed Server in Fusion Middleware Control:
From the navigation pane, expand the domain.
Select the server.
The server home page is displayed.
The following figure shows the home page for a Managed Server:
This page shows the following:
A general summary of the server, including its state, and information about the servlets, JSPs, and EJBs running in the server
Response and load
Information about the applications deployed to the server
For information about monitoring servers using the Oracle WebLogic Server Administration Console, see "Overview of the Administration Console" in Understanding Oracle WebLogic Server. The Administration Console provides details about the health and performance of the server.
You can view the status of a cluster, including the servers and deployments in the cluster using Fusion Middleware Control:
From the navigation pane, expand the domain.
Select the cluster.
The cluster page is displayed, as shown in the following figure:
This page shows the following:
A general summary of the cluster, including the broadcast channel, if appropriate, the load algorithm, and the messaging mode
A response and load section, which shows the requests per minute and the request processing time
A deployments section with information about the applications deployed to the cluster
A servers section, with a table listing the servers that are part of the cluster
See Also: "Overview of the Administration Console" in the Understanding Oracle WebLogic Server for information about monitoring a cluster using Oracle WebLogic Server Administration Console. The Administration Console provides details about the health and performance of the cluster. |
To monitor a system component, such as Oracle HTTP Server:
From the navigation pane, expand Web Tier.
Select the component, such as ohs1.
The component home page is displayed, as shown in the following figure:
This page shows the following:
A response and load section, which shows the requests per second and the request processing time
CPU and memory usage
The virtual hosts, with their names, request throughput and response size.
Module request statistics, with a list of modules and the throughput for each.: A table listing the processing time for each module
A Resource Center with links to relevant documentation
To monitor a Java EE application using Fusion Middleware Control:
From the navigation pane, expand Application Deployments, then select the application to monitor.
The application's home page is displayed.
In this page, you can view a summary of the application's status, entry points to the application, Web services and modules associated with the application, and the response and load.
The following figure shows a portion of the application's home page:
This page shows the following:
A summary of the application, including its state, the Managed Server on which it is deployed, and information about active sessions, active requests, and request processing time
A Deployments section, with the application and its status.
A list of modules with the type of module for each
Response and load, which shows the requests per minute and the request processing time
A list of most requested servlets, JSPs, and Web services
To monitor an ADF application:
From the navigation pane, expand Application Deployments, then select the application to monitor.
The application's home page is displayed.
The following figure shows a portion of the application's home page:
A summary of the application, including its state, the Managed Server on which it is deployed, and information about active sessions, active requests, and request processing time
Deployments, which lists the servers on which the application is deployed.
A list of modules with the type of module for each
A list of data sources
To view health of the environment, from the Application Deployments menu choose Monitoring, then Environment Monitoring. The Environment Monitoring page is displayed.
It contains tabs for Health, Query Caching, Workload, and Coherence.
If you deploy an application to a cluster, Oracle Fusion Middleware automatically deploys the application to each Managed Server in the cluster. As a result, there is an instance of the application on each server.
There are times when you want to monitor the performance of the application on an individual server, and times when you want to monitor the overall performance of the application across all the servers in the cluster.
For example, normally, you would manage the overall performance of the application to determine if there are any performance issues affecting all users of the application, regardless of which instance users access. If you notice a performance problem, you can then drill down to a specific instance of the application to determine if the problem is affecting one or all of the application instances in the cluster.
Fusion Middleware Control provides monitoring pages for both of these scenarios:
From the navigation pane, expand Application Deployments.
Fusion Middleware Control lists the applications deployed in the current domain.
If an application has been deployed to a cluster, expand the application in the navigation pane. Fusion Middleware Control shows that it is deployed to the cluster application to indicate that it represents more than one instance of the application on the cluster:
Monitor the overall performance of the application on the cluster by clicking the cluster application, or monitor the performance of the application on a single server by clicking one of the application deployment instances.
If you encounter a problem, such as an application that is running slowly or is hanging, you can view more detailed performance information, including performance metrics for a particular target, to find out more information about the problem.
Oracle Fusion Middleware automatically and continuously measures run-time performance. The performance metrics are automatically enabled; you do not need to set options or perform any extra configuration to collect them.
Note that Fusion Middleware Control provides real-time data. If you are interested in viewing historical data, consider using Oracle Enterprise Manager Grid Control.
For example, to view the performance of an Oracle WebLogic Server Managed Server:
From the navigation pane, expand the domain.
Select the server to monitor.
The Managed Server home page is displayed.
From the WebLogic Server menu, choose Monitoring, then Performance Summary.
The Performance Summary page is displayed. It shows performance metrics, as well as information about response time and request processing time for applications deployed to the Oracle WebLogic Server.
To see additional metrics, click Show Metric Palette and expand the metric categories.
The following figure shows the Performance Summary page with the Metric Palette displayed:
Select a metric to add it to the Performance Summary.
To overlay another target, click Overlay, and select the target. The target is added to the charts, so that you can view the performance of more than one target at a time, comparing their performance.
To customize the time frame shown by the charts, you can:
Click Slider to display a slider tool that lets you specify that more or less time is shown in the charts. For example, to show the past 10 minutes, instead of the past 15 minutes, slide the left slider control to the right until it displays the last 10 minutes.
Select the calendar and clock icon. Then, enter the Start Time and End Time. If there is no data available for those times, a confirmation message displays, explaining the timeline will be automatically adjusted to the time period for which the data is available.
You can also view the performance of a components, such as Oracle HTTP Server. Navigate to the component and select Monitoring, then Performance Summary from the dynamic target menu.
Fusion Middleware Control provides a Topology Viewer for the domain. The Topology Viewer is a graphical representation of routing relationships across components and elements of the domain You can easily determine how requests are routed across components. For example, you can see how requests are routed from Oracle HTTP Server, to a Managed Server, to a data source.
Note: To view relationships between Oracle WebLogic Server and Oracle HTTP Server, each target must be running and show its status as Up. |
The Topology Viewer enables you to easily monitor your Oracle Fusion Middleware environment. You can see which entities are up and which are down.
You can also print the topology.
To view the topology:
From the WebLogic Domain menu, click Routing Topology.
The Routing Topology page is displayed.
The following shows the Routing Topology page with information about the Managed Server:
With Topology Viewer, you can also:
Choose how to group the routing. From the View menu, you can choose to group by Middleware, host, or application.
View the targets by status. Click the green up arrow or the red down arrow at the top of the page. A list of the targets with the specified status is shown.
Search for a target within the topology. This makes it easier to find a target if you have many targets. Click the Toggle Find Toolbar. Then, enter the name in the Find box, and click Find.
The Find results box is displayed. Click the target name to highlight the target. The topology is repositioned so you can see the target if it was not previously visible in the viewing area.
You can also specify criteria for the search. From Find, choose the one or more types of Status or one or more of Target Type, or both.
Hide or show the status or metrics. From Annotations, click Status or Metrics.
If you select Metrics, one or more key performance metrics for the component are displayed. (You cannot change the metrics that are displayed.)
Reposition the topology and change its orientation:
To change the orientation, from the Options menu, choose Layout, then Left to Right or Top Down.
To reposition the topology, click in the topology, but not on a target or route. Drag the topology to position it.
To change what is visible in the topology view, click the arrow in the right-hand bottom corner Then, drag the shaded section in the navigator window, which is located in the bottom right.
Navigate to the home page of a target. Right-click the target, and select Home.
Perform operations directly on the target by right-clicking. The right-click target menu is displayed. For example, from this menu, you can start or stop an Oracle WebLogic Server or view additional performance metrics.
View the routing relationships between components. For example, you can view the routing from Oracle HTTP Server to Oracle WebLogic Server. Clicking on the line between the two targets displays the URLs used.
This part contains the following appendixes:
Deployment is the process of packaging application files as an archive file and transferring them to a target application server. This chapter describes how to deploy applications, to Oracle Fusion Middleware.
It contains the following sections:
Deploying, Undeploying, and Redeploying Java EE Applications
Deploying, Undeploying, and Redeploying Oracle ADF Applications
About the Common Deployment Tasks in Fusion Middleware Control
Changing MDS Configuration Attributes for Deployed Applications
Oracle WebLogic Server provides a Java EE-compliant infrastructure for deploying, undeploying, and redeploying Java EE-compliant applications and modules.
The following topics describe:
You can deploy the following into Oracle WebLogic Server:
A complete Java EE application packaged as an Enterprise Archive (EAR) file.
Standalone modules packaged as Java Archive files (JARs) containing Web services, Enterprise JavaBeans (EJBs), application clients (CARs), or resource adapters (RARs).
An ADF application. Oracle Application Development Framework (Oracle ADF) is an end-to-end application framework that builds on Java Platform, Enterprise Edition (Java EE) standards, and open-source technologies to simplify and accelerate implementing service-oriented applications.
A Metadata Archive (MAR) is a compressed archive of selected metadata, such as the application-level deployment profile, for an application. A MAR is used to deploy metadata content to the metadata service (MDS) repository. ADF applications use a MAR as a container for content that is deployed to the MDS Repository.
Note: If your application uses password indirection in the application-level data source, you cannot use Fusion Middleware Control to deploy the application. The section "Deploying an Application to an EAR File to run on Oracle WebLogic Server" in the Oracle JDeveloper Help describes how to change the settings of the application to be able to deploy the application using Fusion Middleware Control. |
You can use Fusion Middleware Control, Oracle WebLogic Server Administration Console, Oracle JDeveloper, or the command line to deploy, undeploy, or redeploy an application. Which method you use depends on the type of application, as described in Table 9-1.
Table 9-1 Tools to Deploy Applications
Type of Application | Tools to Use |
---|---|
Pure Java EE application |
Oracle WebLogic Server Administration Console Fusion Middleware Control: Deployment Wizard Oracle JDeveloper WLST command line |
ADF application |
Fusion Middleware Control: Deployment Wizard Oracle JDeveloper WLST command line |
If your application uses an MDS Repository, you must register the repository with the Oracle WebLogic Server domain before you deploy your application. Applications such as custom Java EE applications developed by your organization and some Oracle Fusion Middleware component applications, such as Oracle Web Services Manager, use an MDS Repository. For information about the MDS Repository and registering the repository, see Section 13.3.
Note: If your application contains an application-level credential store, and you are moving the application from a test to a production environment, you must reassociate the credential store, as described in "Reassociating the Domain Policy Store" in the Securing Applications with Oracle Platform Security Services. |
When you deploy an application, you deploy it to the application server for the first time.
When you redeploy an application, you can:
Redeploy a new version of the application; the previous version is still available, but the state is set to "Retired."
This is known as the production redeployment strategy. Oracle WebLogic Server automatically manages client connections so that only new client requests are directed to the new version. Clients already connected to the application during the redeployment continue to use the older version of the application until they complete their work, at which point Oracle WebLogic Server automatically retires the older application.
Redeploy the same version of the application or redeploy an application that is not assigned a version; the application version you select is replaced with the new deployment.
Redeploy a previous version of the application; the earlier, retired version is set to "Active" and the later version is set to "Retired."
When you undeploy an application, Oracle WebLogic Server stops the application and removes staged files from target servers. It does not remove the original source files used for deployment.
The following topics describe data sources and how to manage them:
A data source is a Java object that application components use to obtain connections to a relational database. Specific connection information, such as the URL or user name and password, are set on a data source object as properties and do not need to be explicitly defined in an application's code. This abstraction allows applications to be built in a portable manner, because the application is not tied to a specific back-end database. The database can change without affecting the application code.
Applications use the Java Naming and Directory Interface (JNDI) API to access a data source object. The application uses a JNDI name that is bound to the data source object. The JNDI name is logical and can be mapped to any data source object. Like data source properties, using JNDI provides a level of abstraction, since the underlying data source object can change without any changes required in the application code. The end result is the details of accessing a database are transparent to the application.
See Administering JDBC Data Sources for Oracle WebLogic Server for more information about data sources.
When you configure certain Oracle Fusion Middleware components using the Oracle WebLogic Server Configuration Wizard, you specify the data source connection information. If the components use the MDS Repository, the Configuration Wizard prepends "mds-" to the data source name to indicate that the data source is a system data source used by MDS Repository.
See Creating Domains Using the Configuration Wizard for information about specifying data sources with the Configuration Wizard.
If you are using Oracle Real Application Clusters (Oracle RAC) or Oracle Fusion Middleware Cold Failover Cluster, you must configure one of the following types of data sources:
Multi data sources
To use multi data sources, you must use the Oracle WebLogic Server Administration Console. Note that if you create a multi data source and you add an existing MDS data source to it, the data source you added is no longer considered a valid MDS Repository. The repository is not displayed in Fusion Middleware Control or Oracle WebLogic Server Administration Console. For example, the MDS Repository is not listed in the Fusion Middleware Control navigation pane and is not displayed as a choice for a target metadata repository when you deploy an application.
GridLink data sources
To use GridLink data sources, you can use the Oracle WebLogic Server Administration Console or Fusion Middleware Control, as described in Section 9.2.2.5.
See Administering JDBC Data Sources for Oracle WebLogic Server for more information about configuring multi data sources and GridLink data sources
You can create and manage JDBC data sources using the following management tools:
The Oracle WebLogic Server Administration Console
The WebLogic Scripting Tool (WLST)
Fusion Middleware Control
To create an MDS data source manually, you should use Fusion Middleware Control or WLST to set the correct attributes for the data source. The MDS data source is displayed in the navigation pane in Fusion Middleware Control and in the domain structure in the Administration Console. If your application uses an MDS Repository, you must register the repository with the Oracle WebLogic Server domain before you deploy your application. For information about the MDS Repository and registering the repository, see Section 13.3.
Note: When you create the data source, you must use the MDS schema created by the Repository Creation Utility (RCU), not other schemas. |
Although it is not recommended, you can also use the Oracle WebLogic Server Administration Console to create a MDS data source. If you do, note the following:
You must prefix the data source name with "mds-" if you intend it to be used with MDS Repository.
You must target the data source to the Administration Server and to all Managed Servers to which you are deploying applications that need the data source.
You must turn off global transactions.
See Administering JDBC Data Sources for Oracle WebLogic Server for information about creating and managing a data source using the Oracle WebLogic Server Administration Console or WLST and for more information about configuring multiple data sources.
The following topics describe how to create and manage JDBC data sources with Fusion Middleware Control:
Monitoring a JDBC Data Source Using Fusion Middleware Control
Controlling a JDBC Data Source Using Fusion Middleware Control
Creating a GridLink Data Source Using Fusion Middleware Control
To create a JDBC data source using Fusion Middleware Control:
From the WebLogic Domain menu, choose JDBC Data Sources.
The JDBC Data Sources page is displayed, as shown in the following figure:
From Create, select Generic Data Source.
Follow the instructions in the wizard to set the properties of the data source and to target the data source for one or more of the Managed Servers in the domain.
For help on individual fields and properties, use your mouse to give focus to a field. Fusion Middleware Control displays a popup definition of the field.
Note that the data source properties you define in Fusion Middleware Control are similar to those you define when creating data sources in the Oracle WebLogic Server Administration Console. As a result, you can also refer to "Creating a JDBC Data Source" in Administering JDBC Data Sources for Oracle WebLogic Server for more information about the data source properties.
To edit an existing JDBC data source using Fusion Middleware Control:
From the WebLogic Domain menu, choose JDBC Data Sources.
The JDBC Data Sources page is displayed.
Click the data source that you want to edit.
The page for that particular JDBC Data Source is displayed.
Use the tabs on this page to modify the properties of the selected data source.
For help on individual fields and properties, use your mouse to give focus to a field. Fusion Middleware Control displays a popup definition of the field.
Note that the data source properties you edit in Fusion Middleware Control are similar to those you edit when editing data sources in the Oracle WebLogic Server Administration Console. As a result, you can also refer to "Creating a JDBC Data Source" in Administering JDBC Data Sources for Oracle WebLogic Server for more information about the data source properties.
To monitor a JDBC data source using Fusion Middleware Control:
From the WebLogic Domain menu, choose JDBC Data Sources.
The JDBC Data Sources page is displayed.
Select the data source that you want to monitor.
Click Monitoring to display the Monitor JDBC Data Source page.
This page shows the current instances of the selected data source.
Note that only data sources that are targeted to a running Managed Server are shown on this page. If a specific data source is not listed on the monitoring page, then edit the data source to be sure it is targeted to a running Managed Server.
For each data source instance, review the performance metrics.
To start, stop, suspend, resume, or clear the statement cache for a JDBC data source using Fusion Middleware Control:
From the WebLogic Domain menu, choose JDBC Data Sources.
The JDBC Data Sources page is displayed.
Select the data source that you want to edit.
Select the Control tab.
Note that only data sources that are targeted to a running Managed Server are shown on this page. If a specific data source is not listed on the control page, edit the data source to be sure that it is targeted to a running Managed Server.
Select the instance and click Start, Stop, Resume, Suspend, Shrink, Reset, Clear Statement Cache to control or change the state of the selected JDBC data source.
Note that the commands you select on this page are similar to those available when you are managing data sources in the Oracle WebLogic Server Administration Console. Refer to "Managing WebLogic JDBC Resources" in Administering JDBC Data Sources for Oracle WebLogic Server for more information about the JDBC data source control options.
A single GridLink data source provides connectivity between WebLogic Server and an Oracle Database service targeted to an Oracle RAC cluster. For detailed information about GridLink data sources, see "Creating a GridLink Data Source" in Administering JDBC Data Sources for Oracle WebLogic Server.
To create a Grid Link data source using Fusion Middleware Control:
From the WebLogic Domain menu, choose JDBC Data Sources.
The JDBC Data Sources page is displayed.
From Create, select GridLink Data Source.
Follow the instructions in the wizard to set the properties of the data source and to target the data source for one or more of the Managed Servers in the domain.
For help on individual fields and properties, use your mouse to give focus to a field. Fusion Middleware Control displays a popup definition of the field.
Note that the data source properties you define in Fusion Middleware Control are similar to those you define when creating data sources in the Oracle WebLogic Server Administration Console. As a result, you can also refer to "Creating a GridLink Data Source" in Administering JDBC Data Sources for Oracle WebLogic Server for more information about the data source properties.
You can use Fusion Middleware Control, Oracle WebLogic Server Administration Console, Oracle JDeveloper, or the command line to deploy, undeploy, or redeploy a Java EE application. The following topics describe using Fusion Middleware Control and the command line to accomplish these tasks:
See Deploying Applications to Oracle WebLogic Server for information about deploying using Oracle WebLogic Server Administration Console and the WLST command line.
You can deploy an application to a WebLogic Server Managed Server instance or a cluster. This section describes how to deploy an application to a Managed Server.
To deploy a Java EE application to a Managed Server using Fusion Middleware Control:
From the navigation pane, expand the domain.
Select the server in which you want to deploy the application.
The server home page is displayed.
From the WebLogic Server menu, choose Control, then Deployments.
The Deployments page is displayed.
Click Deploy to open the Deploy Java EE Application Assistant.
The Select Archive page is displayed, as shown in the following figure:
In the Archive or Exploded Directory section, you can select one of the following:
Archive is on the machine where this browser is running. Enter the location of the archive or click Browse to find the archive file.
Archive or exploded directory is on the server where Enterprise Manager is running. Enter the location of the archive or click Browse to find the archive file.
In the Deployment Plan section, you can select one of the following:
Create a new deployment plan when deployment configuration is done.
Deployment plan is on the machine where this Web browser is running. If you select this option, enter the path to the plan.
Deployment plan is on the server where Enterprise Manager is running. If you select this option, enter the path to the plan.
In the Deployment Type section, you can select one of the following:
Deploy this archive or exploded directory as an application
Deploy this archive or exploded directory as a library
Click Next.
The Select Target page is displayed.
Select the target to which you want to deploy the application. The Administration Server, Managed Servers, and clusters are listed. You can select a cluster, one or more Managed Servers in the cluster, or a Managed Server that is not in a cluster. Although the Administration Server is shown in the list of targets, you should not deploy an application to it. The Administration Server is intended only for administrative applications such as the Oracle WebLogic Server Administration Console.
Click Next.
The Application Attributes page is displayed.
In the Application Attributes section, for Application Name, enter the application name.
In the Context Root of Web Modules section, if the Web module does not have the context root configured in the application.xml file, you can specify the context root for your application. The context root is the URI for the Web module. Each Web module or EJB module that contains Web services may have a context root.
In the Distribution section, you can select one of the following:
Install and start application (servicing all requests)
Install and start application in administration mode (servicing only admin requests)
Install only. Do not start.
You can expand Other Options, which provides the following for Application Source Accessibility:
Use the defaults defined by the deployment's targets. Recommended selection.
Copy this application onto every target. During deployment, the files will be copied automatically to the Managed Servers to which the application is targeted.
In Other Options, you can also select one of the following for Deployment Plan Source Accessibility:
Use the same accessibility as the application.
Copy the deployment plan onto every target. During deployment, the files will be copied automatically to the Managed Servers to which the application is targeted.
Make the deployment plan accessible from the source location that it will be deployed on. You must ensure that each target can reach the location.
Click Next.
The Deployment Wizard, Deployment Settings page is displayed.
On this page, you can perform common tasks before deploying your application or you can edit the deployment plan or save it to a disk.
See Section 9.6 for more detailed information about these tasks.
Depending on the type of application, in the Deployment Tasks section, you can:
Configure Web modules: Click Go to Task in the Configure Web Modules row. The Configure Web Modules page is displayed. Click Configure General Properties to view and edit the general configuration for the Web Module or Map Resource References to map the resource references.
For example, you can change the session invalidation interval or the maximum age of session cookies.
Configure EJB modules: Click Go to Task in the Configure EJB modules row to set standard EJB deployment descriptor properties. The Configure EJB Modules page is displayed. Click Configure EJB Properties to view and edit the general configuration for the EJBs or Map Resource References to map the resource preferences.
For example, you can configure the maximum number of beans in the free pool or the network access point.
Configure application security: Click Go to Task in the Configure Application Security row. Depending on what type of security is used, different pages are displayed, as described in Section 9.6.
Configure persistence: Click Go to Task in the Configure Persistence row to configure Java Persistent API (JPA) persistence units.
Expand Deployment Plan.
You can edit and save the deployment plan, if you choose. If you edit the deployment plan and change descriptor values, those changes are saved to the deployment plan. In addition, the following configurations are saved to the deployment plan:
Application attributes
Web module configuration
EJB configuration
Application attributes related to MDS are stored in the file adf-config.xml. Application security attributes are stored in weblogic-application.xml.
Fusion Middleware Control updates the relevant files and repackages the .ear file.
Click Deploy.
Fusion Middleware Control displays processing messages.
When the deployment is completed, click Close.
To deploy an application to multiple servers at the sa me time, navigate to the domain. Then, from the WebLogic Domain menu, select Application Deployment, then Deploy. The deployment wizard displays a page where you can select the servers.
To deploy an application to a cluster, select the cluster. Then, from the Cluster menu, select Application Deployment, then Deploy.
You can deploy an application using the WLST command line. To deploy a Java EE application when WLST is connected to the Administration Server, you use the WLST command deploy
, using the following format:
deploy(app_name, path [,targets] [,stageMode] [,planPath] [,options])
You must invoke the deploy command on the computer that hosts the Administration Server.
For example, to deploy the application mainWebApp:
deploy("myApp","/scratch/applications/wlserveR/samples/server/examples/build/mainWebApp")
You can also deploy the application using the weblogic.deployer, as shown in the following example:
java weblogic.Deployer -adminurl http://localhost:7001 -user username -password password -deploy -name myApp c:\localfiles\mainWebApp -plan c:\localfiles\productionEnvPlan.xml
See Also:
|
You can undeploy an application or a specific version of an application from a WebLogic Server Managed Server instance or a cluster. This section describes how to undeploy an application from a Managed Server. If an application has been deployed to multiple servers, when you undeploy it using Fusion Middleware Control, the application is undeployed from all the servers.
To undeploy a Java EE application from a Managed Server using Fusion Middleware Control:
From the navigation pane, expand Application Deployments.
Select the application to undeploy.
The application home page is displayed.
From the Domain Application Deployment menu, choose Deployments.
Select the application.
In Confirmation page, click Undeploy.
Processing messages are displayed.
When the operation completes, click Close.
Alternatively, you can navigate to the domain, Managed Server, or cluster. Then, from the target's menu, choose Application Deployment, then Undeploy. In the Select Application page, select the application you want to undeploy.
You can undeploy an application using the WLST command line. To undeploy a Java EE application when WLST is connected to the Administration Server, you use the WLST command undeploy
, using the following format:
undeploy(app_name, path [,targets] [,options])
You must invoke the undeploy command on the computer that hosts the Administration Server.
For example, to undeploy the application businessApp from all target servers and specify that WLST wait 60,000 ms for the process to complete:
wls:/mydomain/serverConfig> undeploy('businessApp', timeout=60000)
You can redeploy a new version of an updated application, redeploy the same version, or redeploy a non-versioned application. You can redeploy an application to a cluster or a Managed Server.
The following sections describe how to redeploy an application to a Managed Server:
If you are redeploying a non-versioned application or a versioned application with the same version, note the following:
The file name and path for the archive you are redeploying must be identical to the file name and path you used when you initially deployed the application.
For example, if the file name and path of the original application was /dua0/staging/myApp.ear, then the revised application must be /dua0/staging/myApp.ear.
f you initially deployed the application using the Oracle WebLogic Server Administration Console or WLST or other management tools other and Fusion Middleware Control, then you cannot redeploy the application using Fusion Middleware Control.
To redeploy a Java EE application to a Managed Server using Fusion Middleware Control:
From the navigation pane, expand Application Deployments.
Select the application to redeploy.
The application home page is displayed.
From the Application Deployment menu, choose Deployments.
Click Redeploy.
The Select Application page is displayed.
Click Next.
In the Archive or Exploded Directory section, you can select one of the following:
Archive is on the machine where this browser is running. Enter the location of the archive or click Browse to find the archive file.
Archive or exploded directory is on the server where Enterprise Manager is running. Enter the location of the archive or click Browse to find the archive file.
In the Deployment Plan section, you can select one of the following:
Create a new deployment plan when deployment configuration is done.
Deployment plan is on the machine where this Web browser is running. Enter the path to the plan or click Browse to find the plan file.
Deployment plan is on the server where Enterprise Manager is running. Enter the path to the plan or click Browse to find the plan file.
Click Next.
The Application Attributes page is displayed.
Click Next.
The Deployment Wizard, Deployment Settings page is displayed.
On this page, you can perform common tasks before deploying your application or you can edit the deployment plan or save it to a disk. Depending on the type of application, in the Deployment Tasks section, you can:
Configure Web modules
Configure application security
Configure EJB modules
Configure persistence
See Section 9.6 for detailed information about these tasks.
Expand Deployment Plan.
You can edit and save the deployment plan, if you choose. If you edit the deployment plan and change descriptor values, those changes are saved to the deployment plan. In addition, the following configurations are saved to the deployment plan:
Application attributes
Web module configuration
EJB configuration
Application attributes related to MDS are stored in the file adf-config.xml. Application security attributes are stored in weblogic-application.xml.
Fusion Middleware Control updates the relevant files and repackages the .ear file.
Click Redeploy.
Processing messages are displayed.
When the operation completes, click Close.
To redeploy an application to a cluster, select the cluster. Then, from the target's menu, select Application Deployment, then Redeploy.
You can redeploy an application using the WLST command line. To redeploy a Java EE application when WLST is connected to the Administration Server, you use the WLST command redeploy
, using the following format:
redeploy(app_name [,planpath] [,options])
You must invoke the redeploy command on the computer that hosts the Administration Server.
For example, to redeploy the application businessApp from all target servers:
redeploy('businessApp')
Oracle ADF is an end-to-end application framework that builds on Java Platform, Enterprise Edition (Java EE) standards and open-source technologies to simplify and accelerate implementing service-oriented applications.
You can use Fusion Middleware Control, Oracle WebLogic Server Administration Console, Oracle JDeveloper, or the command line to deploy, undeploy, or redeploy an Oracle ADF application. The following topics describe using Fusion Middleware Control, the Administration Console, and the command line to accomplish these tasks:
See Developing Fusion Web Applications with Oracle Application Development Framework for information on developing ADF applications and for deploying them using Oracle JDeveloper
You can deploy an application to a WebLogic Server Managed Server instance or a cluster. This section describes how to deploy an application to a Managed Server. This example assumes that you have created an .ear file containing the ADF application.
To deploy an Oracle ADF application using Fusion Middleware Control:
From the navigation pane, expand the domain.
Select the server in which you want to deploy the application.
The server home page is displayed.
From the WebLogic Server menu, choose Control, then Deployments.
The Deployments page is displayed.
Click Deploy.
The Select Archive page is displayed.
In the Archive or Exploded Directory section, you can select one of the following:
Archive is on the machine where this browser is running. Enter the location of the archive or click Browse to find the archive file.
Archive or exploded directory is on the server where Enterprise Manager is running. Enter the location of the archive or click Browse to find the archive file.
In the Deployment Plan section, you can select one of the following:
Create a new deployment plan when deployment configuration is done.
Deployment plan is on the machine where this Web browser is running. Enter the path to the plan.
Deployment plan is on the server where Enterprise Manager is running. Enter the path to the plan.
In the Deployment Type section, you can select one of the following:
Deploy this archive or exploded directory as an application
Deploy this archive or exploded directory as a library
Click Next.
The Select Target page is displayed.
Select the target to which you want to deploy the application.
You can select a cluster, one or more Managed Servers in the cluster, or a Managed Server that is not in a cluster.
Click Next.
The Application Attributes page is displayed, as shown in the following figure:
In the Application Attributes section, for Application Name, enter the application name.
In the Context Root of Web Modules section, if the Web module does not have the context root configured in the application.xml file, you can specify the context root for your application. The context root is the URI for the Web module. Each Web module or EJB module that contains Web services may have a context root.
In the Target Metadata Repository section, you can choose the repository and partition for this application. If the partition name is not specified in the adf-config.xml file, the application name plus the version is used as the default partition name. This ensures that the partition used is unique in the domain so that the metadata for different applications are not accidentally imported into the same repository partition and overwrite each other. Typically, each application's metadata is deployed to its own partition.
To change the repository, click the icon next to the Repository Name. In the Metadata Repositories dialog box, select the repository and click OK.
To change the partition, enter the partition name in Partition Name. Oracle recommends that you create a new partition for each application. If you enter a name of a partition that does not exist, the partition is created.
The adf-config.xml file in the .ear file is updated with the new information.
If the partition or repository specified in the application is not valid in the domain, Fusion Middleware Control displays a message.
If the application's adf-config.xml file archive contains MDS configuration for an MDS shared repository, the Shared Metadata Repository section is displayed. In this section, you can choose the repository and partition for this application. If the partition or repository specified in the application is not valid in the domain, Fusion Middleware Control displays a message.
If you change the repository or partition, the adf-config.xml file in the .ear file is updated with the new information.
In the Distribution section, you can select one of the following:
Install and start application (servicing all requests)
Install and start application in admin mode (servicing only administration requests)
Install only. Do not start.
You can expand Other Options. See Section 9.3.1 for a description of those options.
Click Next.
The Deployment Wizard, Deployment Settings page is displayed.
On this page, you can perform common tasks before deploying your application or you can edit the deployment plan or save it to a disk. Depending on the type of application, in the Deployment Tasks section, you can:
Configure Web modules: Click Go to Task in the Configure Web Modules row. The Configure Web Modules page is displayed. Click Configure General Properties to view and edit the general configuration for the Web Module or Map Resource References to map the resource references.
For example, you can change the session invalidation interval or the maximum age of session cookies.
Configure EJB modules: Click Go to Task in the Configure EJB modules row to set standard EJB deployment descriptor properties. The Configure EJB Modules page is displayed. Click Configure EJB Properties to view and edit the general configuration for the EJBs or Map Resource References to map the resource preferences.
For example, you can configure the maximum number of beans in the free pool or the network access point.
Configure application security: Click Go to Task in the Configure Application Security row. Depending on what type of security is used, different pages are displayed, as described in Section 9.6.
Configure persistence: Click Go to Task in the Configure Persistence row to configure Java Persistent API (JPA) persistence units.
Configure ADF Connections: To modify the ADF connections, click Go to Task in the Configure ADF Connections row. The Configure ADF Connections page is displayed, showing the current connection information. To modify a connection type, click the Edit icon for a particular row. For example, you can modify the connection information for an external application. For more information about ADF connections, see Developing Fusion Web Applications with Oracle Application Development Framework.
For more information about these options, see Section 9.6.
Expand Deployment Plan.
You can edit and save the deployment plan, if you choose.
Click Deploy.
Fusion Middleware Control displays processing messages.
When the deployment is completed, click Close.
You can deploy an ADF application using the WLST command line or the Oracle WebLogic Server Administration Console.
Take the following steps:
If your application uses an MDS Repository, you must configure the application archive (.ear) file before you deploy your application. You must provide the repository information for the deploy target repository and any shared metadata repositories using the WLST getMDSArchiveConfig command. The repository specified must already be registered with the domain before deploying the application. The following example show how to use this command to get the MDSArchiveConfig and call the setAppMetadataRepository method to set the deploy target repository. Otherwise, your application will fail to start.
wls:/offline> archive = getMDSArchiveConfig(fromLocation='/tmp/App1.ear') wls:/offline> archive.setAppMetadataRepository(repository='AppRepos1', partition='partition1', type='DB', jndi='mds-jndi1')
The operation places the changes in the MDS configuration portion of the adf-config.xml file in the archive file.
Save the changes to the original .ear file, using the following command:
wls:/offline> archive.save()
Deploy the application.
To deploy an application when WLST is connected to the Administration Server, you use the WLST command deploy
, using the following format:
deploy(app_name, path [,targets] [,stageMode] [,planPath] [,options])
You must invoke the deploy command on the computer that hosts the Administration Server.
For example, to deploy the application myApp:
deploy("myApp","/scratch/applications/myApp", targets='myserver', timeout=120000))
See Also:
|
To deploy the application using the Oracle WebLogic Server Administration Console:
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.
In the left pane of the Administration Console, select Deployments.
In the right pane, click Install.
To undeploy an Oracle ADF application using Fusion Middleware Control:
From the navigation pane, expand Application Deployments.
Select the application to undeploy.
The application home page is displayed.
From the Domain Application Deployment menu, choose Deployments.
Select the application.
In Confirmation page, click Undeploy.
Processing messages are displayed.
When the operation completes, click Close.
Alternatively, you can navigate to the domain, Managed Server, or cluster. Then, from the target's menu, choose Application Deployment, then Undeploy. In the Select Application page, select the application you want to undeploy.
Note that when you undeploy an application, documents stored in the MDS partition are not deleted.
When you redeploy an application, if the application contains a Metadata Archive (MAR), the contents of the MAR is imported to the application's metadata repository only if the MAR is changed. If the MAR is unchanged from previous deployment of the application, it is ignored.
If you are redeploying a non-versioned application or a versioned application with the same version, note the following:
The file name and path for the archive you are redeploying must be identical to the file name and path you used when you initially deployed the application.
For example, if the file name and path of the original application was /dua0/staging/myApp.ear, then the revised application must be /dua0/staging/myApp.ear.
f you initially deployed the application using the Oracle WebLogic Server Administration Console or WLST or other management tools other and Fusion Middleware Control, then you cannot redeploy the application using Fusion Middleware Control.
To redeploy an Oracle ADF application using Fusion Middleware Control:
From the navigation pane, expand Application Deployments.
Select the application to redeploy.
The application home page is displayed.
From the Domain Application Deployment menu, choose Deployments.
Click Redeploy.
Click Next.
The Select Archive page is displayed.
In the Archive or Exploded Directory section, you can select one of the following:
Archive is on the machine where this browser is running. Enter the location of the archive or click Browse to find the archive file.
Archive or exploded directory is on the server where Enterprise Manager is running. Enter the location of the archive or click Browse to find the archive file.
In the Deployment Plan section, you can select one of the following:
Create a new deployment plan when deployment configuration is done.
Deployment plan is on the machine where this web browser is running. Enter the path to the plan.
Deployment plan is on the server where Enterprise Manager is running. Enter the path to the plan.
Click Next.
The Application Attributes page is displayed.
In the Application Attributes section, for Application Name, enter the application name.
In the Context Root of Web Modules section, if the Web module does not have the context root configured in the application.xml file, you can specify the context root for your application. The context root is the URI for the Web module. Each Web module or EJB module that contains Web services may have a context root.
The Target Metadata Repository section is displayed. In this section, you can choose the repository and partition for this application:
To change the repository, click the icon next to the Repository Name. In the Metadata Repositories dialog box, select the repository and click OK.
To change the partition, enter the partition name in Partition Name. Oracle recommends that you create a new partition for each application. If you enter a name of a partition that does not exist, the partition is created.
If the application's adf-config.xml file archive contains MDS configuration for an MDS shared repository, the Shared Metadata Repository section is displayed. In this section, you can choose the repository and partition for this application.
Click Next.
The Deployment Settings page is displayed.
On this page, you can perform common tasks before deploying your application or you can edit the deployment plan or save it to a disk. In the Deployment Tasks section, you can:
Configure Web modules
Configure application security
Configure persistence
See Section 9.6 for detailed information about these options.
Expand Deployment Plan.
You can edit and save the deployment plan, if you choose.
Click Deploy.
Fusion Middleware Control displays processing messages.
When the deployment is completed, click Close.
In the Confirmation page, click Redeploy.
A deployment plan is a client-side aggregation of all the configuration data needed to deploy an archive into Oracle WebLogic Server. A deployment plan allows you to easily deploy or redeploy an application using a saved set of configuration settings.
A new deployment plan is created by default if you do not apply an existing deployment plan to an application at the time of deployment, as described in Section 9.3.1. Once created, you can save a deployment plan as a file and reuse it for redeploying the application or for deploying other applications.
However, if you change the configuration of an application after it is deployed (for example, if you modify the MDS configuration of an application), ]then any existing deployment plans you saved no longer represent the configuration settings of the deployed application.
In such a situation, you can fetch a new deployment plan that more closely represents the configuration of the deployed application.
To fetch the deployment plan of an application that is currently deployed:
From the WebLogic Domain menu, choose Deployments.
Select an application from the list of currently deployed applications.
Click Fetch Deployment Plan.
The Fetch Deployment Plan page is displayed.
Select a location where you want to save the deployment plan, and click Fetch.
You can save the plan to the computer where the Web browser is running or to the computer where Fusion Middleware Control is running.
In the resulting dialog box, specify a directory location for the saved deployment plan.
You can now use this deployment plan to later deploy or redeploy the application using the configuration currently in use by the application.
Alternatively, you can edit a deployment plan on the Deployment Settings page of the Application Deployment wizard.
When you deploy an application using Fusion Middleware Control, you can use the Deployment Settings page of the Deployment wizard to perform specific deployment configuration tasks before the application is deployed.
The following describes the deployment tasks that can appear on the Deployment Settings page, depending on the type of application you are deploying.
Configure Web modules
This deployment task is available when you are deploying any application that includes a Web module. In most cases, this means the application contains a Web application deployment descriptor (web.xml or weblogic.xml); however, a Web module can also be identified by annotations in the Java code of the application.
You can use this deployment task to set standard Web application deployment descriptor properties, such as:
Session validation interval
Maximum age of session cookies
Configure EJBs
This deployment task is available for any application that includes an EJB module. In most cases, this means the application contains an EJB deployment descriptor (ejb-jar.xml or weblogic-ejb-jar.xml); however, an EJB module can also be identified by annotations in the Java code of the application.
You can use this deployment task to set standard EJB deployment descriptor properties, such as:
The maximum number of beans in the free pool
The EJB network access point
Configure Application Security
This deployment task is available for all application types. However, the options available when you select this task vary depending on the existence of the following files in the application:
jazn-data.xml
If the jazn-data.xml file exists in the application, then you can:
Append, overwrite, or ignore policy migration.
If you are deploying the application for the first time, then select Append.
If the application was previously deployed and the application authorization policy exists, then select Append, or select Ignore to keep the application authorization policy.
To overwrite the previous policy, then select Overwrite.
Specify the Application stripe ID, if the stripe ID is inconsistent with the one defined in the migration options.
Specify that policies are removed when the application is undeployed.
cwallet.sso
If an cwallet.sso file exists in the application, then you can set additional application credential migration options.
If the application contains both files, the page displays both sections.
For more information about the settings available when you select the Configure Application Security deployment task, see "Deploying Java EE and Oracle ADF Applications with Fusion Middleware Control" in Securing Applications with Oracle Platform Security Services.
If neither of these files exists in the application, then you can use this task to determine how user roles and policies will be defined when the application is deployed. For example, you can choose to use only the roles and policies defined in the deployment descriptors, or you can choose to use only the roles and policies defined on the server. The Configure Application Security page displays the following options:
Deployment Descriptors Only: Use only roles and policies that are defined in the deployment descriptors.
Custom Roles: Use roles that are defined in the Administration Console; use policies that are defined in the deployment descriptor.
Custom Roles and Policies: Use only roles and policies that are defined in the Administration Console.
Advanced: Use a custom model that you have configured on the realm's configuration page.
Configure persistence
This deployment task is available for applications that contain one or more persistence.xml files. Using this task, you can configure the Java Persistent API (JPA) persistence units for the application.
You can view details about each persistence unit and define a Java Transaction API (JTA) data source or non-JTA data source for each persistence unit.
Configuring the data sources for persistence units can be useful for applications that take advantage of Oracle TopLink. For more information, refer to the Solutions Guide for Oracle TopLink.
For more information about how persistence units and the persistence.xml file can be used in Java EE applications, refer to the definition of Persistence Units in the Java EE 5 Tutorial at the following Web site:
http://download.oracle.com/javaee/5/tutorial/doc/bnbqw.html#bnbrj
Configure ADF connections
This deployment task is available for applications that use ADF connections. You can modify the connection information for an external application. For more information about ADF connections, see Developing Fusion Web Applications with Oracle Application Development Framework.
If your application uses an MDS Repository, you can modify configuration attributes after the application is deployed. To view or modify the attributes, you can use the System MBean Browser or WLST.
Note: Changes to the configuration persist in MDS as customizations. Because these persist as customizations:
|
The following topics describe how you can change the MDS configuration attributes:
To change the MDS configuration attributes of an application, take the following steps:
Navigate to the application's home page by expanding Application Deployments. Then, select an application.
The application's home page is displayed.
From the Application Deployment menu, choose System MBean Browser.
The System MBean Browser page is displayed.
Expand Application Defined MBeans, then oracle.adf.share.config, then Server: name, then Application: name, then ADFConfig, then ADFConfig, and ADFConfig.
Select MDSAppConfig.
The Application Defined MBeans page is displayed, as shown in the following figure:
You can view the description and values for the attributes.
Table 9-2 describes the configuration attributes that are specific to MDS. Note that other attributes, such as ConfigMBean appear in the browser, but these are generic attributes for all MBeans.
Table 9-2 MDS Configuration Attributes for Deployed Applications
Attribute | Description |
---|---|
AppMetadataRepositoryInfo |
Read only. Describes the metadata repository partition where the application is deployed. |
AutoPurgeTimeToLive |
Automatically purge versions of metadata documents older than the given time interval, specified in seconds. Any unlabeled versions older than this time interval are automatically purged on any subsequent update from this application. If the value is not set, versions are not automatically purged. |
ConfigMBean |
If true, indicates that this MBean is a Config MBean. |
DeployTargetRepository |
The name of the target repository configured for the application. |
eventProvider |
If true, it indicates that this MBean is an event provider as defined by JSR-77. |
eventTypes |
All the event's types emitted by this MBean. |
ExternalChangeDetection |
Specifies that the MDS Repository is polled to determine if any metadata changes have been performed on other cluster nodes or by other applications. If changes are detected, notifications are sent to applications that share the repository. Multiple applications can share metadata that is deployed to a shared repository. Changes performed by one application to this shared metadata can be detected by the other application. To do this, both the applications should configure the shared repository as part of their application configuration. If the MDS Repository is being used by more than one application in the same JVM, then MDS polls for changes if any of those applications have ExternalChangeDetection set to true. This attribute should only be set to false if the application metadata is never updated or if it is used only by this application and on a single server node. This attribute is applicable only to database-based repositories. The default is true. |
ExternalChangeDetectionInterval |
The maximum time interval, in seconds, to poll the MDS Repository to determine if there are external metadata changes. This attribute is only valid if ExternalChangeDetection is enabled. If the MDS Repository is shared and being used by more than one application in the same JVM, MDS uses the lowest of the values specified in the different applications for this attribute. As a result, changing the value of this parameter in one application only has an effect if the new value is lower than any values specified in the other applications. The default is 30 seconds. |
MaximumCacheSize |
The maximum metadata cache size limit, in kilobytes. If the value is 0, caching is disabled. If no value is specified, there is no cache limit. In this case, cached data is stored indefinitely. |
objectName |
All the event's types emitted by this MBean. |
ReadOnly |
If true, it indicates that this MBean is a read-only MBean. |
ReadOnlyMode |
Changes the application to read-only mode, so that no updates can be made to the application's repository partition, including configuration and application metadata. |
RemoteNotifications |
Enables distributed remote notifications of applicable metadata changes.This parameter is valid only if ExternalChangeDetection is enabled. |
RestartNeeded |
Enables distributed remote notifications of applicable metadata changes.This parameter is only valid if ExternalChangeDetection is enabled. |
RetryConnection |
Enables the application to retry the connection to the metadata repository after connection failure. |
SharedMetadataRepositoryInfo |
Read only. Specifies the MDS Repository partition used by the application. Note that an application can use more than one shared metadata repository. |
stateManageable |
If true, it indicates that this MBean provides State Management capabilities as defined by JSR-77. |
statisticsProvider |
If true, it indicates that this MBean is a statistic provider as defined by JSR-77. |
SystemMBean |
If true, it indicates that this MBean is a System MBean. |
Visible |
If true, it indicates that this MBean is visible to the current user. |
To view or modify an attribute, select the attribute.
The attribute page is displayed.
If the attribute is not read-only, you can change the values. For example, for AutoPurgeTimeToLive, you can change the interval, by entering a new value in Value.
Click Apply.
Navigate up to ADFConfig (the parent of MDSAppConfig) and select it.
In the Operations tab, click Save.
Click Invoke.
You can change the MDS configuration of an application using WLST. The following example shows a WLST script that reads and then sets the ReadOnlyMode attribute:
""" Getting ReadOnlyMode Attribute from MBean """ connect('username','password','hostname:port') application = 'application_name' attribute = 'ReadOnlyMode' beanName = 'oracle.adf.share.config:ApplicationName='+ application +',name=MDSAppConfig,type=ADFConfig,Application='+ application +',ADFConfig=ADFConfig,*' beanObjectName = ObjectName(beanName) beans = mbs.queryMBeans(beanObjectName, None) bean = beans.iterator().next().getObjectName() custom() value = mbs.getAttribute(bean, attribute) print value """ Setting ReadOnlyMode Attribute from MBean """ attr = Attribute(attribute, Boolean(0)) mbs.setAttribute(bean,attr) value = mbs.getAttribute(bean, attribute) print value """ Saving the Changes. This is required to persist the changes. """ adfConfigName = 'oracle.adf.share.config:ApplicationName='+ application + ',name=ADFConfig,type=ADFConfig,Application='+ application + ',*' adfConfigObjectName = ObjectName(adfConfigName) adfConfigMBeans = mbs.queryMBeans(adfConfigObjectName, None) adfConfigMBean = adfConfigMBeans.iterator().next().getObjectName() mbs.invoke(adfConfigMBean, 'save', None, None)
To restore the original MDS configuration for an application:
Navigate to the application's home page by expanding Application Deployments. Then, select an application.
The application's home page is displayed.
From the Application Deployment menu, choose System MBean Browser.
The System MBean Browser page is displayed.
Expand Application Defined MBeans, then oracle.adf.share.config, then Server: name, then Application: name, then ADFConfig, and then ADFConfig.
Select the Operations tab.
Select RestoreToOriginalConfiguration.
The Operation: restoreToOriginalConfiguration page is displayed.
Click Invoke.
Use this operation with caution. It causes all changes made to the original adf-config.xml file to be discarded. The adf-config.xml is restored to the base document.
This part describes how to expand your Oracle Fusion Middleware environment.
It contains the following chapters:
This part provides an overview to Oracle Fusion Middleware and its concepts as they relate to administering Oracle Fusion Middleware.
Part I contains the following chapter:
This appendix summarizes the command-line tools that are available in Oracle Fusion Middleware.
Table B-1 Oracle Fusion Middleware Command-Line Tools
Command | Path | Description |
---|---|---|
adrci |
UNIX: ORACLE_HOME/bin/adr/adcri.sh Windows: ORACLE_HOME\bin\adrci.bat |
Package incident and problem information into a zip file for transmission to Oracle Support. |
config |
UNIX: ORACLE_HOME/oracle_common/common/bin/config.sh Windows:ORACLE_HOME\oracle_common\common\bin\config.cmd |
Invoke the Configuration Wizard to created and configure a domain or extend a domain. See: The Installation Guide for the component. |
ua |
UNIX: ORACLE_HOME/oracle_common/upgrade/bin /ua Windows: ORACLE_HOME\oracle_common\upgrade\ua.bat |
Oracle Fusion Middleware Upgrade Assistant. See: Planning an Upgrade of Oracle Fusion Middleware |
orapki |
UNIX: ORACLE_HOME/oracle_common/bin/orapki Windows: ORACLE_HOME\oracle_common\bin\orapki.bat |
Manages wallets and certificates. See Appendix G. |
wlst |
UNIX: ORACLE_HOME/oracle_common/common/bin/wlst.sh Windows: ORACLE_HOME\oracle_common\common\bin\wlst.cmd |
(WebLogic Scripting tool) Manages Oracle WebLogic Server and the components in an Oracle WebLogic Server domain. See: Section 2.4, WLST Command Reference for WebLogic Server, and WLST Command Reference for Infrastructure Components |
This part describes advanced administration tasks, such as managing the metadata repository and changing the network configuration, that involve reconfiguring Oracle Fusion Middleware.
Part VI contains the following chapters:
This part describes how to secure communications between Oracle Fusion Middleware components using the Secure Sockets Layer (SSL) and how to use Oracle Fusion Middleware security features to administer keystores, wallets, and certificates.
Part III contains the following chapters:
This guide describes how to manage Oracle Fusion Middleware, including how to start and stop Oracle Fusion Middleware, how to change ports, deploy applications, how to back up and recover Oracle Fusion Middleware and how to move your environment from a source environment, such as a test environment to a target environment, such as a production environment.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc
.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info
or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs
if you are hearing impaired.
For more information, see the following documents in the Oracle Fusion Middleware 12c (12.1.2) documentation set:
The following text conventions are used in this document:
Convention | Meaning |
---|---|
boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
monospace | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. |