1 About the Oracle Service Bus Installation
- Using the Standard Installation Topology as a Starting Point
The standard installation topology is a flexible topology that you can use as a starting point in production environments. - Understanding Insight Integration with Oracle Service Bus
You can configure an Oracle Real-Time Integration Business Insight (Insight) agent with Oracle Service Bus to collect metrics. - About Secondary Topologies
Secondary topologies include configurations with components that require additional installation or configuration steps on top of the standard topology. - Using This Document to Extend an Existing Domain
The procedures in this guide describe how to create a new domain. The assumption is that no other Oracle Fusion Middleware products are installed on your system.
1.1 Using the Standard Installation Topology as a Starting Point
The standard installation topology is a flexible topology that you can use as a starting point in production environments.
The information in this guide helps you to create a standard installation topology for Oracle Service Bus. If appropriate and required, you can later extend the standard installation topology to create a secure and highly available production environment (see Next Steps After Configuring the Domain).
The standard installation topology represents a sample topology for this product. It is not the only topology this product supports. For more information, see About the Standard Installation Topology in Planning an Installation of Oracle Fusion Middleware.
- About the Oracle Service Bus Standard Installation Topology
This topology represents a standard WebLogic Server domain that contains an Administration Server and one or more clusters containing one or more Managed Servers. - About Elements in the Standard Installation Topology Illustration
The standard installation topology typically includes common elements.
1.1.1 About the Oracle Service Bus Standard Installation Topology
This topology represents a standard WebLogic Server domain that contains an Administration Server and one or more clusters containing one or more Managed Servers.
The following figure shows the standard installation topology for Oracle Service Bus.
See Table 1-1 for information on elements of this topology.
For configuration instructions, see Configuring the Oracle Service Bus Domain.
1.1.2 About Elements in the Standard Installation Topology Illustration
The standard installation topology typically includes common elements.
The following table describes all elements of the topology illustration:
Table 1-1 Description of Elements in Standard Installation Topologies
| Element | Description and Links to Related Documentation |
|---|---|
| APPHOST | A standard term used in Oracle documentation to refer to the machine that hosts the application tier. |
| DBHOST | A standard term used in Oracle documentation to refer to the machine that hosts the database. |
| WebLogic Domain | A logically related group of Java components (in this case, the Administration Server, Managed Servers, and other related software components).
For more information, see What Is an Oracle WebLogic Server Domain? in Understanding Oracle Fusion Middleware. |
| Administration Server | Central control entity of a WebLogic domain. It maintains configuration objects for that domain and distributes configuration changes to Managed Servers.
For more information, see What Is the Administration Server? in Understanding Oracle Fusion Middleware. |
| Enterprise Manager | The Oracle Enterprise Manager Fusion Middleware Control is a primary tool used to manage a domain.
For more information, see Oracle Enterprise Manager Fusion Middleware Control in Understanding Oracle Fusion Middleware. |
| Cluster | A collection of multiple WebLogic Server instances running simultaneously and working together.
For more information, see Overview of Managed Servers and Managed Server Clusters in Understanding Oracle Fusion Middleware. |
| Machine | A logical representation of the computer that hosts one or more WebLogic Server instances (servers). Machines are also the logical glue between the Managed Servers and the Node Manager. In order to start or stop the Managed Servers using the Node Manager, associate the Managed Servers with a machine. |
| Managed Server | A host for your applications, application components, web services, and their associated resources.
For more information, see Overview of Managed Servers and Managed Server Clusters in Understanding Oracle Fusion Middleware. |
| Infrastructure | A collection of services that include the following:
|
1.2 Understanding Insight Integration with Oracle Service Bus
You can configure an Oracle Real-Time Integration Business Insight (Insight) agent with Oracle Service Bus to collect metrics.
Insight enables you to model, collect, and monitor business-level metrics using web-based dashboards and reports, without the need to modify your already-deployed integrations and applications. Insight is collocated with the BAM Managed Server. The business metrics are collected by Insight agents that are co-located with Oracle SOA Suite or Oracle Service Bus Managed Servers and made available to the central application, viewed using BAM dashboards and reports.
To include an Insight agent with Oracle Service Bus, you select the Insight Service Bus Agent template in the Configuration Wizard. See Selecting the Configuration Templates for Oracle Service Bus.
-
Getting Started with Oracle Real-Time Integration Business Insight
-
Understanding the Oracle Real-Time Integration Business Insight Standard Installation Topology in Installing and Configuring Oracle SOA Suite and Business Process Management
1.3 About Secondary Topologies
Secondary topologies include configurations with components that require additional installation or configuration steps on top of the standard topology.
This is a test of using a variable for an xref from a shared topic to a shared topic:
The main sections of this guide describe how to install and configure a standard installation topology. The secondary topologies contain several products that are not identified or included in the standard installation topologies.
For guidelines to install and configure secondary topologies, see Oracle Service Bus and Oracle Enterprise Scheduler Topology.
1.4 Using This Document to Extend an Existing Domain
The procedures in this guide describe how to create a new domain. The assumption is that no other Oracle Fusion Middleware products are installed on your system.
If you have installed and configured other Oracle Fusion Middleware products on your system (for example, Fusion Middleware Infrastructure, with a domain that is up and running), use the same instructions to extend your existing domain. If you choose extend an existing domain, read Installing Multiple Products in the Same Domain for detailed information.