Skip Headers
Oracle® Communications Billing and Revenue Management JCA Resource Adapter
Release 7.4

E25091-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

3 Deploying and Configuring the BRM JCA Resource Adapter

This chapter describes how to deploy and configure the Oracle Communications Billing and Revenue Management (BRM) JCA Resource Adapter.

Before configuring the adapter, you should be familiar with the following:

Overview of the BRM JCA Resource Adapter Configuration Procedure

The procedure for setting up the BRM JCA Resource Adapter includes the following tasks:

  1. Installing the adapter on your BRM system, if you have not already done so. See "Installing the BRM JCA Resource Adapter".

  2. Compiling your custom Java Portal Connection Module (PCM) classes and adding them to the adapter. See "Creating and Packaging Custom Classes and Fields".

  3. Generating the schema files for the adapter. See "Generating the Schema Files for Your System".

  4. Specifying how to construct XML tags. See "Specifying the XML Tags for Extended Fields".

  5. Generating the WSDL files for the adapter. See "Generating the WSDL Files for Your System".

  6. Deploying and connecting the adapter on your application server:

Creating and Packaging Custom Classes and Fields

The JCA Resource Adapter uses Java PCM APIs to connect to BRM. If the adapter will be calling opcodes that reference custom storable class fields, you must make the custom storable class fields available to the adapter by:

  • Compiling your custom classes and adding them to the adapter.

  • Adding the Infranet.properites file as a resource to the adapter. The Infranet.properties file defines which package contains the custom field definitions.

    Note:

    The application server class loader does not load the Infranet.properties file, so you must make the file available as a resource.

To make your custom and modified storable classes available to the JCA Resource Adapter:

  1. Use Storable Class Editor to create or modify your storable classes and fields. For information, see Storable Class Editor Help.

    For information about editing storable classes, see "Creating, Editing, and Deleting Fields and Storable Classes" in BRM Developer's Guide.

  2. Choose File - Generate Custom Fields Source to create source files for your custom fields. See Storable Class Editor Help for detailed instructions.

    Storable Class Editor creates a C header file called cust_flds.h, a Java properties file called InfranetPropertiesAdditions.properties, and a Java source file for each custom field.

  3. For each Java application that will use these fields, copy the contents of the InfranetPropertiesAdditions.properties file and paste it into each application's Infranet.properties file.

  4. In the directory where Storable Class Editor created the Java source files, compile the source files:

    javac -d . *.java 
      
    
  5. Package the class files created in step 4 into a JAR file:

    jar cvf filename.jar *.class 
      
    
  6. In the CLASSPATH, add the location of the JAR file.

  7. Create a package that includes both the JAR file and the updated BRM Infranet.properties file.

  8. Place the package in the adapter's working directory (Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName).

  9. Restart your application server.

Generating the Schema Files for Your System

The JCA Resource Adapter uses schema files to validate data it sends to or receives from the BRM software.

To generate the schema files for your system, perform these tasks:

  1. If you modified any opcodes, generate schemas for the opcodes in your BRM system. See "Generating the Schema for Your Opcodes".

  2. Generate schemas for the storable classes and subclasses in your BRM system. See "Generating the Schema for Your Storable Classes and Subclasses".

  3. In your opcode schema files, specify the location of your storable class schema files. See "Specifying the Location of the Storable Class Schema Files in the Opcode Schema Files".

    Note:

    After generating the opcode and storable class schema files, copy the schema files to a location that is accessible to the adapter. Make sure that this location is the same as the one specified in the include section of the opcode schema files and in the opcode schema InteractionSpec attribute in the WSDL files. See "Specifying the Location of the Storable Class Schema Files in the Opcode Schema Files" and "Generating the WSDL Files for Your System".

Generating the Schema for Your Opcodes

The adapter package includes all of the opcode schemas and flist specifications you need for a default integration.

If you customized any of the opcodes that are supported by the adapter or if you added support for new opcodes, you must generate XSD schema files for the opcodes.

The steps you need to take depend on the type of changes you made, as shown in Table 3-1:

Table 3-1 Procedure for Modifying Opcodes

Opcode Modification Procedure

Customized an opcode that the JCA Resource Adapter already supports

  1. Modify the opcode's XML specification file. By default, the opcode specification XML files are installed in the BRM_Home/apps/brm_integrations/opspecs directory. See "Creating Custom Opcode Specification XML Files".

  2. Run the pin_opspec_to_schema utility. See "Converting flist Specs into XSD Schema Files with pin_opspec_to_schema".

Added a custom data type to an opcode that the JCA Resource Adapter already supports

  1. Modify the opcode's XML specification file. By default, the opcode specifications are installed in the BRM_Home/apps/brm_integrations/opspecs directory. See "Creating Custom Opcode Specification XML Files".

  2. Modify the pin_opspec_to_schema style sheet to handle custom data types or custom data structures. See "Specifying the XSL Rules to Create the Opcode Schema".

  3. Run the pin_opspec_to_schema utility. See "Converting flist Specs into XSD Schema Files with pin_opspec_to_schema".

Added a custom opcode to the JCA Resource Adapter

  1. Configure BRM to recognize the custom opcode and manually create the opcode's XML specification file. See "Writing a custom Facilities Module" in BRM Developer's Guide.

  2. If your opcode supports custom data types or data structures, modify the pin_opspec_to_schema style sheet. See "Specifying the XSL Rules to Create the Opcode Schema".

  3. Run the pin_opspec_to_schema utility. See "Converting flist Specs into XSD Schema Files with pin_opspec_to_schema".

Note: Make sure you add your custom opcode to a WSDL file. See "Generating the WSDL Files for Your System".


Creating Custom Opcode Specification XML Files

You must create XML specification files for any opcodes that you customize or add to the adapter. Create the XML specification files by following the BRM_Home/apps/brm_integrations/stylesheets/opspec.xsd file. You can then convert the opcode specifications into XSD schema by using the pin_opspec_to_schema utility.

Specifying the XSL Rules to Create the Opcode Schema

The pin_opspec_to_schema utility uses the BRM_Home/brm_integrations/stylesheets/pin_opspec_to_schema.xsl style sheet to generate the schema for BRM opcodes. If your opcode references custom data types or custom data structures, you must customize the pin_opspec_to_schema.xsl style sheet to handle your customizations.

