Creating WebLogic Domains Using the Configuration Wizard

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

How Do I...?

This section provides examples for specific tasks using the Configuration Wizard. The topics include:

How Do I: Create a WebLogic Integration Domain Using an Enterprise-Quality Database?

The following example explains the procedure to create a new Oracle WebLogic Integration domain that uses a database other than the default PointBase database.

  1. Start the Configuration Wizard in graphical mode.
    • On Windows:

      • Start > Programs > Oracle WebLogic > WebLogic Server 10gR3 > Tools > Configuration Wizard

    • On UNIX:

      • Go to the /common/bin subdirectory of the product installation directory. For example: cd $BEA_HOME/wlserver_10.3/common/bin

      Enter sh config.sh

  2. In the Welcome window, select Create a new WebLogic domain, and click Next.
  3. In the Select a Domain Source window:
    1. Select Generate a domain configured automatically to support the following products.
    2. Select the WebLogic Integration check box.
      3. Note: The WebLogic Server check box is selected by default since it is a prerequisite for all Oracle WebLogic domains.
    3. Click Next.
  4. In the Configure Administrator Username and Password window, enter a valid username and password, and click Next. This username is used to boot the Administration Server and connect to it.
  5. In the Configure Server Start Mode and JDK window, specify the Domain startup mode, JDBC and JDK, click Next, and for more information, see Creating a WebLogic Domain.
  6. In the Customize Environment and Services Settings window, select Yes to modify JDBC Data Source Configurations to specify a non-PointBase database, and click Next.
  7. In the Configure the Administration Server window, define the configuration information for the Administration server, and click Next. For more information, see Configuring the Administration Server.
  8. In the Configure Managed Servers window, define the configuration information for one or more managed servers, and click Next. For more information, see Configuring Managed Servers.
  9. In the Configure Machines window, define the configuration information for machine or hosts in the domain, and click Next. For more information, see Configuring Machines.
  10. In the Configure JDBC Data Sources window, modify the configuration information for each data source to point to the desired Database type and driver.
    11. Note: Always define p13nDataSource and cgDataSource-nonXA with a non-XA driver. For example, when configuring a domain for Oracle, use Oracle Driver (Type 4) with these data sources.
    Note: For every other data source, a tab is displayed in the Configure JDBC Data Sources panel for Database Type and Driver configuration. The remaining data sources can be defined with either an XA or non-XA Driver, as required. When each data source is configured, click Test Connections to display the Test Data Source Connections window. Test each database source to verify database connectivity. Go back to the Configure JDBC Data Sources window to check and correct any database connectivity issue before proceeding.
    Note: Ensure that the database to which you want to test the connection is running.

    Click Next to proceed to the Run Database Scripts window.

  11. In the Run Database Scripts window, select the Log File check box, and click Run Scripts to create WLI Business Process, P13N, and Worklist Data Objects.
    12. Note: In the Results pane, verify that Database Load Successful is returned for each Run Script execution. Otherwise, correct the problem before proceeding.
  12. In the Configure JMS File Store window, enter any JMS File Store information for the domain, and click Next. For more information, see Configure JMS File Stores.
  13. In the Review WebLogic Domain window, verify the contents of the domain, and click Next. For more information, see Review the Domain Settings and Create the Domain.

In the Create WebLogic Domain window, type a name and location for your new Oracle WebLogic Integration domain, click Create. Once the domain is created, the server for Oracle WebLogic Integration is ready to be started.

How Do I: Create a WebLogic Portal Domain Using an Enterprise-Quality Database?

The following example explains the procedure to create a new Oracle WebLogic Portal domain that uses a database other than the default PointBase database. For additional information about configuring an Enterprise-Quality Database, see the WebLogic Portal Database Administration Guide at the following URL:

