|
|
Before you can develop and run Oracle Service Bus-based applications, you must first create an Oracle Service Bus domain on an Oracle WebLogic Server. The Configuration Wizard guides you through the process of creating a new domain quickly and easily, by selecting the product components you want to include in your domain, or by using domain templates.
The following topics describe the steps required to create a new Oracle Service Bus domain using the Configuration Wizard:
The Welcome window prompts you to choose whether you want to create a new domain or extend an existing one.
Add product component functionality or support for additional applications and services to an existing domain. Begin by selecting the directory of the domain that you want to update. Then specify the product components you want to add, or identify the extension template you want to use for adding applications and services. You then have the option of customizing the JDBC connections to your database and the JMS file store, if defined. To learn more, see Extending WebLogic Domains.
|
The Select a Domain Source window prompts you to select the source from which to create the domain. You can select the product components to include in your domain, or select a custom template on which to base your domain.
Choose one of the following options for selecting the source for your domain:
To use this option, select the check boxes associated with the components you want to include, and click Next.
You can select the following product components in the Select a Domain Source window as displayed in Figure 4-1. For more information about selecting different products from the list of products and relation between them, see http://download.oracle.com/docs/cd/E12840_01/common/docs103/tempref/tempref.html.
The WebLogic Server is selected by default.
To use this option, manually enter the full pathname to the template in the Template location field and click Next, or click Browse to navigate to the directory containing the desired template. Select the domain template that contains the settings you want to use as the basis for your domain.
| Note: | While using the Configuration Wizard or Oracle WebLogic Scripting Tool Off-line to create or extend a clustered domain with a template that has applications containing application-scoped JDBC and/or JMS resources, you may need to perform additional steps (after the domain is created or extended) to make sure that the application and its application-scoped resources are targeted and deployed properly in a clustered environment. For more information on the targeting and deployment of application-scoped modules, see “Deploying Applications and Modules with weblogic.deployer” in Deploying Applications to WebLogic Server at the following URL: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/deployment/deploy.html. |
The Configure Administrator Username and Password window prompts you to specify a username and password to be used for starting the Administration Server.
To configure an administrator username and password:
Do not use commas or any characters in the following comma-separated list: \t, < >, #, |, &, ?, ( ), { }. User names are case sensitive.
| Note: | Do not use password = weblogic in a production environment. |
The Configure Server Start Mode and JDK window prompts you to specify the:
Specify the startup mode for your domain as shown in the following table.
The following table describes the differences between development and production modes in terms of key functions.
You can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL.
For more information about managing security, see "Configuring SSL" in Securing WebLogic Server at the following URL: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/ssl.html
|
||
WebLogic Server instances can automatically deploy and update applications that reside in the domain_name/autodeploy directory (where domain_name is the name of a domain).
For more information, see Deploying Applications to WebLogic Server at the following URL: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/deployment/deploy.html
|
||
The JDK Selection pane prompts you to select the J2SE Development Kit (JDK) for the startup mode you selected in the WebLogic Domain Startup Mode pane. The Configuration Wizard presents a list of the JDKs supplied by Oracle and installed with the product, including:
You can choose one of the JDKs supplied by Oracle or another JDK that you have installed on your system. If you select a JDK supplied by Oracle, the Configuration Wizard will create server startup scripts that invoke the JDK you select.
For more information about startup scripts, see WLS Performance and Tuning available at:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/perform/WLSTuning.html
Select only those JDKs that are supported on the platform you are using. For a list of the JDKs that are supported for a specific platform, see Supported Configurations available at the location:
http://edocs.bea.com/platform/suppconfigs/configs_al10gr3/osb10gr3/index.html
The default selection reflects the JDK that best meets the requirements of your environment, based on the platform on which you are installing the domain.
| Note: | If you plan to use the JRockit JDK in production mode, Oracle recommends that you develop and test your applications using Oracle JRockit early in your project cycle. For information about Oracle JRockit, see the Oracle JRockit JDK documentation at the following URL: |
| Note: | http://www.oracle.com/technology/software/products/jrockit/index.html |
| Note: | The Configuration Wizard does not configure the start scripts to use this type of JDK. You must change the start scripts manually. |
For information on changing the run-time mode after you have created a domain, see “Change to production mode” in the WebLogic Server Administration Console Online Help at http://download.oracle.com/docs/cd/E13222_01/wls/docs100/ConsoleHelp/taskhelp/domainconfig/ChangeRuntimeModes.html.
The Customize Environment and Services Settings window gives you the option to change the distribution of your domain across servers, clusters, and machines, and to modify existing JDBC and JMS file store settings.
If you choose not to customize any environment or services settings by accepting the default (No), you proceed directly to creating the domain.
The following topics summarize the settings you can change.
You can customize the environment of your domain as follows:
For more information, see Customizing the Environment and Customizing the Oracle Service Bus Environment.
If the domain source on which you are basing your domain contains a database configuration, you have the option to do the following:
If a JMS file store has been defined in the domain source, you can also change the file store definition.
For more information, see Customizing JDBC and JMS Settings in WebLogic Domains and Customizing JDBC and JMS Settings in Oracle Service Bus Domains.
The Create WebLogic Domain window prompts you to specify the name and pathname for the domain, and initiate its creation.
To create the WebLogic domain:
The domain directory can be located anywhere on your system. By default, it resides in BEA_HOME\user_projects\domains\domain, where BEA_HOME is the directory that contains the product installation, and domain is the name of the domain directory defined by the selected domain template.
| Note: | You cannot overwrite an existing domain. If a domain with the name you specify already exists in the selected location, you must either delete the existing domain, or specify a different name or location for this domain. |
The Creating Domain window is opened to display status messages during the domain creation process.
The Configuration Wizard stores the config.xml file and all other generated components in the domain directory that you specify.
The Creating Domain window displays status messages during the domain creation process. When the process is complete, the new domain is ready for use.
|