For a list of the supported BRM data types, see "Understanding the BRM Data Types" in BRM Developer's Guide.

Converting flist Specs into XSD Schema Files with pin_opspec_to_schema

You convert opcode flist specifications into XSD schema by using the pin_opspec_to_schema utility.

To generate XSD schema, go to the BRM_Home/apps/brm_integrations directory and run the following command:

pin_opspec_to_schema -i InputFile [-o OutputFile]
  

where:

  • -i InputFile specifies the name and location of the opcode's XML flist specification. By default, the utility looks for the file in the current directory.

  • -o OutputFile creates the XSD schema output file using the name you specify. By default, the utility creates a file named opcodename.xsd in the directory from which you run the utility.

Generating the Schema for Your Storable Classes and Subclasses

The adapter uses storable class schema files to validate storable class extensions passed in the input XML. See "Connecting J2EE-Compliant Applications to BRM".

To generate storable class schema files for your system:

  1. Determine which storable class files you need to convert into XSD schema. See "Determining the Storable Classes to Convert Into Schema".

  2. Convert your storable classes and subclasses by running the pin_dd_to_schema utility. See "Generating Storable Class Schema Files with pin_dd_to_schema".

Determining the Storable Classes to Convert Into Schema

The adapter package includes all of the storable class schema files required for a default integration. By default, they are installed in the BRM_Home/apps/brm_integrations/schemas directory.

You will need to generate additional schema files if your system contains the following:

  • Extensions to the /account, /billinfo, /discount, /event, /event/billing, /payinfo, /product, /profile, /purchased_discount, /purchased_product, or /service storable classes. If you extended any of these storable classes, you must create a new schema file for the base class. For example, if you added a subclass to the /profile storable class, you must regenerate the profile.xsd schema file.

  • Storable classes required by opcodes you added to the adapter. If you added an opcode schema to the adapter, you can determine whether it requires a storable class by checking for an include schemaLocation entry at the beginning of the schema file. If the entry exists, it lists the required storable class schema files. For example, the PCM_OP_CUST_COMMIT_CUSTOMER.xsd schema file includes these entries, which indicate that the opcode needs schema files for the /service and /profile classes:

    <?xml version = '1.0' encoding = 'UTF-8'?>
    <xsd:schema targetNamespace="http://www.xmlns.oracle.com/BRM/schemas/BusinessOpcodes"
    elementFormDefault="qualified"
        xmlns="http://www.xmlns.oracle.com/BRM/schemas/BusinessOpcodes"
        xmlns:op="http://www.portal.com/schemas/BusinessOpcodes"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      
      <xsd:include schemaLocation="service.xsd"/>
      <xsd:include schemaLocation="profile.xsd"/>
      
      <xsd:element name="PCM_OP_CUST_COMMIT_CUSTOMER_inputFlist">
        <xsd:complexType>
    

Generating Storable Class Schema Files with pin_dd_to_schema

You use the pin_dd_to_schema utility to generate the schema for storable classes and their subclasses from the data dictionary. The adapter uses the schema to validate the object fields that are passed in the input XML.

Note:

The utility requires a configuration file to access the BRM database. For more information, see "Using Configuration Files to Connect and Configure Components" in BRM System Administrator's Guide.

Before you run the pin_dd_to_schema utility, make sure you have added the storable class changes to the BRM data dictionary.

To generate the schema for the storable classes and subclasses in your system:

  1. Using a text editor, create a configuration file that lists all storable classes you would like to convert. For example, create a sample.txt file that includes the following entries:

    /service/telco/gsm
    /service/telco/gprs
    /service/sms
    /service/telephony
    /profile
      
    
  2. Save and close the file.

  3. On Linux systems only, set the LC_ALL environment variable to C:

    setenv LC_ALL C
      
    
  4. Go to the BRM_Home/apps/brm_integrations directory and enter the following command:

    pin_dd_to_schema  -e ConfigFile | -r StorableClass
      
    

    where:

    • -e ConfigFile generates the schema for all storable classes listed in the configuration file as well as their subclasses.

    • -r StorableClass generates the schema for the specified storable class and all of its subclasses.

    The utility generates the schema files in the directory from which you run the utility.

  5. Copy the schema files to a location that is accessible to the adapter during the XML validation process. For example, the BRM_Home/apps/brm_integrations/schemas directory.

Specifying the Location of the Storable Class Schema Files in the Opcode Schema Files

Opcode schema files contain an include section that lists each storable class schema file that they need. You must manually update the opcode schema files to point to the storable class schema file's correct location.

Not all opcodes need storable classes, so only a subset of the opcode schema files have the include section. The following list shows the opcode schemas that are packaged with the adapter and have an include section:

  • PCM_OP_CUST_COMMIT_CUSTOMER

  • PCM_OP_CUST_CREATE_PROFILE

  • PCM_OP_CUST_MODIFY_CUSTOMER

  • PCM_OP_CUST_MODIFY_PROFILE

  • PCM_OP_CUST_UPDATE_CUSTOMER

  • PCM_OP_CUST_UPDATE_SERVICES

  • PCM_OP_PYMT_COLLECT

  • PCM_OP_READ_FLDS

  • PCM_OP_READ_OBJ

  • PCM_OP_SUBSCRIPTION_CANCEL_DISCOUNT

  • PCM_OP_SUBSCRIPTION_CANCEL_PRODUCT

  • PCM_OP_SUBSCRIPTION_CANCEL_SUBSCRIPTION

  • PCM_OP_SUBSCRIPTION_CHANGE_DEAL

  • PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS

  • PCM_OP_SUBSCRIPTION_PURCHASE_DEAL

  • PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO

  • PCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUS

  • PCM_OP_SUBSCRIPTION_SET_PRODINFO

  • PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS

  • PCM_OP_SUBSCRIPTION_TRANSFER_SUBSCRIPTION

