B Oracle Service Bus Deployment Resources

This section describes Oracle Service Bus deployment resources that are added to your domain when you extend your domain with the Oracle Service Bus domain extension template.

The Oracle Service Bus Administration Console and the UDDI manager run on the Admin Server. Therefore, you must run an Admin Server to manage Oracle Service Bus and to facilitate publishing and importing to and from a UDDI registry.

B.1 Oracle Service Bus Domain Extension Template

Using the Oracle Fusion Middleware Configuration Wizard or WLST, you can easily extend a base Oracle WebLogic Server domain to create an Oracle Service Bus domain. You accomplish this by adding the resources and services provided in the Oracle Service Bus extension template to a base Oracle WebLogic Server domain.

Note:

Using the Oracle Fusion Middleware Configuration Wizard in graphical mode, you can easily create a new Oracle Service Bus domain by checking the Oracle Service Bus check box in the Select Domain Source window. The result is the same as creating a base Oracle WebLogic Server domain first and then extending that domain with the Oracle Service Bus extension template. For more information about the templates required to create an Oracle Service Bus domain, see "Relationships Between Templates" in the Oracle Fusion Middleware Domain Template Reference.

B.1.1 Generated Domain Output

The following table defines the default directory structure and files generated after applying the Oracle Service Bus extension template to a base Oracle WebLogic Server domain. Unless otherwise specified, by default, the Oracle Fusion Middleware Configuration Wizard creates the domain in the MW_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table B-1 Your Domain After Applying the Oracle Service Bus Extension Template

Directory	Files	Description
user_projects\domains\your_domain\	fileRealm.properties	File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
user_projects\domains\your_domain\	derby.ini	File containing initialization information for an Apache Derby JDBC database.
user_projects\domains\your_domain\	startWebLogic.cmd startWebLogic.sh	Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
user_projects\domains\your_domain\	URLs.dat	File containing the URL for the JDBC database.
user_projects\domains\your_domain\	alsbdebug.xml configfwkdebug.xml	Files containing debug parameters for the domain. The default setting for all the parameters is false.
autodeploy\	readme.txt	File providing information about the directory, which initially serves as a placeholder for automatic deployments.
bin\	setDomainEnv.cmd setDomainEnv.sh	Scripts used to set up the development environment on Windows and UNIX systems, respectively.
bin\	startManagedWebLogic.cmd startManagedWebLogic.sh	Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
bin\	startDerbyConsole.cmd startDerbyConsole.sh	Scripts used to start the Apache Derby console on Windows and UNIX systems, respectively.
bin\	startWebLogic.cmd startWebLogic.sh	Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
bin\	stopManagedWebLogic.cmd stopManagedWebLogic.sh	Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.
bin\	stopWebLogic.cmd stopWebLogic.sh	Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
config\	config.xml	File containing the configuration information used by the Administration Server.
config\deployments\	readme.txt	File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."
config\diagnostics\	readme.txt	File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
config\jdbc\	readme.txt	File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
config\jdbc\	wlsbjmsrpDataSource-jdbc.xml	Global non-XA JDBC data source module for the Oracle Service Bus domain.
config\jms\	readme.txt	File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
config\jms\	wseejmsmodule-jms.xml	Configuration file containing JMS resources for Web Services Reliable Messaging (WS-RM).
config\jms\	xbusResources-jms.xml	Global JMS module for the Oracle Service Bus domain.
config\lib\	readme.txt	File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
config\nodemanager\	nm_password.properties	File containing Node Manager password property values.
config\security\	readme.txt	File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
config\startup\	readme.txt	File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
console-ext\	readme.txt	File providing information about the directory, which initially serves as a placeholder for custom extensions to the Oracle WebLogic Server Administration Console.
init-info\	domain-info.xml	File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
init-info\	security.xml	File used for creating user groups and roles that establish identity and access to domain resources.
init-info\	startscript.xml	File used to create the `.cmd` and `.sh` files that are placed into the domain's root and `bin` directories.
init-info\	tokenValue.properties	File that contains the actual values to substitute for the tokens specified in the start scripts.
lib\	readme.txt	File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
rmfilestore\	none	Directory serving as a disk-based file store to store persistent messages and durable subscribers.
security\	DefaultAuthenticatorInit.ldift DefaultAuthorizerInit.ldift DefaultRoleMapperInit.ldift XACMLAuthorizerInit.ldift XACMLRoleMapperInit.ldift	Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper).
security\	SerializedSystemIni.dat	File containing encrypted security information.
servers\AdminServer\security\	boot.properties	File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode. This file enables you to bypass the prompt for user name and password during a server's startup cycle.