This chapter describes how to configure Application Developer after the software has already been installed.
The following topics are covered:
After the installation is complete, you can configure the components using the Oracle Fusion Middleware Configuration Wizard. The instructions in this section describe how to do so.
This section contains the following conent:
The Configuration Wizard is located in the MW_HOME/oracle_common/common/bin (on UNIX operating systems) or MW_HOME\oracle_common\common\bin (on Windows operating systems) directory. Go to this directory, then run the config.sh (on UNIX operating systems) or config.cmd (on Windows operating systems) script to start the Configuration Wizard:
On UNIX operating systems:
./config.sh
On Windows operating systems:
config.cmd
If this is a new installation and you need to create a new WebLogic domain, follow the instructions in Section 2.1.3, "Creating a New Domain". You can also run the Configuration Wizard to extend an existing WebLogic domain, as described in Section 2.1.4, "Extending an Existing Domain".
If you are using a 32-bit operating system, Oracle JRockit SDK is installed as part of the Oracle WebLogic installation (see Section 1.1.3, "Install Oracle WebLogic Server and Create the Middleware Home"). This is the JDK that the Configuration Wizard will use by default. If you want to invoke the Configuration Wizard with the Sun JDK, do the following prior to starting the Configuration Wizard:
Set the JAVA_HOME environment variable to the location of the Sun JDK. For example, you can set it to the Sun JDK that was installed with Oracle WebLogic Server in the MW_HOME/jdk160_14_R27.6.4-18 (on UNIX operating systems) or MW_HOME\jdk160_14_R27.6.4-18 (on Windows operating systems) directory.
Set the JAVA_VENDOR environment variable to "Sun."
To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:
On UNIX operating systems:
./config.sh -log=log_filename
On Windows operating systems:
config.cmd -log=log_filename
If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the MW_HOME/oracle_common/common/bin (on UNIX operating systems) or MW_HOME\oracle_common\common\bin (on Windows operating systems) directory.
Follow the instructions in Table 2-1 to create a new WebLogic domain for Application Developer.
Note:
For more information about WebLogic Server domains, refer to "WebLogic Server Domain" in Oracle Fusion Middleware Installation Planning Guide.If you need additional help with any of the configuration screens, refer to Appendix B, "Application Developer Configuration Screens" or click Help at the bottom of each screen to access the online help for that screen.
Table 2-1 Configuration Flow for Creating a New Domain
| No. | Screen | Description and Action Required |
|---|---|---|
|
1 |
Select Create a new WebLogic Domain. Click Next to continue. |
|
|
2 |
Select components you want to create in your domain. Click Next to continue. |
|
|
3 |
Specify the name and location for the new domain. Click Next to continue. |
|
|
4 |
Specify a user and password for the Administrator role. Click Next to continue. |
|
|
5 |
Select the WebLogic domain startup mode and the JDK to be used for the domain. Click Next to continue. |
|
|
6 |
This screen only appears if you selected Oracle WSM Policy Manager on the Select Domain Source Screen. If you did not, skip to the Select Optional Configuration Screen. Configure the schema owner and password for each component schema listed on this screen. Changes to any of the fields on this screen are applied to all selected component schema in the table. For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port). If, for example, you hare a different password for each schema, then you must select each schema individually and specify the password for the selected schema only. Click Next to continue. |
|
|
7 |
Test and verify the connections to your component schema. Click Next to continue. |
|
|
8 |
Select the category or categories for which you want to make additional configuration changes:
If you choose not to select anything on this screen, skip to the Configuration Summary Screen. Click Next to continue. |
|
|
9 |
Review the contents of your domain. Click Create to continue. |
|
|
10 |
Click Done when finished. |
While creating your WebLogic domain, if you chose not to configure all of the components on the Select Domain Source Screen, you can add these components at a later date by extending your domain. If this is a first time installation or you do not want to add more components, you can skip this section and move to the next section.
Note:
Before proceeding, make sure that schemas exist in your database for the components you are configuring when you extend the domain. For example, if you are planning to extend the domain and configure Oracle WSM Policy Manager, then make sure the required schema for this component (MDS) exists in your Oracle database before you continue.Follow the instructions in Table 2-2 to extend an existing domain.
Table 2-2 Configuration Flow for Extending an Existing Domain
| No. | Screen | Description and Action Required |
|---|---|---|
|
1 |
Select Extend an existing WebLogic Domain. Click Next to continue. |
|
|
2 |
Select the WebLogic directory to which you want to add your applications and services. Click Next to continue. |
|
|
3 |
Select the components with which you want to extend this domain. Click Next to continue. |
|
|
4 |
This screen only appears if you selected Oracle WSM Policy Manager on the Select Extension Source Screen. If you did not, skip to the Select Optional Configuration Screen. Configure the schema owner and password for each component schema listed on this screen. Changes to any of the fields on this screen are applied to all selected component schema in the table. For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port). If, for example, you hare a different password for each schema, then you must select each schema individually and specify the password for the selected schema only. Click Next to continue. |
|
|
5 |
Test and verify the connections to your component schema. Click Next to continue. |
|
|
6 |
Select the category or categories for which you want to make additional configuration changes:
If you choose not to select anything on this screen, skip to the Configuration Summary Screen. Click Next to continue. |
|
|
7 |
Review the contents of your domain. Click Extend to continue. |
|
|
8 |
Click Done when finished. |
The Select Optional Configuration Screen gives you the following optional configuration options:
If you select Administration Server on the Select Optional Configuration Screen, you will see the Configure Administration Server Screen. This screen enables you to customize your Administration Server settings, such as the server name, port number, and secure connection settings.
If you select Managed Servers, Clusters, and Machines on the Select Optional Configuration Screen, you will see the screens described in Table 2-3:
Table 2-3 Managed Servers, Clusters, and Machines Advanced Settings Screens
| No. | Screen | Description and Action Required |
|---|---|---|
|
1 |
Add new managed servers, or edit and delete existing managed servers. Click Next to continue. |
|
|
2 |
Create clusters if you are installing in a high availability environment. For more information, refer to Oracle Fusion Middleware High Availability Guide. Click Next to continue. |
|
|
3 |
Assign your managed servers to a cluster in your domain. Click Next to continue. |
|
|
4 |
Select whether or not you want a configure an HTTP proxy server for your cluster. This screen only appears if you have configured a managed server outside of a cluster. Click Next to continue. |
|
|
5 |
Configure the machines that will host the managed servers. Click Next to continue. |
|
|
6 |
Assign each managed server to the machine on which it runs. Click Next to continue. |
If you select Deployments and Services on the Select Optional Configuration Screen, you will see the screens described in Table 2-4.
The Configuration Wizard automatically takes care of all necessary deployment and services targeting. You should not have to change anything on these screens unless specifically directed to do so.
If you select JMS File Store on the Select Optional Configuration Screen, you will see the Configure JMS File Stores Screen. This screen enables you to configure the names, location, and write policy for your file stores.
If you select RDBMS Security Store on the Select Optional Configuration Screen, you will see the Configure RDBMS Security Store Database Screen. This screen enables you to configure an external relational database management system (RDBMS) as a data store for various security providers.
Java Required Files (JRF) consists of those components not included in the Oracle WebLogic Server installation and that provide common functionality for Oracle business applications and application frameworks.
JRF consists of a number of independently developed libraries and applications that are deployed into a common location. The components that are considered part of Java Required Files include: Oracle Application Development Framework, Oracle Fusion Middleware Audit Framework, Dynamic Monitoring Service, Infrastructure Security, Java Object Cache, Oracle Platform Security Services, logging, MDS, Oracle Web Services, and Oracle Web Services Manager.
You must apply JRF to a Managed Server or cluster in certain circumstances.You can only apply JRF to Managed Servers that are in a domain in which JRF was configured. That is, you must have selected Oracle JRF in the Configuration Wizard when you created or extended the domain.
For more information, see "Applying Java Required Files to a Managed Server or Cluster" in Oracle Fusion Middleware Administrator's Guide.
To get your deployments up and running, you must start the Administration Server by running the startWebLogic.sh (on UNIX operating systems) or startWebLogic.cmd (on Windows operating systems) script in the directory where you created your new domain.
On UNIX systems:
MW_HOME/user_projects/domains/domain_name/startWebLogic.sh
On Windows systems:
MW_HOME\user_projects\domains\domain_name\startWebLogic.cmd
You entered the domain name and location on the Specify Domain Name and Location Screen in the Configuration Wizard.
To verify the installation, start your browser and enter the following URLs:
To access the Administration Server console:
http://host:admin_server_port/console
If you configured your Administration Server to accept SSL connection, use the following URL to access the Administration Server console in secure mode:
https://host:secure_admin_server_port/console
http://host:admin_server_port/em