Perform the following for each opcode schema that contains an include section for the storable class schema files:

  1. Open the opcode XSD schema file in a text editor. By default, the opcode schema files are located in the BRM_Home/apps/brm_integrations/schemas directory.

  2. Edit the include schemaLocation entry to point to each schema file's correct location. For example, you edit the lines shown in bold below for the PCM_OP_CUST_COMMIT_CUSTOMER.xsd file:

    <?xml version = '1.0' encoding = 'UTF-8'?>
    <xsd:schema targetNamespace="http://www.xmlns.oracle.com/BRM/schemas/BusinessOpcodes"
    elementFormDefault="qualified"
        xmlns="http://www.xmlns.oracle.com/BRM/schemas/BusinessOpcodes"
        xmlns:op="http://www.portal.com/schemas/BusinessOpcodes"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      
      <xsd:include schemaLocation="service.xsd"/>
      <xsd:include schemaLocation="profile.xsd"/>
      
      <xsd:element name="PCM_OP_CUST_COMMIT_CUSTOMER_inputFlist">
        <xsd:complexType>
    

    Note:

    The adapter does not support accessing schemas through URLs.
  3. Save and close the file.

Specifying the XML Tags for Extended Fields

The brm_extensions.xml file defines how to construct XML tags for PIN_FLD_INHERITED_INFO and PIN_FLD_EXTENDED_INFO substructs when converting output flists into XML. The default file is preconfigured for the opcode and storable class schemas shipped with the adapter. You must modify this file if you added to the adapter any opcodes that reference storable class fields.

The adapter creates XML tags for PIN_FLD_INHERITED_INFO and PIN_FLD_EXTENDED_INFO substructs by using the following syntax:

ClassExtension
  

where Class is the subclass name, using an underscore (_) notation. For example, the XML tag for /service/telco/gsm is written as service_telco_gsmExtension. You configure how the adapter determines the subclass name by using the brm_extensions.xml file. The file specifies the following for each opcode:

  • The flist array that contains the PIN_FLD_INHERITED_INFO or PIN_FLD_EXTENDED_INFO substruct.

  • The flist field in which to look up the subclass name.

To specify how to create XML tags for custom extensions, perform the following tasks:

  1. Open the brm_extensions.xml file in an XML editor.

    Note:

    The file is packaged with the adapter and is copied to the Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName directory during the deployment process.
  2. Enter the opcode that requires the subclass fields in the opcode name entry:

    <opcode name="Opcodename">
      
    
  3. Enter the flist field used to construct the XML tag in the container name entry:

    <container name="Arrayname">Fieldname</container>
      
    

    where:

    • Arrayname specifies the array that contains the PIN_FLD_INHERITED_INFO or PIN_FLD_EXTENDED_INFO substruct.

    • Fieldname specifies the flist field in which to look up the subclass name.

    For example, the following entry for the PCM_OP_CUST_COMMIT_CUSTOMER opcode specifies that when the PIN_FLD_SERVICES output flist array contains PIN_FLD_INHERITED_INFO or PIN_FLD_EXTENDED_INFO, the adapter looks up the subclass name from the PIN_FLD_SERVICE_OBJ flist field.

    <?xml version="1.0" encoding="UTF-8"?>
    <brm_extensions>
    <opcode name="PCM_OP_CUST_COMMIT_CUSTOMER">
    <container name="PIN_FLD_SERVICES">PIN_FLD_SERVICE_OBJ</container>
    </opcode> 
    ... 
    </brm_extensions> 
      
    

    In this example, if the PIN_FLD_SERVICE_OBJ output flist field is 0.0.0.1 /service/ip 12345 0, Class is service_ip and the corresponding XML extension tag is service_ipExtension.

  4. Save and close the file.

  5. Restart the adapter.

Generating the WSDL Files for Your System

The adapter package includes all of the WSDL files you need for a default implementation. If you customized the adapter to support additional opcodes, you must create or modify a WSDL file.

To generate a WSDL file:

Defining a Web Service

To define a Web service, you specify the following in a configuration file:

  • The Web service name.

  • The opcodes associated with the Web service.

  • The location of each opcode's schema files.

You create the configuration file manually by using an XML editor. The adapter provides a sample XML configuration file (BRM_Home/apps/brm_integrations/config/pin_wsdl_generator.xml) that you can use as a guide.

The configuration file includes four main sections: namespaces, groups, binding-info, and service-info. You configure the groups section only; the namespaces, binding-info, and service-info sections are preconfigured for Oracle Application Server.

Defining Default Values for a Web Service

You specify the default values for a Web service in the group-info name entry. The default values apply to all opcodes in the Web service, but they are overridden by any opcode-specific values defined in the opcode name entry. For information, see "Defining Settings for Individual Opcodes".

<group-info name="BASE" base="True" includePath="../schemas/"
 wsdlFileInFix="Base"  validation="ValidationNotRequired"
 validationAttr="ValidationNotRequired">
  

where:

  • group-info name specifies the name of the Web service.

  • base specifies whether the opcodes in this Web service are base opcodes. See "Base Opcodes" in BRM Developer's Reference. The default is False.

  • includePath specifies the relative path to the schema files. The utility adds this value to the WSDL file's include entries.

  • wsdlFileInFix specifies the value to add to the WSDL file name, using this syntax: BRMValueServices.wsdl. For example, if wsdlFileInFix is set to Bill, the WSDL file name is BRMBillServices.wsdl. If this attribute is not present, the utility uses the group-info name value in the file name's syntax.

  • validation specifies whether the adapter validates the input and output XML for the opcodes in this group. The valid values are:

    • ValidationRequired, which specifies to validate the input and output XML. You can limit validation to just the input XML or just the output XML by using the validationAttr entry.

    • ValidationNotRequired, which specifies to skip the validation process.

    • InternalSchemaValidation, which specifies that the utility determines whether to validate the input and output XML by reading the validation requirement from the interaction specification.

    The default is ValidationRequired.

  • validationAttr specifies whether to validate only the input XML or only the output XML. This entry is valid only when the validation entry is set to ValidationRequired. The valid values are:

    • InputValidationNotRequired, which specifies to validate only the output XML.

    • OutputValidationNotRequired, which specifies to validate only the input XML.

Defining Settings for Individual Opcodes

You use the opcode name lines to list the opcodes that are in the Web service. Each opcode in the Web service must have its own opcode name entry.

Note:

The opcode-specific settings in this section override the default settings in the group-info name entry. If you set both default values and values specific to an individual opcode, the utility uses the opcode-specific settings first.
 <opcode name="PCM_OP_SEARCH"
