Oracle® Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite 11g Release 1 (11.1.1) E14495-04 |
|
![]() Previous |
![]() Next |
This appendix describes Fusion Middleware Configuration Wizard screens for configuring Oracle Enterprise Content Management Suite applications:
For more information about a screen, click the Help button on the screen. For more information about configuring Oracle WebLogic Server domains, see Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.
The Welcome screen appears each time you start the configuration wizard.
Select Create a new WebLogic domain to create a new Oracle WebLogic Server domain in your projects
directory.
Select Extend an existing WebLogic domain if you want to add applications and services, or to override existing database access (JDBC) and messaging (JMS) settings.
Click Next to continue.
Select the Oracle WebLogic Server directory to which you want to add your applications or services, or both.
Click Next to continue.
Select the source from which to create a new Oracle WebLogic Server domain. Select Generate a domain configured automatically to support the following products to create your domain to support selected products, and then select the products.
When you select Oracle Imaging and Process Management, you should also select Oracle Universal Content Management - Content Server.
When you select any Oracle ECM application on the Select Domain Source screen, Oracle Enterprise Manager and Oracle JRF are automatically selected. If you deselect any of these items that are automatically selected, the Oracle ECM application will also be deselected.
If you want a remote deployment of a Site Studio for External Applications web site, you can select Oracle Universal Content Management - SSXA Server to create an Oracle WebLogic Server domain with a Managed Server that has the files required to run the web site.
To create a domain that includes Oracle Web Services Manager (Oracle WSM) Policy Manager, select Oracle WSM Policy Manager.
Select Base this domain on an existing template to create your domain based on an existing domain template. Click Browse to navigate your directories to find an existing template.
Click Next to continue.
Select the source from which to extend an existing Oracle WebLogic Server domain. Select Extend my domain automatically to support the following added products, and then select the products.
When you select Oracle Imaging and Process Management, you should also select Oracle Universal Content Management - Content Server, if Oracle UCM is not already configured.
When you select any Oracle ECM application on the Select Extension Source screen, Oracle Enterprise Manager and Oracle JRF are automatically selected. If you deselect any of these items that are automatically selected, the Oracle ECM application will also be deselected.
If you want a remote deployment for a Site Studio for External Applications web site, you can select Oracle Universal Content Management - SSXA Server to extend an Oracle WebLogic Server domain with a Managed Server that has the files required to run the web site.
To extend a domain that includes Oracle Web Services Manager (Oracle WSM) Policy Manager, select Oracle WSM Policy Manager.
Click Next to continue.
Use the default domain name, domain location, and application location, or specify different ones.
Click Next to continue.
Create a user that will be assigned to the Administrator role. This user is the default administrator for starting development mode servers.
User name
Specify the user name.
User password
Specify the password for the user.
Confirm user password
Reenter the user password.
Description
Enter a description for the user. This field is optional.
Click Next to continue.
In the WebLogic Domain Startup Mode section, select one of the following startup modes:
Development Mode
In this mode, boot.properties
is used for user names and passwords, and polling is used for application deployment. Sun SDK is the default for this mode.
Production Mode
In this mode, user names and passwords are required, and polling is not used for application deployment. JRockit SDK is the default for this mode.
In the JDK Selection section, select a JDK from the list of available JDKs, or select Other JDK, and then click Browse to find another JDK on your system.
Click Next to continue.
Use this screen to edit the configuration information for each JDBC component schema.
A component schema contains a pool of database connections. Your application uses a component schema by looking it up in the JNDI tree, requesting a connection, using the connection, and then returning the connection to the component schema.
Click Next to continue.
Use this screen to test JDBC connections to application schemas.
Click Select All to select all of the schemas for connection testing, or select one or more individual schemas.
Click Unselect All to deselect all of the schemas.
Click Test Connections to test the JDBC connections to the selected schema or schemas.
The Connection Result Log section shows the results of connection testing.
Click Next to continue.
Select any of the server and cluster settings that you want to customize.
Note: To use clusters, you need a license for Oracle WebLogic Server Enterprise Edition. |
Click Next to continue.
Use this screen to change the default configuration of the Administration Server for an Oracle WebLogic Server domain. Each domain must have one Administration Server, which hosts the Oracle WebLogic Server Administration Console used to perform administration tasks. You can change values in these fields:
Name: The name of the Administration Server
Listen Address: An address on which the Administration Server will listen, selected from the list
Listen Port: The listen port number
SSL Listen Port: The port number for SSL connections, active when SSL enabled is selected
SSL Enabled: Enabled if selected and if a port number for SSL connections is provided in the SSL Listen Port field
Note: If SSL is enabled, before using Oracle WebLogic Scripting tool (WLST) to connect to the Administration Server, you must append the following parameters to the JVM_ARGS section of thewlst.sh file or set them in the CONFIG_JVM_ARGS environment variable:
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.TrustKeyStore=KeyStoreName
|
Click Next to continue.
A Managed Server is an instance of Oracle WebLogic Server used to host enterprise applications. A typical production environment has at least one Managed Server.
Use this screen to change the default configuration of Managed Servers. For each Managed Server, you can change values in these columns:
Name
Name of the Managed Server
Listen Address
An address on which the server will listen, selected from the list
Listen Port
Listen port number
SSL Listen Port
Port number for SSL connections, active when SSL enabled is selected in the same row
SSL Enabled
Enabled if selected and if a port number for SSL connections is provided in the same row
Click Next to continue.
Use this screen to configure Oracle WebLogic Server clusters.
A cluster contains multiple Oracle WebLogic Server instances running simultaneously and working together for scalability and reliability. To clients, a cluster appears as a single Oracle WebLogic Server instance.
Notes:
|
Click Next to continue.
Use this screen to assign Managed Servers to clusters that you added on the Configure Clusters screen.
If you configure a cluster and assign some, but not all, of the Managed Servers in the domain to a cluster, the Create HTTP Proxy Applications screen appears next.
Use this screen to create proxy applications for Managed Servers that you do not assign to a cluster in a domain that includes some clustered Managed Servers.
Use this screen to add or delete machines that host Oracle WebLogic Server instances.
The Administration Server and Node Manager use the machine configuration on this screen to start remote servers.
Click Next to continue.
Use this screen to assign at least one server to each machine you added on the Configure Machines screen.
Use this screen to target your deployments to Managed Servers or to clusters of Managed Servers. Doing so enables Oracle WebLogic Server to serve the deployments to clients.
Click Next to continue.
Use this screen to target your services (such as JMS and JDBC) to Managed Servers or to clusters of Managed Servers. Doing so enables your applications to use these services.
Click Next to continue.
Use this screen to select a distributed destination type for JMS.
Click Next to continue.
Use this screen to make changes to your security store. Make sure that your RDBMS tables are created prior to booting your domain. The scripts used by the DBA are located in the server/lib
directory under the Oracle WebLogic Server home directory.
Click Next to continue.
Use this screen to configure JMS file stores for web services.
Click Next to continue.
Review the contents of your domain.
Click Previous to go back and change something on a preceding screen.
Click Next to continue.
This screen shows the progress of the domain creation.
When the Progress bar shows 100%
, click Done to dismiss the window.
For information about starting the Administration Server and Managed Servers for the domain, see Section 10.1, "Starting the Administration Server," and Section 10.2, "Starting Managed Servers."
On a Windows operating system, you can select Start Admin Server on the Creating Domain screen to start the Administration Server for the domain when you click Done. This option is not available on a UNIX operating system.
This screen shows the progress of the domain extension.
When the Progress bar shows 100%
, click Done to dismiss the window.
For information about starting the Administration Server and Managed Servers for the domain, see Section 10.1, "Starting the Administration Server," and Section 10.2, "Starting Managed Servers."
On a Windows operating system, you can select Start Admin Server on the Extending Domain screen to start the Administration Server for the domain when you click Done. This option is not available on a UNIX operating system.