The Configuration Wizard helps and simplifies the task of creating the needed WebLogic Server domain and configuring Oracle Forms and Reports.

1. Run the Configuration Wizard using config.sh (config.cmd on Windows) located in the ORACLE_HOME/oracle_common/common/bin directory.
2. Work your way through the screens described in Table 2-4.

   Table 2-4 Configuration Wizard Screens

   Screen	Description
   Create Domain	Choose Create a new domain, then type the desired domain home path. Note: It is recommended that the domain home not reside within the Oracle Home. Therefore, it is further recommended that "Oracle_Home" be removed from the default value or use a completely different location other than the one presented by default.
   Templates	Choose Create Domain Using Product Templates. In the Available Templates box, select the desired components. For example, to configure Oracle Forms, select the template named "Oracle Forms – 14.1.2.0.0 [forms]". Do similar to choose for other desired components (such as Oracle Reports). Note: Any dependent templates are automatically selected. Dependent templates cannot be deselected. Commonly used templates: Oracle Forms Application Deployment Services (FADS) Oracle Forms Oracle Reports Application Oracle Reports Tools Oracle Reports Server Oracle Reports Bridge Oracle HTTP Server Note: Refer to those individual component’s documentation for more details.
   Application Location	As mentioned for the domain location, it is recommended that the Application location not reside within the Oracle Home. Remove "Oracle_Home" from the default path or use a completely different location other than the one presented by default.
   Administrator Account	Type in the desired WebLogic Domain administration user name and password. This information is needed to access Fusion Middleware Control and for starting and stopping servers on the command line. It will also be used for accessing other services like Forms Application Deployment Services (if selected in Templates) and others.
   Domain Mode and JDK	For Domain Mode, select either Development or Production. To ensure the highest degree of security, selecting Production is recommended. If Production mode is selected, Secure Mode is also selected by default. This mode enables the use of SSL/TLS using a provided demo/example TLS certificate. However, that certificate should be replaced with a more appropriate certificate that is provided by a trusted and known certificate authority. Disabling secure mode is not recommended but can be helpful— for example in test environments where sensitive data is not accessed. Enable or disable the desired port types. For secure mode, SSL ports are enabled by default. The default JDK selection is appropriate for most configurations unless you need to use a different version the JDK than the one used to perform the installation.
   Database Configuration Type	The default selections are appropriate for most cases. Enter the RCU DB host name, service name, port, schema owner, and schema password. Then click Get RCU Configuration. Note: The schema name consists of the prefix value you provided when RCU was run to create the infrastructure schemas followed by “_STB”. For example, PROD_STB. You must include _STB when entering the value in the schema name field. Verify that there is a success message in the Connection Result Log panel. If there is no success message, check the database entries made in this step, then retry.
   JDBC Component Schema	This step assumes each repository schema uses the same password. If not, type in the correct schema passwords as needed.
   JDBC Component Schema Test	Testing begins automatically when this screen is displayed. If not, click Test Selected Connections. If there are any failures, carefully review the Result Log field, make corrections, then try again.
   Advanced Configuration	Which boxes need to be selected on this screen depends on which templates were selected in a previous step. In most cases you will need to select these templates: Administration Server Node Manager Topology System Components Depending on the level of customization desired, other selections may be needed. The following four screens are displayed if you selected the entries recommended here.
   Administration Server	In most cases, the default values should be appropriate. If you need to change the port numbers, use caution that you don't change a port to one that is already in use. Note: If Forms Application Deployment Services (FADS) was selected for inclusion in this domain, click the Server Groups poplist and select WSMPM-MAN-SVR.
   Node Manager	Provide a Node Manager user name and password. This will be needed to start and stop managed servers and components on the command line.
   Managed Servers	In most cases, the default values should be appropriate. If you need to change the port numbers, use caution that you don't change a port to one that is already in use. If you add managed servers, be sure to properly add them to the appropriate Server Group(s). Verify that each managed server includes the Server Group associated with that server (for example FORMS-MAN-SVR for WLS_FORMS) and JRF-MAN-SVR. Note: JRF-MAN-SVR may not be automatically selected. If it is not, add it by checking the JRF-MAN-SVR box in the Server Groups list then continue.
   Clusters	In most cases, all the default values should be appropriate. However, you can add additional clusters here if required.
   Server Templates	In most cases, the default values should be appropriate.
   Dynamic Servers	In most cases, the default values should be appropriate.
   Assign Severs to Cluster	Verify that servers are appropriately assigned to the desired cluster. In most cases, the default values should be appropriate. If not, use the left and right buttons to move the servers to the desired cluster(s).
   Coherence Clusters	In most cases, the default values should be appropriate.
   Machines	Use this screen to override the machine name or add additional machine names for extended domain scenarios (such as adding remote Forms nodes). In most cases, the default values should be appropriate.
   Assign Servers to Machines	Move the AdminServer and any additional servers you may have previously created to the AdminServerMachine by selecting the AdminServerMachine node on the right, then clicking the top button for each server that needs to be moved. All entries should now appear in the right-side pane.
   System Components	In most cases, the default values should be appropriate. If you added the HTTP Server (OHS) earlier, click +Add. In the System Component field, provide a name for the OHS component (such as ohs1), then select OHS from the Component Type list.
   OHS Server	In most cases, the default values should be appropriate. If it's desirable to have a fully-qualified server.domain instead of "localhost", make the appropriate changes.
   Assign System Components to Machines	Verify that all system components on the left are assigned to the appropriate machine on the right. Select SystemComponent on left and AdminServerMachine on right. Then click the right arrow to move all left side components to the right.
   Configuration Summary	The Configuration Summary screen indicates what will be contained in the domain once created. If everything looks right, click Create.
   Configuration Progress	This screen shows the progress of the domain creation. The process may take some time. How long it takes depends on many factors, including machine and network performance. If any errors occur, they will be presented. Unfortunately, some errors may not be correctable without deleting the Repository Schemas and starting over. Be careful not to interrupt this process or the connection between this environment and the database. When the domain is successfully created, click Finish to close the wizard.

3. Start the servers (Node Manager, Admin Server, and managed servers).
   • On Unix/Linux platforms, the shell used to start these servers the first time, must be the installation owner's (for example, oracle).
   • On Microsoft Windows, the DOS shell used to start these servers the first time must have Administrator permissions.

     To enable an Administrator shell session, right-click the Command Prompt shortcut and select Run as Administrator. The shell that opens will indicate that it has Administrator privileges in its title bar.