base="True" 
custom="no"
opcodeNumber="89"
includePath="../schemas/"
wsdlFileInFix="Base" 
validation="ValidationRequired" 
validationAttr="InputValidationNotRequired">
   <opcodeFlag>1</opcodeFlag>
  

where:

  • opcode name specifies the name of an opcode in the Web service.

  • base specifies whether the opcode is a base opcode. See "Base Opcodes" in BRM Developer's Reference. The default is False.

  • custom specifies whether the opcode is a custom opcode. The valid values are yes and no. The default is no.

  • opcodeNumber specifies the opcode number. This field is mandatory if the custom field is set to yes.

  • includePath specifies the relative path to the schema files. The utility adds this value to the WSDL file's include entries.

  • wsdlFileInFix specifies the value to add to the WSDL file name, using this syntax: BRMValueServices.wsdl. For example, if wsdlFileInFix is set to Bill, the WSDL file name is BRMBillServices.wsdl. If this attribute is not present, the utility uses the group-info name value in the file name's syntax.

  • validation specifies whether the adapter validates the input and output XML. The valid values are:

    • ValidationRequired, which specifies to validate the input and output XML. You can limit validation to just the input XML or just the output XML by using the validationAttr entry.

    • ValidationNotRequired, which specifies to skip the validation process.

    • InternalSchemaValidation, which specifies that the utility determines whether to validate the input and output XML by reading the validation requirements from the interaction specification.

    The default is ValidationRequired.

  • validationAttr specifies whether to validate only the input XML or only the output XML. This entry is valid only when the validation entry is set to ValidationRequired. The valid values are:

    • InputValidationNotRequired, which specifies to validate only the output XML.

    • OutputValidationNotRequired, which specifies to validate only the input XML.

  • opcodeFlag is the flag to pass to the opcode when it is called by the adapter. The default is 0.

Sample Web Services Group Configuration File

The following shows a sample XML configuration file:

<?xml version='1.0'?>
<wsdl-generate>
  <namespaces>
    <partnerlink-namespace     prefix="plt">http://schemas.xmlsoap.org/ws/2003/05/partner-link/</partnerlink-namespace>
    <jca-namespace prefix="jca">http://xmlns.oracle.com/pcbpel/wsdl/jca/</jca-namespace>
    <soap-namespace prefix="soap">http://schemas.xmlsoap.org/wsdl/soap/</soap-namespace>
    <default-namespace>http://schemas.xmlsoap.org/wsdl/</default-namespace>
    <brm-nameSpace prefix="brm">http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes</brm-nameSpace>
  </namespaces>
  <groups>
    <group-info name="BAL" includePath="../schemas/" wsdlFileInFix="Bal">
     validation=”ValidationRequired” validationAttr=”InputValidationNotRequired”/> 
    <opcode name=”PCM_OP_BAL_GET_BAL_GRP_AND_SVC” 
     validation=”ValidationNotRequired”>
      <opcodeFlag>1</opcodeFlag> 
    </group-info>
  </groups>
  <binding-info>
    <!-- binding information specific to J2CA and SOAP.
    The general binding information is filled by the tool. -->
  <JCA>
    <InteractionSpec>oracle.tip.adapter.brm.BRMInteractionSpec</InteractionSpec>
  </JCA>
  <SOAP>
    <Action>http://localhost/operationName</Action>
    <encodingStyle>http://schemas.xmlsoap.org/soap/encoding/</encodingStyle>
  </SOAP>
  </binding-info>
  <service-info>
    <!-- Service information specific to J2CA and SOAP -->
    <JCA>
      <!-- JNDI name of the BRM JCA Adapter -->
      <location>eis/BRM</location>
    </JCA>
    <SOAP>
      <address>http://localhost:8080/brm/BRMWS</address>
    </SOAP>
  </service-info>
</wsdl-generate>

Generating WSDL Files for Web Services

After you define a Web service in the XML configuration file, you generate the WSDL file by running the pin_wsdl_generator utility.

To generate WSDL files, go to the BRM_Home/apps/brm_integrations/config directory and run the following command:

pin_wsdl_generator [-c ConfigFile] [-j | -s]
  

where:

  • -c ConfigFile specifies the name and location of the XML configuration file that describes the grouping of opcodes. By default, the utility uses the BRM_Home/apps/brm_integrations/config/pin_wsdl_generator.xml file.

  • -j specifies to generate WSDL files with JCA bindings. This is the default.

  • -s specifies to generate WSDL files with SOAP bindings.

The utility generates the WSDL files in the current directory.

Configuring How to Represent Infinite Date Values

In some external applications, the infinite date value is represented as a NULL (empty XML element) value and in other external applications as the epoch time (01-01-1970 1200 AM UTC).

By default, when the JCA Resource Adapter sends data to your external application, the infinite date value is the start of the epoch time.

You can define how the JCA Resource Adapter sets infinite date values by using the ZeroEpochAsNull connection factory field.

Note:

Before configuring the new connection factory field, you must redeploy the JCA Resource Adapter on the server running Oracle Application Server or Oracle WebLogic Server.

To configure how to represent infinite date values:

  1. Start the application server or the J2EE instance.

  2. From the Oracle Application Server ASC page or the WebLogic Server Administration Console, go to the resource adapter home page and create connection factories.

  3. Set the ZeroEpochAsNull connection factory field to either of the following values:

    • true sends the date field value as NULL to represent an infinite start or end date.

    • false sends the date field value as the start of the epoch time. This is the default.

    Note:

    Connection factory field values must be lowercase.

Deploying and Connecting the BRM JCA Adapter on Oracle Application Server

To deploy and configure the adapter on Oracle Application Server, perform these tasks:

Deploying the BRM JCA Resource Adapter on Oracle Application Server

The adapter is dependent on JAR files to deploy properly. Table 3-2 lists the JAR files that the adapter requires from each application in your system.

Table 3-2 Jar Files

Application JAR files

J2EE application server

classes12.jar, connector15.jar, and jta.jar

Oracle BPEL process

bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar

Apache

xercesImpl.jar


If you are deploying the adapter in a standalone OC4J instance, make sure these JAR files are available to the class loader that is loading the adapter.

