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.
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.
Note: | Using the Configuration Wizard in graphical mode, you can easily create a new AquaLogic Service Bus domain by checking the AquaLogic Service Bus check box in the Select Domain Source window. The result is the same as creating a base WebLogic Server domain first and then extending that domain with the AquaLogic Service Bus extension template. For more information about the templates required to create an AquaLogic Service Bus domain, see Relationships Between Templates in the BEA Domain Template Reference. |
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.
File containing the configuration information used by the Administration Server. For more information, see
Domain Configuration Files in Understanding Domain Configuration.
|
||||
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.
|
||||
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.
|
The following table identifies the resources and services configured in a domain extended with the AquaLogic Service Bus extension template.
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.
|
||
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.
|
||