http://download.oracle.com/docs/cd/E13219_01/wlp/docs103/db/index.html

  1. Start the Configuration Wizard in graphical mode.
    • On Windows:

      • Start > Programs > Oracle WebLogic > WebLogic Server 10gR3 > Tools > Configuration Wizard

    • On UNIX:

      • Go to the /common/bin subdirectory of the product installation directory. For example: cd $BEA_HOME/wlserver_10.3/common/bin

      Enter sh config.sh

  2. In the Welcome window, select Create a new WebLogic domain, and click Next.
  3. In the Select a Domain Source window:
    1. Select Generate a domain configured automatically to support the following products.
    2. Select the WebLogic Portal check box.
      3. Note: The WebLogic Server check box is selected by default since it is a prerequisite for all Oracle WebLogic domains.
    3. Optionally, select the WebLogic Portal GroupSpace Framework and WebLogic Portal GroupSpace Application check boxes to include database resources required for a GroupSpace Community and a pre-configured GroupSpace application, respectively. For more information, see the WebLogic Portal GroupSpace Guide at the following URL:
      http://download.oracle.com/docs/cd/E13219_01/wlp/docs103/groupspace/index.html
      4. Note: The WebLogic Portal checkbox is selected by default since it is a prerequisite for WebLogic Portal GroupSpace.
    4. Click Next.
  4. In the Configure Administrator Username and Password window, enter a valid username and password, and click Next. This username is used to boot the Administration Server and connect to it.
  5. In the Configure Server Start Mode and JDK window, specify the Domain startup mode, JDBC and JDK, click Next, and for more information, see Creating a WebLogic Domain.
  6. In the Customize Environment and Services Settings window, select Yes to modify JDBC Data Source Configurations to specify a non-PointBase database, and click Next.
  7. In the Configure the Administration Server window, define the configuration information for the Administration server, and click Next. For more information, see Configuring the Administration Server.
  8. In the Configure Managed Servers window, define the configuration information for one or more managed servers, and click Next. For more information, see Configuring Managed Servers.
  9. In the Configure Machines window, define the configuration information for machine or hosts in the domain, and click Next. For more information, see Configuring Machines.
  10. In the Configure JDBC Data Sources window, modify the configuration information for each data source to point to the desired Database type and driver. For a list of supported databases and drivers for Oracle WebLogic Portal, see Supported Database Configurations at the following URL:
    http://download.oracle.com/docs/cd/E12840_01/platform/configs_osb10gr3/osb10gr3/index.html

    11. Please keep the following considerations in mind:

    • Each data source for Oracle WebLogic Portal is described in BEA_HOME/portal/db/jdbc/README.txt. This Readme file includes additional important information about database specific data source settings and XA JDBC Driver usage. It also describes a process for switching a default PointBase domain to a domain using an Enterprise Quality Database, without using the Configuration Wizard guide to modify each data source.
    • For the MySQL Database:

      • The MySQL JDBC driver is not fully XA compatible, therefore Oracle WebLogic Portal does not support using com.mysql.jdbc.jdbc2.optional.MysqlXADataSource. Data sources that require XA, and those that are XA capable, should use the com.myself.jdbc.Driver with the global-transactions-protocol LoggingLastResource instead.

    • For Database Types other than MySQL:

      • Always define portalDataSourceAlwaysXA with an XA driver. For example, when configuring a domain for Oracle, use Oracle Driver (Type 4 XA).

      Always define p13nDataSource and cgDataSource-nonXA with a non-XA driver. For example, when configuring a domain for Oracle, use Oracle Driver (Type 4) with these data sources.

      For every other data source, a tab is displayed in the Configure JDBC Data Sources panel for Database Type and Driver configuration. The remaining data sources can be defined with either an XA or non-XA Driver, as required. When each data source is configured, click Test Connections to display the Test Data Source Connections window. Test each database source to verify database connectivity. Go back to the Configure JDBC Data Sources window to check and correct any database connectivity issue before proceeding.

      Note: If you selected the WebLogic Portal GroupSpace Framework check box in step 3, and you want to use a database other than PointBase for the GroupSpace Database, appsGroupSpaceDataSource will require data source configuration. For example, to use an Oracle database with the WebLogic Portal GroupSpace Framework configure appsGroupSpaceDataSource, to use Oracle Driver (Type 4) and specify a user name and password that is unique for WebLogic Groupspace. For more information, see the WebLogic Portal Database Administration Guide at the following URL:
      http://download.oracle.com/docs/cd/E12840_01/wlp/docs103/db/oracle.html#wp1070839
      Ensure that the database to which you want to test the connection is running.

      Click Next to proceed to the Run Database Scripts window.

  11. In the Run Database Scripts window, select the Log File check box, and then click Run Scripts to create both the P13N and Portal Database Objects.

    12. Also, if you selected WebLogic Portal GroupSpace Framework in Step 3, select the appsGroupSpaceDataSource in Available JDBC Data Sources, and then click Run Scripts to load the database objects for the WebLogic Portal GroupSpace Framework.

    Note: In the Results pane, verify that Database Load Successful is returned for each Run Script execution. Otherwise, correct the problem before proceeding.
  12. In the Configure JMS File Store window, enter any JMS File Store information for the domain, and click Next. For more information, see Configure JMS File Stores.
  13. In the Review WebLogic Domain window, verify the contents of the domain, and click Next. For more information, see Review the Domain Settings and Create the Domain.
  14. In the Create WebLogic Domain window, enter a name and location for your new WebLogic Portal domain, click Create. Once the domain is created, the server for WebLogic Portal is ready to be started.