If you are deploying the adapter by using Oracle SOA Suite, these JAR files are available as part of the oracle.bpel.common code source. You import these libraries as follows:

  1. Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.

  2. Add the oracle.bpel.common entry (shown in bold below) to the imported-shared-libraries section of the file:

    <imported-shared-libraries>
       <import-shared-library name="adf.oracle.domain"/>
       <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
      
    
  3. Save and close the file.

  4. Restart the application server or the J2EE instance.

After you make the JAR files available, deploy the adapter on Oracle Application Server by using either Oracle Application Server Application Server Control (ASC) or the Oracle admintool.jar file. Copy the adapter archive file (BRM_Home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar) from the installation directory to a location that is accessible to the adapter deployment tool. You can then open and deploy the archive file on your application server. When deploying the archive file, make sure you:

  • Name the adapter BRMJCAAdapter.

  • Choose the default deployment plan.

  • Choose the private connection pool.

After successful deployment, return the applications.xml file to its original settings and add the oracle.bpel.common codesource to the BRM Adapter oc4j-ra.xml file:

  1. Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.

  2. Remove the following oracle.bpel.common entry (shown in bold below):

    <imported-shared-libraries>
       <import-shared-library name="adf.oracle.domain"/>
       <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
      
    
  3. Save and close the file.

  4. Open the JCA Resource Adapter oc4j-ra.xml file from the Oracle_home/j2ee/Instance/application-deployments/default/BRMJCAAdapter directory.

  5. Add the oracle.bpel.common entry (shown in bold below) to the oc4j-connector-factories section of the file:

    <oc4j-connector-factories...>
       <imported-shared-libraries>
          <import-shared-library name="oracle.bpel.common"/>
       </imported-shared-libraries>
       ...
    <oc4j-connector-factories>
      
    
  6. Save and close the file.

  7. Restart the application server or the J2EE instance.

For more information about deploying the adapter, see your application server's documentation.

Connecting the Adapter to BRM in Oracle Application Server

You connect the adapter to the BRM software by creating connection pools and connection factories. As part of the adapter deployment, the application server creates the oc4j-ra.xml file from the packaged ra.xml file. The ra.xml file is located in the Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName/META-INF directory. For example, Oracle_home/j2ee/home/connectors/BRMAdapter/BRMAdapter/META-INF/ra.xml.

Create your connection pool by following the performance and tuning guidelines in Configuring Connection Pooling in OC4J in Oracle Containers for J2EE Resource Adapter Administrator's Guide found at: http://www.oracle.com/technetwork/documentation/index.html

To configure the JCA Resource Adapter connection factory and connection pool:

  1. Restart the application server or the J2EE instance.

  2. Use the resource adapter home page from the Oracle Application Server ASC page to create connection pools and connection factories. Create the adapter's Connection Factory with the connection pooling scheme set to Use PrivateConnection Pool.

    For each connection factory, specify the following along with the connection factory field values listed in Table 3-3:

    • The JNDI location for the connection factory.

    • The connection pool to use.

    • How to connect to BRM by using these entries:

      Note:

      Connection factory field values must be lower case.

    Table 3-3 Connection Factory Field Values

    Entry Description

    AverageOpcodeCount

    Specifies the average number of opcode calls per thread.

    BRMConnectionPoolMaxIdleTime

    Specifies the maximum amount of time in milliseconds that a free connection in the Connection Pool can be idle. If a free connection is idle for a time greater than or equal to BRMConnectionPoolMaxIdleTime, the connection is removed from the pool.

    Note: Only the connections created after the limit set by BRMConnectionPoolMinsize is reached are verified for the idle time; if the condition is met, the connection is removed from the pool.

    BRMConnectionPoolMaxSize

    Specifies the maximum number of connections the Connection Pool can create.

    BRMConnectionPoolMinSize

    Specifies the minimum number of connections created by the Connection Pool when the pool is initialized.

    BRMConnectionPoolTimeout

    Specifies the maximum amount of time in milliseconds that a connection request is queued.

    ConnectionString

    Specify the protocol, host name, and port number for connecting to the BRM software. For example: ip server1 12006.

    Note: The protocol must be set to ip.

    InputValidation

    Specifies whether to validate the input XMLRecord:

    • true: The adapter validates the input XMLRecord against the opcode schema.

    • false: The adapter does not validate the input XMLRecord.

    The default is false.

    This overrides any other validation parameter specified in the WSDL file. For information about setting the validation parameters in the WSDL file, see "Defining a Web Service".

    InteractionTimeZone

    Specifies the time zone of the date fields in which the JCA Resource Adapter sends the date fields to the AIA components. The valid values are UTC and LOCAL. The default is UTC.

    For AIA 2.5 and later systems, do not change the default value. For AIA 2.4 and earlier systems, set the value to LOCAL.

    LoginType

    Specifies the authentication method:

    • 1: The adapter logs in to BRM by using the specified login name and password.

    • 0: The adapter logs in to BRM by using the specified service type and POID ID.

    The default is 1.

    MaxRequestListSize

    Specifies the maximum number of connection requests the Connection Pool can queue before returning a NAP_CONNECT_FAILED error.

    Typically, the requests are queued when all the connections in the Connection Pool are occupied.

    MultiDB

    Specifies whether to enable connections to multiple databases:

    • true: Enables connections to multiple databases.

    • false: Disables connections to multiple databases.

    OutputValidation

    Specifies whether to validate the output XMLRecord:

    • true: The adapter validates the output XMLRecord against the opcode schema.

    • false: The adapter does not validate the output XMLRecord.

    The default is false.

    This overrides any other validation parameter specified in the WSDL file. For information about setting the validation parameters in the WSDL file, see "Defining a Web Service".

    Password

    Specify the password the adapter uses for logging in to the BRM software.

    This entry is required only if LoginType is set to 1.

    Note: The default password is encrypted on the screen. However, when you type a new password, it is not encrypted.

    PoidID

    Specifies the POID. This entry should be set to 1.

    If the JCA Resource Adapter is deployed under a brand, set PoidID to the account POID of the brand login.

    ServiceType

    Specifies the service the adapter uses to log in to the BRM software.

    The default is /service/pcm_client.

    UserName

    Specifies the login name the adapter uses for logging in to the BRM software.

    Note: This entry is required only if LoginType is set to 1.


  3. Open the JCA Resource Adapter oc4j-ra.xml file from the Oracle_home/j2ee/Instance/application-deployments/default/BRMJCAAdapter directory.

  4. Make sure the following entries are set as shown below:

    <connection-pooling use="private"> 
        <property name="waitTimeout" value="300" /> 
        <property name="scheme" value="fixed_wait" /> 
        <property name="maxConnections" value="300" /> 
        <property name="inactivity-timeout-check" value="periodic" /> 
        <property name="minConnections" value="100" /> 
        <property name="initial-capacity" value="25" /> 
        <property name="inactivity-timeout" value="300" /> 
    </connection-pooling> 
      
    
  5. Save and close the file.

