![]() ![]() ![]() ![]() ![]() ![]() |
This section provides an overview of the tools and tasks involved in managing WebLogic Integration™ solutions. The following topics are provided:
Note: | Throughout this section, the focus is on administrative tasks and tools that are specific to WebLogic Integration. For more details, see Introduction to WebLogic Platform™ Administration. |
The following tools are available to support WebLogic Integration administration:
http://dev2dev.com/resourcelibrary/utilitiestools/adminmgmt.jsp#snmp
Instructions for installing and configuring the SNMP Agent and a description of the WebLogic Integration MIB items are included in the package.
http://dev2dev.com/resourcelibrary/utilitiestools/adminmgmt.jsp
In addition to the above, WebLogic Server provides a number of tools with which you should be familiar. For more information, see " System Administration for BEA WebLogic Server.
Note: | Items or tools on
http://dev2dev.com are listed for your convenience and are not supported by BEA Customer Support.![]() |
Resources within a domain use Java Management Extensions (JMX) Managed Beans (MBeans) to expose their management functions. An MBean is a concrete Java class that is developed per JMX specifications. It can provide getter and setter operations for each management attribute within a managed resource along with additional management operations that the resource makes available. MBeans that expose the configuration data of a managed resource are called Configuration MBeans, while MBeans that provide performance metrics and other information about the runtime state of a managed resource are called Runtime MBeans.
To learn more about WebLogic Server managed resources and MBeans, see Overview of WebLogic JMX Services in Programming WebLogic Management Services with JMX.
To learn more about the WebLogic Integration MBeans, refer to the following packages in the WebLogic Integration Javadoc:
The weblogic.management.MBeanHome
interface is the most convenient way to access the JMX MBean Server that resides on each WebLogic Server in a domain. You can access the Administration MBeanHome
interface from the JNDI tree of the Administration Server as described in "Using JNDI to Retrieve an MBeanHome Interface" in Accessing WebLogic Server MBeans at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jmx/accessWLS.html
The following example shows how you can access the ProcessRuntimeMBean
interface:
Environment env = new Environment();
env.setSecurityPrincipal("weblogic");
env.setSecurityCredentials("weblogic");
Context ctx = env.getInitialContext();
MBeanHome home = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
System.out.println("Got the Server-specific MBeanHome: " + home);
Set s = home.getMBeansByType("ProcessRuntime");
Iterator it = s.iterator();
try {
while (it.hasNext()){
ProcessRuntimeMBean bean = (ProcessRuntimeMBean)it.next();
ProcessInstanceQuery query = new ProcessInstanceQuery();
query.setServiceURI(context.getService().getURI());
ProcessInstanceQueryResult info = bean.getProcessInstances(query);
String[] instances = info.getInstanceIds();
System.out.println(instances[0]);
}
} catch (Exception ex) {
System.out.println(ex);
ex.printStackTrace();
}
This section provides references to the instructions and background information required to perform the most common WebLogic Integration administrative tasks:
Although a majority of the tasks can be performed using the WebLogic Integration Administration Console, some must be performed using other tools, and in some cases, you must directly edit a configuration file. You can use this section as a roadmap to the task-specific information that can be found in the following resources:
Note: | URLs are provided in the preceding table to assist those using a printed version of the documentation to locate the information referenced in the following sections. If you are viewing an HTML or PDF version of the documentation, the references in the following sections are active links. |
Throughout this reference section, it is assumed that the WebLogic Integration Administration Console is to be used as the primary management tool. As described in WebLogic Integration Management Tools, alternative utilities, such as the SNMP Agent or WLShell, can be used to perform many tasks.
A domain includes one or more instances of WebLogic Server and may include WebLogic Server clusters. WebLogic Integration is a collection of applications and resources—EJBs, Web applications, JDBC connection pools, and so on—that are deployed in a domain to provide a unified platform for developing and deploying comprehensive business integration solutions. A first step in the development or deployment of a WebLogic Integration solution is to create a suitable domain.
The following table provides a roadmap to the information you need to create or extend a development or production (running in "noniterativedev" mode) domain.
|
General information in the overview about WebLogic Server domains and how to use the Configuration Wizard.
|
|
Related tasks and references are provided in Deploying Integration Solutions and Securing WebLogic Integration Resources.
|
||
Additional references are provided in the following section, Managing Database Resources.
|
For general information about managing database resources for WebLogic Platform, see Managing WebLogic Platform Database Resources.
For information about creating the tables required by WebLogic Integration, see Configuring a Production Database.
For information about deploying an integration application from the Workshop environment (running in iterative development mode), see Building and Deploying WebLogic Integration Applications in Building Integration Applications.
For the background information and procedures required to configure a production environment and deploy integration solutions, see Deploying WebLogic Integration Solutions.
Note: | This section focuses on security tasks and references that are specific to WebLogic Integration. For an overview of WebLogic Platform security see Security in WebLogic Platform 9.2. |
The following table provides a roadmap to the information you need to secure WebLogic Integration resources.
Process types can be monitored from the WebLogic Integration Administration Console. For a description of the Process Configuration module, and step-by-step procedures for the various management tasks, see Process Configuration section in Using the WebLogic Integration Administration Console.
You can also access the graphical view of a process type from other HTTP clients. See Accessing Process Graphs from HTTP Clients.
Process instances are monitored from the WebLogic Integration Administration Console. For a description of the Process Instance Monitoring module, and step-by-step procedures for the various monitoring tasks, see Process Instance Monitoring section in Using the WebLogic Integration Administration Console.
You can also access the graphical view of a process instance from other HTTP clients. See Accessing Process Graphs from HTTP Clients.
Message broker channels are monitored from the WebLogic Integration Administration Console. For a description of the Message Broker module, and step-by-step procedures for the monitoring tasks, see the Message Broker section at http://download.oracle.com/docs/cd/E13214_01/wli/docs92/adminhelp/msgbroker.html
WebLogic Integration provides native event generators, including JMS, Email, File, and Timer event generators. These event generators are typically used to start a business process based on events, such as the receipt of email or a new file appearing in a directory. WebLogic Integration also works with Application View event generators, which work with J2EE-CA connectors.
The following table provides a roadmap to the information you need to manage event generators.
"Message Broker Resources" and "Event Generator Resources" in
Introduction in Deploying WebLogic Integration Solutions.
|
||
"Events" section of "
Application Integration Capabilities and Clients" in
Introduction in Deploying WebLogic Integration Solutions.
|
||
"Processing Event Notifications at Run-Time" in
Understanding Application Integration in Introducing Application Integration
|
||
"Events" section of "Load Balancing Application Integration Functions in a Cluster" in Deploying WebLogic Integration Solutions.
|
||
Creating and Deploying Event Generators section in Using The WebLogic Integration Administration Console
|
||
"Deploying Event Generators" in
Understanding WebLogic Integration Clusters in Deploying WebLogic Integration Solutions.
|
||
The description of the wli.jmseg.EatSoapActionElement element in
wli-config.properties Configuration File in Deploying WebLogic Integration Solutions.
|
The following table provides a roadmap to the information you need to manage WebLogic Integration tracking and reporting data.
|
||
|
||
Viewing and Changing Process Details section in Using The WebLogic Integration Administration Console
|
||
Configuring the Mode and Message Tracking section in Using The WebLogic Integration Administration Console
|
||
Configuring the Default Data Policy and Tracking Level for Processes section in Using The WebLogic Integration Administration Console
|
Most of the management tasks associated with business calendars are completed from the WebLogic Integration Administration Console. For a description of the Business Calendar Configuration module, and step-by-step procedures for the various management tasks, see Business Calendar Configuration section in Using The WebLogic Integration Administration Console
Most of the management tasks associated with the worklist can be completed from the WebLogic Integration Administration Console. For a description of the Worklist Administration module, and step-by-step procedures for the various management tasks, see Worklist Administration section in Using the Worklist Console.
Custom worklist interfaces can also provide administrative and management functionality. Refer to Worklist User Interface and Enterprise JavaBeans API in Using the Worklist.
Detailed information regarding worklist operations is provided in the following sections of Using the Worklist.
Most of the application integration management tasks are from the WebLogic Integration Administration Console. For a description of the Application Integration module, and step-by-step procedures for the various management tasks, see Introduction to Application Integration. For background information, refer to the following sections of Introducing Application Integration:
Most of the trading partner integration management tasks are completed from the WebLogic Integration Administration Console. For a description of the Trading Partner Management module, and step-by-step procedures for the various management tasks, see Trading Partner Management in Using The WebLogic Integration Administration Console.
You can also use the Bulk Loader command line utility to import and export trading partner management data. To learn more, see Using the Trading Partner Bulk Loader..
See Securing WebLogic Integration Resources for additional references on securing trading partner integration applications.
The XML Cache stores XML metadata documents. When you are designing a business process, you use the XML Cache Control to retrieve the XML documents stored in the XML Cache. You use the XML Cache module to create and maintain the XML metadata documents stored in the XML Cache. For a description of the XML Cache module, and step-by-step procedures for the various management tasks, see XML Cache section in Using The WebLogic Integration Administration Console.
![]() ![]() ![]() |