How Do I: Create an Oracle Service Bus Domain Using an Enterprise-Quality Database?

The following example explains how to create a new Oracle Service Bus domain that uses a database other than PointBase for your JMS Reporting Provider.

  1. Start the Configuration Wizard in graphical mode.
    • On Windows:

      • Start > Programs > Oracle WebLogic > WebLogic Server 10.3 > Tools > Configuration Wizard

    • On UNIX:

      • Go to the /common/bin subdirectory of the product installation directory. For example: cd $BEA_HOME/wlserver_10.3/common/bin

      Enter sh config.sh

  2. In the Welcome window, select Create a new WebLogic domain and click Next.
  3. In the Select a Domain Source window:
    1. Select Generate a domain configured automatically to support the following products.
    2. Select the Service Bus check box.

      3. Note that the WebLogic Server check box is selected by default since it is a prerequisite for all Oracle WebLogic domains.

    3. Click Next.
  4. In the Configure Administrator Username and Password window, enter a valid username and password, and click Next. This username is used to boot the Administration Server and connect to it.
  5. In the Configure Server Start Mode and JDK window, specify whether to start the server in development mode or production mode, and select which JDK to use. For more information, see Specify the Server Start Mode and JDK. Click Next.
  6. In the Customize Environment and Services Settings window, indicate whether you want to change the distribution of your domain across servers, clusters, and machines, or to modify existing JDBC and JMS file store services.

    7. The JMS Reporting Provider in the Service Bus template is preconfigured to use the PointBase database provided with your installation. In this example, we want to select a different database. Select Yes and click Next.

  7. In the Configure the Administration Server window, define the configuration information for the Administration Server, including:
    • Administration Server name
    • Listen address
    • Nonsecure and secure (optional) listen ports

      • Servers can be reached through the following URL: protocol://listen-address:listen-port

      For more information, see Configure the Administration Server.

      In this example, you can either accept the default values, or enter configuration information specific to your Administration Server.

      Click Next to proceed to the Configure Managed Servers window.

  8. In the Configure Managed Servers window, define the configuration information for one or more Managed Servers. For this example, you do not need to add Managed Servers.

    9. Click Next to proceed to the Configure Machines window.

  9. In the Configure Machines window, define the configuration information for the Windows and UNIX machines in the domain. If you intend to use Node Manager, you must create a machine configuration for each product installation that runs a Node Manager process. For this example, you do not need to configure a machine.

    10. Click Next to proceed to the Configure JDBC Data Sources window.

  10. In the Configure JDBC Data Sources window, you can modify the configuration information for data sources defined in the template. You can also test the connections to your database.

    11. The JMS Reporting Provider data source (wlsbjmsrpDataSource) is preconfigured to use the PointBase database. To use an alternate database, make the following edits in this window:

    • In the Database type field, select a supported database, such as Oracle, MS SQL, Sybase, or DB2.
    • In the Driver field, select a supported non-XA driver.
      • Note: For a list of the supported drivers, see “Supported Database Configurations” in Supported Configurations for Oracle Service Bus 10g Release 3 (10.3) at http://download.oracle.com/docs/cd/E12840_01/platform/configs_osb10gr3/osb10gr3/index.html.
    • Select the Supports global transactions and Logging last resource options.
    • Complete the remaining required fields as appropriate for your database.

      • When you have completed all the required fields in this window, click Test Connections to display the Test Data Source Connections window.

  11. In the Test Data Source Connections window, you can test the connection to the database for each of the data sources defined in your domain, using the JDBC URL defined for the database.
    12. Note: Make sure that the database to which you want to test the connection is running.

    To test the connection from the wlsbjmsrpDataSource data source to the database you specified, click Test. Verify that the test was successful, then click OK to return to the Configure JDBC Data Sources window.

    Click Next to proceed to the Run Database Scripts window.

  12. In the Run Database Scripts window, you set up the database content for each of the data sources defined in your domain using pre-existing SQL or database loading files.

    13. If you selected Development for the server start mode in Step 5, the database tables are created automatically when the JMS Reporting Provider is deployed.

    If you selected Production for the server start mode in Step 5, you must execute the database scripts to create the JMS Reporting Provider tables, as described below. To do so:

    1. In the Available JDBC Data Sources pane, select wlsbjmsrpDataSource.
    2. The Available Sql Files And Database Loading Options pane displays all the scripts available in the data source. Select the scripts to run, by checking or unchecking the check box associated with the scripts.
    3. Select the database version from the DB Version drop-down menu.
    4. To create a log file, select the check box associated with Log File. Specify the location of the log file. The default location of the log file is BEA_HOME\wlserver_10.3\common\lib\jdbc.log
      where: BEA_HOME is the directory containing the product installation.
    5. Click Run Scripts.

      6. To confirm that the tables were created successfully, review the results in the Results pane.

    6. Click Next.
  13. In the Configure JMS File Store window, you can modify JMS file stores that are configured in your domain.

    14. In this example, you do not need to modify the JMS file store definition.

    Click Next.

  14. In the Review WebLogic Domain window, review the detailed configuration settings of your domain before the Configuration Wizard creates the domain.

    15. The Domain Summary pane shows the Deployment view by default. By selecting different options from the Summary View drop-down list, you can see different views of the domain summary, for example, the Cluster view.

    Select an item in the Domain Summary pane on the left and review the associated details in the Details pane on the right. You can make limited adjustments by clicking Previous to return to a prior window.

    After reviewing the contents of your domain, click Next to go to the Create WebLogic Domain window.

  15. In the Create WebLogic Domain window, enter a name for the domain and specify a location for the domain directory.

    16. For example, you may want to name this servicebus_domain.

    By default, the domain is created in BEA_HOME\user_projects\domains\domain, where BEA_HOME is the directory that contains the product installation, and domain is the domain name that you specify (servicebus_domain in this example). Click Create.

  16. In the Creating Domain window, once the domain has been created, do one of the following:
    • If you are creating the domain on a Windows system and you want to start the server immediately, select the Start Admin Server check box and click Done.
    • Click Done.

  Back to Top       Previous  Next