You have successfully configured the adapter to connect to BRM.

Configuring the Transaction Mode in Oracle Application Server

If you are deploying JCA Resource Adapter on Oracle Application Server, set the JCA Resource Adapter transaction mode as follows:

  1. Unzip the BRM_Home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar file by using the following command:

    unzip OracleBRMJCA15Adapter.rar –d OracleBRMJCA15Adapter
      
    
  2. In the META-INF directory, open the ra.xml file.

    Note:

    If you are deploying the JCA Resource Adapter on a WebLogic server, configure the transaction mode in the weblogic-ra.xml file instead of the ra.xml file.
  3. In the config-property section, replace the value in the <config-property-value> element with the appropriate transaction mode:

    <config-property>
    <config-property-name>transactionMode</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>TransactionMode</config-property-value>
    </config-property>
      
    

    where TransactionMode is:

    • NO_TRANSACTION for no transaction mode

    • LOCAL_TRANSACTION for local transaction mode

  4. In the <transaction-support> element, replace the value with the appropriate transaction supported value:

    <transaction-support>TransactionSupported</transaction-support>
      
    

    where TransactionSupported is:

    • NoTransaction for no transaction

    • LocalTransaction for local transaction

    Note:

    TransactionMode in the <config-property-value> element and TransactionSupported in the <transaction-support> element must match. If they do not match, the JCA Resource Adapter generates a run-time error.
  5. Save and close the file.

  6. Repackage the META-INF directory in the OracleBRMJCA15Adapter.rar file by using the following command:

    jar –cvf ../AdapterName.rar .
      
    

    where AdapterName is the name of the JCA Resource Adapter.

  7. Redeploy JCA Resource Adapter.

Configuring Java Logging on Oracle Application Server

The JCA Resource Adapter supports Java Unified Logging (JUL), which allows the adapter to use the Oracle Application Server logging library. You specify how the adapter generates log files by editing the OC4J logging configuration file (j2ee-logging.xml).

To specify how the adapter generates log files:

  1. Create the following new directory: Oracle_home/j2ee/Instance/application-deployments/default/BRMAdapter/logs.

  2. Open the Oracle_home/j2ee/Instance/config/j2ee-logging.xml file in an XML editor.

  3. Add following lines under the <log_handlers> element:

    <log_handlers> 
       <log_handler name="brm-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory"> 
          <property name="path" value="Oracle_home/j2ee/oc4j_soa/application-deployments/default/BRMAdapter/logs/BRMAdapterLog.log"/>
          <property name="maxFileSize" value="10485760"/> 
          <property name="maxLogSize" value="104857600"/> 
          <property name="encoding" value="UTF-8"/> 
          <property name="format" value="ODL-TEXT"/> 
       </log_handler> 
    </log_handlers> 
      
    

    where:

    • Path specifies the directory in which the adapter creates the log file.

    • maxFileSize specifies the maximum size, in bytes, of the log file. When a log file reaches this limit, a new log file is generated.

    • maxLogSize specifies the maximum size, in bytes, of the logging directory.

    • encoding must be set to UTF-8.

    • format must be set to ODL-TEXT. This enables you to view the log files directly in the Oracle Application Server control console.

  4. Add the following lines under the <loggers> element:

    <loggers> 
       <logger name="oracle.tip.adapter.brm" level="LogLevel" useParentHandlers="false"> 
          <handler name="oc4j-handler"/> 
          <handler name="brm-handler"/> 
       </logger>  
      
    

    where LogLevel is set to one of the following:

    • SEVERE to log problems that require attention from the system administrator.

    • WARNING to log actions that should be reviewed and may require action before an error occurs.

    • INFO to log normal actions or events. This includes user operations, such as user log ins, and automatic operations, such as log file rotations.

    • CONFIG to log configuration-related messages.

    • FINE to log trace or debug messages for performance monitoring.

    • FINER to log highly detailed trace or debug message.

    • FINEST to log the most detailed trace or debug messages.

  5. Save and close the file.

  6. Restart the application server or the J2EE instance.

Changing the Java Logging Level

To change the logging level by using the Oracle Application Server ASC:

  1. On the OC4J home page, click Administration.

  2. From the administration tasks, select Logger Configuration.

    The Logger Configuration page appears.

  3. Click Expand All to view the entire list of loggers currently loaded for the OC4J instance.

  4. Select NULL for oracle.tip.adapter.brm.

  5. Click Apply.

Deploying and Connecting the BRM JCA Adapter on Oracle WebLogic Server

To deploy and configure the adapter on Oracle WebLogic Server, perform these tasks:

Deploying the BRM JCA Resource Adapter on Oracle WebLogic Server

The adapter is dependent on JAR files to deploy properly. Table 3-4 lists the JAR files that the adapter requires from each application in your system.

Table 3-4 Jar File Details

Application JAR Files

J2EE application server

classes12.jar, connector15.jar, and jta.jar

Oracle BPEL process

bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar

Apache

xercesImpl.jar


If you are deploying the adapter in a standalone WebLogic Server instance, make sure these JAR files are available to the class loader that is loading the adapter.

To deploy the adapter on WebLogic Server:

  1. Start the WebLogic Server domain, if it is not already started.

  2. Log in to the Oracle WebLogic Server Administration Console. The default is:

    http://localhost:8001/console
      
    
  3. Click Lock and Edit.

  4. In the Domain Structure tree, click Deployments.

    The Summary of Deployments pane appears.

  5. Click Install.

    The Install Application Assistant pane appears.

  6. Browse to the deploy directory of the ResourceAdapterDeployment project, select the OracleBRMJCAAdapter.rar file, and click Next.

  7. Select Install this deployment as an application and click Next.

  8. In the server list, select the required server, and click Next.

  9. Accept all other defaults on the remaining screens.

  10. Click Finish.

  11. Click Activate Changes, which deploys the resource adapter.

