AquaLogic Service Bus Deployment Resources

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

The ALSB Console and the UDDI manager run on the administration server. Therefore, you must run an administration server to manage ALSB and to facilitate publishing and importing to and from a UDDI registry.

ALSB Domain Extension Template

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

Generated Domain Output

The following table defines the default directory structure and files generated after applying the AquaLogic Service Bus extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_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.

Directory

File

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.

pointbase.ini

File containing initialization information for a PointBase JDBC database.

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

URLs.dat

File containing the URL for the JDBC database.

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.

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

startPointBaseConsole.cmd

startPointBaseConsole.sh

Scripts used to start the PointBase console on Windows and UNIX systems, respectively.

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

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. For more information, see Domain Configuration Files in Understanding Domain Configuration.

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).

wlsbjmsrpDataSource-jdbc.xml

Global non-XA JDBC data source module for the AquaLogic 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).

wseejmsmodule-jms.xml

Configuration file containing JMS resources for Web Services Reliable Messaging (WS-RM).

xbusResources-jms.xml

Global JMS module for the AquaLogic 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 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.

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

startscript.xml

File used to create the *.cmd and *.sh files that are placed into the domain’s root and bin directories.

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\

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). For more information, see WebLogic Security Providers in Understanding WebLogic Security at http://e-docs.bea.com/wls/docs100/secintro/archtect.html#archtect_0111.

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. For more information, see “Provide User Credentials to Start and Stop Servers” in Starting and Stopping Servers in Managing Server Startup and Shutdown at

http://edocs.bea.com/wls/docs100/server_start/overview.html.

Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the AquaLogic Service Bus extension template.

Table B-2 Resources Configured in an AquaLogic Service Bus Domain
Resource Type	Name	Extension Result / Description
Administration Server	AdminServer	Uses the Administration Server provided in the base WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in the extension template is `xbusServer`.
Application Deployments	ALDSP Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	ALSB Cluster Singleton Marker Application	Adds the application and targets it to the Administration Server, `AdminServer`. Internal application.
	ALSB Domain Singleton Marker Application	Adds the application and targets it to the Administration Server, `AdminServer`. Internal application.
	ALSB Framework Starter Application	Adds the application and targets it to the Administration Server, `AdminServer`. Internal application that starts various alsb frameworks.
	ALSB Logging	Adds the application and targets it to the Administration Server, `AdminServer`.
	ALSB Publish	Adds the application and targets it to the Administration Server, `AdminServer`.
	ALSB Resource	Adds the application and targets it to the Administration Server, `AdminServer`.
	ALSB Routing	Adds the application and targets it to the Administration Server, `AdminServer`.
	ALSB Subscription Listener	Adds the application and targets it to the Administration Server, `AdminServer`. UDDI subscription listener.
	ALSB Test Framework	Adds the application and targets it to the Administration Server, `AdminServer`. In clusters, the Test Framework is deployed on the admin server and on each managed server by default. It must be deployed on the admin server if you want to test XQueries from the XQuery builders. To use the test console, a cluster address must be configured. The cluster address must contain at least one of the managed servers where the Test Framework EJB is deployed.
	ALSB Transform	Adds the application and targets it to the Administration Server, `AdminServer`.
	ALSB UDDI Manager	Adds the application and targets it to the Administration Server, `AdminServer`.
	EJB Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	Email Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	File Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	Flow Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`. For the Split-Join feature.
	Ftp Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	JMS Reporting Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	JPD Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	Message Reporting Purger	Adds the application and targets it to the Administration Server, `AdminServer`. The AquaLogic Service Bus Message Reporting Purger runs as a singleton instance on one of the managed servers in the cluster. The Message Reporting Purger queues the purging requests and processes them one by one. For failover information in the event the managed server that hosts the Message Reporting Purger and the `wli.reporting.purge.queue` fails, see Message Reporting Purger.
	MQ Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	SB Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	ServiceBus_Console	Adds the application and targets it to the Administration Server, `AdminServer`.
	SFTP Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	Tuxedo Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`.
	WS Transport Provider	Adds the application and targets it to the Administration Server, `AdminServer`. Transport provider for WS-RM.
	WS Transport Async Application	Adds the application and targets it to the Administration Server, `AdminServer`. Internal application.
	XBus Kernel	Adds the application and targets it to the Administration Server, `AdminServer`. The application includes the `/` (slash) WAR and `kerneladmin` EJB modules, which are also targeted to `AdminServer`.
File Stores	FileStore	Adds the file store to be used as the persistent store for the JMS server, `wlsbJMSServer`.
JDBC Data Source	wlsbjmsrpDataSource	Identifies the JDBC data source as a `wlsbjmsrpDataSource` system resource.
JDBC System Resources	wlsbjmsrpDataSource	Identifies the JDBC data source and connection pool setup to be used for JDBC system resources and targets the resources to the Administration Server, `AdminServer`.
JMS Connection Factories	weblogic.wlsb.jms.transporttask.QueueConnectionFactory	Adds the JMS connection factory as a `jmsResources` system resource and targets it to the Administration Server, `AdminServer`.
	wli.reporting.jmsprovider.NonXAConnectionFactory	Adds the JMS connection factory as a `jmsResources` system resource and targets it to the Administration Server, `AdminServer`.
	wli.reporting.jmsprovider.XAConnectionFactory	Adds the JMS connection factory as a `jmsResources` system resource and targets it to the Administration Server, `AdminServer`.
JMS Queues	QueueIn	Adds the JMS queue to the JMS server, `wlsbJMSServer`.
	wlsb.internal.transport.task.queue.email	Adds the JMS queue to the JMS server, `wlsbJMSServer`.
	wlsb.internal.transport.task.queue.file	Adds the JMS queue to the JMS server, `wlsbJMSServer`.
	wlsb.internal.transport.task.queue.ftp	Adds the JMS queue to the JMS server, `wlsbJMSServer`.
	wlsb.internal.transport.task.queue.sftp	Adds the JMS queue to the JMS server, `wlsbJMSServer`.
	wli.reporting.jmsprovider.queue	Adds the JMS queue to the JMS server, `wlsbJMSServer`.
	wli.reporting.jmsprovider_error.queue	Adds the JMS queue to the JMS server, `wlsbJMSServer`.
	wli.reporting.purge.queue	Adds the JMS queue to the JMS server, `wlsbJMSServer`.
JMS Servers	wlsbJMSServer	Adds the JMS server as a `jmsResources` system resource and targets it to the Administration Server, `AdminServer`.
JMS System Resources	jmsResources	Identifies the JMS servers, connection factories, and queues to be used for JMS system resources, and targets the resources to the Administration Server, `AdminServer`.
Security realm	myrealm	Uses the security realm provided by the base WebLogic Server domain.
Web Services Security	__SERVICE_BUS_INBOUND_WEB_SERVICE_SECURITY_MBEAN__	Adds the inbound Web Services security configuration, including the `default_x509_handler` and `default_ut_handler` token handlers and the `ServiceBusProviderUNT` and `ServiceBusProviderX509` credential providers.
Web Services Security	__SERVICE_BUS_OUTBOUND_WEB_SERVICE_SECURITY_MBEAN__	Adds the outbound Web Services security configuration, including the `default_x509_handler` and `default_ut_handler` token handlers and the `ServiceBusProviderUNT`, `ServiceBusProviderX509`, `and alsb_saml_credential_provider` credential providers.

Deployment Guide

AquaLogic Service Bus Deployment Resources

ALSB Domain Extension Template

Generated Domain Output

Resources and Services Configured