![]() |
![]() |
|
|
Defining an Application View
This section presents the following topics:
Before You Begin
When you define an application view, you are creating an XML-based interface between WebLogic Server and a particular EIS application within your enterprise. Once you create the application view, a business analyst can use it to create business processes that use the application. For any adapter, you can create any number of application views, each of which may contain any number of services and events.
Before you attempt to define an application view, make sure the following prerequisites are satisfied:
High-Level Procedure for Defining an Application View
Figure 2-1 summarizes the procedure for defining and configuring an application view.
Figure 2-1 Procedure for Defining and Configuring an Application View
Sample Detailed Procedure for Defining an Application View
This section explains how to define and maintain application views using an EIS adapter for a hypothetical database EIS called simply DBMS. The steps in the procedure presented here correspond to the steps shown in Figure 2-1.
When you create application views for your enterprise, they may look different from these shown in this document. Such differences are to be expected, because the application view's adapter determines the information required for each application view page, and each enterprise has its own specialized adapters. For details about an adapter used in your enterprise, consult the relevant technical analyst or EIS specialist.
Step 1: Log On to the Application View Console
The Application View Console displays all the application views in your WebLogic Integration environment, organized in folders.
To log on to the Application View Console:
http://host:port/wlai
Steps 2 and 3: Define an Application View and Configure Connection Parameters
Step 4A: Add a Service to an Application View
Step 4B: Add an Event to an Application View
Step 5: Deploy an Application View
You may deploy an application view when you have added at least one event or service to it. You must deploy an application view before you can test its services and events or use the application view in the WebLogic Server environment. By deploying an application view, you place relevant metadata about its services and events into a run-time metadata repository. Deployment also makes the application view available to other WebLogic Server clients. As a result, business processes can interact with the application view, and you can test the application view's services and events.
To deploy an application view:
Optional Step: Undeploy an Application View
You must undeploy an application view whenever you want to edit its connection parameters, add services and events to it, or disable clients from using it. For information about editing connection parameters, see Steps 2 and 3: Define an Application View and Configure Connection Parameters. When an application view is undeployed, no other WebLogic Server clients can interact with it, and you cannot test its services or events.
To undeploy an application view:
Step 6A: Test an Application View's Services
The purpose of testing an application view service is to evaluate whether or not that service interacts properly with the target EIS. You can test an application view only if it is deployed and it contains at least one event or service. To test an application view service:
Step 6B: Test an Application View's Events
The purpose of testing your application view events is to evaluate whether or not the application view responds correctly to the EIS application. You can test an application view only if it is deployed and it contains at least one event or service. To test an application view event:
If You Select Service
If You Select Manual
Editing an Application View
When you define an application view, you must configure its connection parameters. After you add and test services and events, you may want to reconfigure the connection parameters or remove services and events.
To edit an existing application view:
![]() |
![]() |
![]() |
|
Copyright © 2002 BEA Systems, Inc. All rights reserved.
|