Check the state of the OracleBRMJCAAdapter application in the WebLogic Server Administration Console. Start the application if the state is set to Prepared.

Connecting the Adapter to BRM in Oracle WebLogic Server

You connect the adapter to the BRM software by creating connection pools and connection factories. As part of the adapter deployment, the application server creates a weblogic-ra.xml file from the packaged ra.xml file.

To configure the JCA Resource Adapter connection factory and connection pools:

  1. Use the resource adapter home page from the WebLogic Server Administration Console to create connection pools and connection factories.

    For each connection factory, specify the following along with the connection factory field values listed in Table 3-5:

    • The JNDI location for the connection factory.

    • The connection pool to use.

    • How to connect to BRM by using these entries:

      Note:

      Connection factory field values must be lower case.

    Table 3-5 Connection Factory Field Values

    Entry Description

    ConnectionString

    Specify the protocol, host name, and port number for connecting to the BRM software. For example: ip server1 12006.

    Note: The protocol must be set to ip.

    InputValidation

    Specifies whether to validate the input XMLRecord:

    • true: The adapter validates the input XMLRecord against the opcode schema.

    • false: The adapter does not validate the input XMLRecord.

    The default is false.

    This overrides any other validation parameter specified in the WSDL file. For information about setting the validation parameters in the WSDL file, see "Defining a Web Service".

    OutputValidation

    Specifies whether to validate the output XMLRecord:

    • true: The adapter validates the output XMLRecord against the opcode schema.

    • false: The adapter does not validate the output XMLRecord.

    The default is false.

    This overrides any other validation parameter specified in the WSDL file. For information about setting the validation parameters in the WSDL file, see "Defining a Web Service".

    LoginType

    Specifies the authentication method:

    • 1: The adapter logs in to BRM by using the specified login name and password.

    • 0: The adapter logs in to BRM by using the specified service type and POID ID.

    The default is 1.

    UserName

    Specifies the login name the adapter uses for logging in to the BRM software.

    Note: This entry is required only if LoginType is set to 1.

    Password

    Specify the password the adapter uses for logging in to the BRM software.

    Note: This entry is required only if LoginType is set to 1.

    PoidID

    Specifies the POID. This entry should be set to 1.

    If the JCA Resource Adapter is deployed under a brand, set PoidID to the account POID of the brand log in.

    ServiceType

    Specifies the service the adapter uses to log in to the BRM software.

    The default is /service/pcm_client.

    BRMConnectionPoolMaxSize

    Specifies the maximum number of connections the Connection Pool can create.

    BRMConnectionPoolMinSize

    Specifies the minimum number of connections created by the Connection Pool when the pool is initialized.

    BRMConnectionPoolTimeout

    Specifies the maximum amount of time in milliseconds that a connection request is queued.

    BRMConnectionPoolMaxIdleTime

    Specifies the maximum amount of time in milliseconds that a free connection in the Connection Pool can be idle. If a free connection is idle for a time greater than or equal to BRMConnectionPoolMaxIdleTime, the connection is removed from the pool.

    Note: Only the connections created after the limit set by BRMConnectionPoolMinsize is reached are verified for the idle time; if the condition is met, the connection is removed from the pool.

    InteractionTimeZone

    Specifies the time zone of the date fields in which the JCA Resource Adapter sends the date fields to the AIA components. The valid values are UTC and LOCAL. The default is UTC.

    For AIA 2.5 and later systems, do not change the default value. For AIA 2.4 and earlier systems, set the value to LOCAL.

    MaxRequestListSize

    Specifies the maximum number of connection requests the Connection Pool can queue before returning a NAP_CONNECT_FAILED error.

    Typically, the requests are queued when all the connections in the Connection Pool are occupied.

    MultiDB

    Specifies whether to enable connections to multiple databases:

    • true: Enables connections to multiple databases.

    • false: Disables connections to multiple databases.

    When the MultiDB connection factory entry is set to true, you do not need to supply the target database number; the adapter automatically opens transactions on the correct database and generates an error if a transaction attempts to manipulate data across databases

    AverageOpcodeCount

    Specifies the average number of opcode calls per thread.


  2. Save and close the file.

You have successfully configured the adapter to connect to BRM.

Configuring Java Logging in Oracle WebLogic Server

The JCA Resource Adapter supports Java Unified Logging (JUL), which allows the adapter to use the Java Unified Logging library.

Creating a Startup Class

To create a Startup class:

  1. Copy the weblogic_startup.jar file provided with the installation package to Domain_Home/lib.

  2. Log in to the WebLogic Server Administration Console. The default is:

    http://localhost:8001/console
      
    
  3. Click Lock and Edit.

  4. In the Domain Structure tree, expand Environment and then click Startup and Shutdown classes.

    The Startup and Shutdown Classes pane appears.

  5. Click New.

    The Configure a New Startup or Shutdown Class: Class Type pane appears.

  6. Select Startup Class and click Next.

    The Configure a New Startup or Shutdown Class: Startup Class Properties pane appears.

  7. In the Name field, enter BRMStartupClass.

  8. In the Class Name field, enter oracle.tip.adapter.brm.BRMLoggerStartUP.

  9. Click Next.

    The Configure a New Startup or Shutdown Class: Select Targets pane appears.

  10. From the Servers list, select the server on which to deploy the class and click Finish.

    The Startup and Shutdown Classes pane appears.

  11. Click BRMStartupClass.

    The Settings for BRMStartupClass pane appears.

  12. Select Run Before Application Deployments and Run Before Application Activations and click Save.

  13. Click Activate Changes.

  14. Restart WebLogic Server to apply the changes.

By default, log files will be created in the Domain_Home/logs/BRMAdapterLogs directory.

Changing the Java Logging Level in Oracle WebLogic Server

