Managing Oracle WebLogic Integration Solutions

Managing Oracle WebLogic Integration Solutions: Tools and Tasks

This section provides an overview of the tools and tasks involved in managing Oracle WebLogic Integration solutions. The following topics are provided:

Oracle WebLogic Integration Management Tools

The following tools are available to support Oracle WebLogic Integration administration:

In addition to these tools, Oracle WebLogic Server provides a number of tools with which you should be familiar. For more information about the Oracle WebLogic Server tools, see System Administration for Oracle WebLogic Server.

WebLogic Managed Beans

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.

For more information about Oracle WebLogic Server managed resources and MBeans, see Overview of WebLogic JMX Services in Programming WebLogic Management Services with JMX.

For more information about the Oracle WebLogic Integration MBeans, see the following packages in the Oracle WebLogic Integration Javadoc:

Programmatically Accessing Oracle WebLogic Integration MBeans

The weblogic.management.MBeanHome interface is the most convenient way to access the JMX MBean Server that resides on each Oracle 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 Oracle WebLogic Server MBeans.

Listing 1-1 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(); 
    } 

Oracle WebLogic Integration Management Task Reference

This section provides references to the instructions and background information required to perform the most common Oracle WebLogic Integration administrative tasks:

Majority of these tasks can be performed using the Oracle WebLogic Integration Administration Console.

Some of the tasks 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:

Throughout this reference section, it is assumed that the Oracle WebLogic Integration Administration Console is to be used as the primary management tool. As described in Oracle WebLogic Integration Management Tools, alternative utilities, such as the SNMP Agent or WLShell, can be used to perform many tasks.

Creating or Extending Server Domains

A domain includes one or more instances of Oracle WebLogic Server and may include Oracle WebLogic Server clusters. Oracle 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 Oracle 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.

Managing Database Resources

For information about creating the tables required by Oracle WebLogic Integration, see Configuring a Production Database.

Deploying Integration Solutions

For information about deploying an integration application from the environment (running in iterative development mode), see Building and Deploying Oracle WebLogic Integration Applications in Guide to Building Business Process.

For the background information and procedures required to configure a production environment and deploy integration solutions, see Deploying Oracle WebLogic Integration Solutions.

Securing Oracle WebLogic Integration Resources

This section focuses on security tasks and references that are specific to Oracle WebLogic Integration.

Table 1-3 provides a roadmap to the information you need to secure Oracle WebLogic Integration resources.

Managing Process Types

Process types can be monitored from the Oracle 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 in Using the Oracle 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.

Monitoring Process Instances

Process instances are monitored from the Oracle 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 in Using the Oracle 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.

Monitoring Message Broker Channels

Message broker channels are monitored from the Oracle WebLogic Integration Administration Console. For more information about Message Broker module, and step-by-step procedures for the monitoring tasks, see Message Broker in Using the Oracle WebLogic Integration Administration Console.

Creating and Managing Event Generators

Oracle 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. Oracle WebLogic Integration Table 1-4 provides a roadmap to the information you need to manage event generators.

Managing Oracle WebLogic Integration Tracking and Reporting Data

The following table provides a roadmap to the information you need to manage Oracle WebLogic Integration tracking and reporting data.

Creating Business Calendars and Assigning Them to Users or Groups

Most of the management tasks associated with business calendars are completed from the WorkList 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 Worklist Console.

Managing and Monitoring Worklist Task Plan

Most of the management tasks associated with the worklist can be completed from the Oracle 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 Worklist Console.

Custom worklist interfaces can also provide administrative and management functionality. For more information about custom worklist interfaces, see Using and Customizing User Portal in Using Worklist User Portal.

For more information about worklist operations, see the following sections of Using Worklist Console.

Managing Trading Partner Integration

Most of the trading partner integration management tasks are completed from the Oracle WebLogic Integration Administration Console. For more information about the Trading Partner Management module, and step-by-step procedures for the various management tasks, see Trading Partner Management in Using Oracle WebLogic Integration Administration Console.

You can also use the Bulk Loader command line utility to import and export trading partner management data. See Using the Trading Partner Bulk Loader.

For more information about securing trading partner integration applications, see Securing Oracle WebLogic Integration Resources .

Managing XML Cache Instances

The XML Cache stores XML metadata documents. When you are designing a business process, XML Cache Controls are used 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 more information about XML Cache module, and step-by-step procedures for the various management tasks, see XML Cache section in Using The Oracle WebLogic Integration Administration Console.