Documentos de Académico
Documentos de Profesional
Documentos de Cultura
This sample demonstrates the dynamic message routing capabilities of the Mediator Service Component (aka Mediator).
PROVIDED FILES
Sample zip mediator_107_dynamicrouting.zip will contain following: jdev this directory will contain soa composite and jdev workspace. bin this directory will contain build scripts for building and deploying custom document protocol and associated composite. doc/mediator-107-dynamicrouting.pdf: instructions to build the project and walk through the tutorial [ this file ] artifacts: directory contains schema artifacts and input payloads.
Oracle SOA Suite 11g - Sample Create an Application Connection to a target server Skip this section if you are already familiar with steps to create the weblogic application server connection. From the resource palette create an Application Server connection using the wizard. Name and Type: o Connection name = <any name> o Connection type = e.g. WebLogic 10.3 Authentication: o User name = <username> e.g. weblogic o Password = <password> e.g.weblogic1 Configuration: o Host name = host on which 11g is installed o Port = <port number> e.g. 7001 o WLS Domain = <domain name> e.g. soainfra Application deployment Skip this section if you are already familiar application deployment Right click the project Deploy-> CustomerRouter ->Deploy to Application Server When Revision ID dialog box appears, click next (default revision id is 1.0) Select the connection name, which is created in previous section and Click Next. Select the SOA server for which application has to be deployed. Click next. Repeat the same for DynamieMediator project. Click Finish
Installing and Running the Prebuilt Sample Installing the prebuilt Sample through JDev
Please execute the following steps to run the pre-built sample Open the MediatorDynamicRouting.jws SOA application in JDeveloper using the File Open menu. Double-click on the CustomerStatusLogger File Adapter in customerRouter project, to launch the file adapter wizard. Click on next until the File Directories step of the Wizard is reached. Please update the Directory for Outgoing Files text field to a value that you wish your application to write the files to. Please make sure the directory is accessible from the SOA server on which you expect to run the scenario.
VERIFYING EXECUTION
Please check the target directory (for CustomerRouterlogger) for one copy of customer_1.xml file. The file will contain the name of the customer you provided and the status which will be default , silver , gold or platinum based on the customer name. If customer name is Intel , the status field will have silver, if name is Cisco then status will be gold, if the name is HP then status will be platinum and otherwise it will be default. Please open the EM Console (em ) or SOAConsole (for standalone install) with the appropriate URL http://<hostname>:<portnum>/em or
Step 2: Dynamic Mediator Flow Creation Open DynamicCutomerRouter project composite.xml. Drag and drop an one-wayMediator (Service Component) from the Component Palette/SOA tab from the right-hand side of the diagrammer into the Components swim-lane. Name the component as CustomerRoutingLogger and specify to use CustomerData.xsd [provide as part of the sample for request. Similarly, create another asynchronous mediator component and specify CustomerData.xsd for request and callback operation. Double click on the DynamicCustomerRouter to open the DynamicCustomerRouter.mplan editor. Click on+ icon and it will show static routing rule and dynamic routing rule options. Select dynamic routing rule option. This option will take few second to a minute to created artifacts for dynamic routing rule [Rule service, decision table, dummy reference etc.] Double click on the CustomerRoutingLogger to open the CustomerRoutingLogger.mplan editor. Click on+ icon and it will show static routing rule and dynamic routing rule options. Select static routing rule option and when asked, provide DynamicCustomerRouter as target service. As CustomerRoutingLogger is an one-way mediator component, UI will prompt to provide handler for callback coming from DynamicCustomerRouter. Create outbound File Adapter reference [CustomerStatusLogger] using same schema - CustomerData.xsd