You change the logging level by using JConsole.

  1. Go to the WebLogic_home/jdk160_05/bin directory and enter the following command:

    jconsole
      
    

    The New Connection dialog box appears as shown in Figure 3-1.

    Figure 3-1 New Connection Dialog Box

    Description of Figure 3-1 follows
    Description of "Figure 3-1 New Connection Dialog Box"

  2. Select Remote Process, enter the WebLogic Server host name and port number, enter your user name and password, and then click Connect.

    Note:

    When WebLogic Server is running on the same system, you can use Local Process without authentication. The Local Process list shows the WebLogic Server process name and PID.

    The Java Monitoring and Management Console pane appears.

  3. Click the MBeans tab.

  4. In the MBean tree, expand java.util.logging, then expand Attributes, and then select LoggerNames.

  5. Copy the oracle.tip.adapter.brm.BRMConnectionFactory line.

  6. In the MBean tree, expand java.util.logging and then select Operations.

    The Operation invocation pane appears.

  7. In the void setLoggerLevel p0 and p1 fields, paste the logger name and log level that you copied in step 4.

  8. Click setLoggerLevel, which updates the log level.

  9. Close Java Monitoring and Management Console.

For more information about JConsole, access the Java documentation at: http://download.oracle.com/javase/6/docs/technotes/guides/management/jconsole.html.

Deploying and Connecting the BRM JCA Adapter on Oracle GlassFish Server

To deploy and configure the JCA adapter on Oracle GlassFish Server, perform these tasks:

Configuring the GlassFish Server

To configure the GlassFish Server:

  1. Set the PATH environment variable to Glassfish_Home/bin, where Glassfish_Home is the directory in which the GlassFish software is installed.

  2. Copy the orabpel.jar file located in the BRM_Home/apps/brm_integrations/jca_adapter/dependentjars directory to the Glassfish_Home/glassfish/domains/Domain_Name/lib directory, where Domain_Name is the name of the home directory for the domain you are configuring.

  3. Copy the xmlparserv2.jar file located in the BRM_Home/apps/brm_integrations/jca_adapter/dependentjars directory to the Glassfish_Home/glassfish/domains/Domain_Name/lib/applibs directory, where Domain_Name is the name of the home directory for the domain you are configuring.

Deploying and Configuring JCA Resource Adapter on the GlassFish Server

To deploy and configure JCA Resource Adapter on the GlassFish Server:

  1. Start the GlassFish Server domain, if it is not already started.

  2. Run the following command:

    asadmin deploy --libraries xmlparserv2.jar BRM_Adapter_Directory/OracleBRMJCA15Adapter.rar
      
    

    where BRM_Adapter_Directory is the path to the directory where the OracleBRMJCA15Adapter.rar file is located.

  3. Start the GlassFish Server Administration Console.

  4. Create a connector connection pool for JCA Resource Adapter. For more information on creating a connector connection pool, see the Oracle GlassFish Server Help.

  5. Create a Java Naming and Directory Interface (JNDI) connector resource for JCA Resource Adapter. For more information on creating a JNDI connector resource, see the Oracle GlassFish Server Help.

  6. Set the visibility of the JCA Resource Adapter classes to global by running the following command:

    asadmin set server.connector-service.class-loading-policy="global"
      
    
  7. Set the log level for JCA Resource Adapter to FINEST by running the following command:

    asadmin set-log-levels oracle.tip.adapter.brm=FINEST
    

Note:

JCA Resource Adapter logs are stored in the Glassfish_Home/glassfish/domains/Domain_Name/logs/server.log file.

Setting Up JCA Resource Adapter to Support Custom Opcodes

You can enable JCA Resource Adapter to support custom opcodes.

To enable JCA Resource Adapter to support custom opcodes:

  1. Run the parse_custom_ops_fields Perl script, which creates the CustomOp.java class in the Java default package.

    For more information about the script, see the BRM documentation.

  2. Verify that the CustomOp.java file contains the following:

    • The opcode-name-to-opcode-number mapping for all the custom opcodes in the class

      Important:

      Verify that the mapping includes the full name of each opcode. If any opcode name is truncated, replace the truncated name with the full name.
    • The opToString method, which converts opcode numbers to opcode names

    • The stringToOp method, which converts opcode names to opcode numbers

    For example:

    public class CustomOp {
      
    public static final int Custom_Opcode_Name = Custom_Opcode_Number;
      
    public static String opToString( int op ) {
    -------
    }
    .
    public static int stringToOp( String op ) { 
    -------
    }
    .
    }
    .
      
    
  3. Create a JAR file that includes the CustomOp.java class.

  4. Make the JAR file available to JCA Resource Adapter at run time by doing one of the following:

    • If you have not deployed the adapter, put the JAR file in BRM_Home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar

      The JCA Resource Adapter package will then contain the custom opcode JAR file created in step 3 along with other JAR files such as pcm.jar, pcmext.jar and OracleBRMJCA15Adapter.jar.

    • If you have deployed the adapter, put the JAR file in the adapter's working directory on the application server.

      For Oracle application servers, the working directory is Oracle_Home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName.

Using the BRMAdapterServletClient Application

Use the BRMAdapterServletClient application to test the JCA Resource Adapter's configuration and connectivity to BRM. The application allows you to provide input to an opcode and view its output.

To set up the BRMAdapterServletClient application, you must deploy and configure it on your Oracle Application Server system.

Note:

Make sure the BRM JCA Resource Adapter is deployed first, because BRMAdapterServletClient uses classes from the adapter.

Deploy the BRMAdapterServletClient application on Oracle Application Server by using either Oracle Application Server ASC or the Oracle admintool.jar file. When deploying the application, make sure you perform the following:

  • Copy the BRMAdapterServletClient.war file from the BRM_Home/apps/brm_integrations/jca_adapter/BRMAdapterServletClient directory to a location that is accessible to the adapter deployment tool.

  • Specify to deploy BRMAdapterServletClient in the same instance as that of the BRM JCA Resource Adapter.

  • Upload the BRMAdapterServletClient.war archive file.

  • Specify that BRMAdapterServletClient is dependent on the oracle.bpel.common shared library.

After the application is deployed, you can begin using it to run and test the adapter. You can access the application's default page at the following URL:

http://HostName:PortNumber/BRMAdapterServletClient
  

where HostName is the host name of the machine where the application is deployed and PortNumber is the port where the application is deployed.