How to Set the Trace Level of Oracle JCA Adapters

ADAPTER Life-Cycle Management 2-43 Figure 2–15 The Log Configuration Page For more information, see Section 2.25, Viewing Adapter Logs .

2.25 Viewing Adapter Logs

You can view the logs for Oracle JCA Adapters as follows: ■ Oracle JCA Adapters and Oracle Adapter for Oracle Applications: These adapters implement the LogManager interface of the JCA Binding Component, which redirects log files in the Oracle Diagnostic Logging ODL format. For both outbound and inbound interactions, the log files are redirected to the soa-diagnostic.log file. The log files for the Oracle SOA Suite that is deployed to the server-soa managed server are located in: MW_HOMEuser_projectsdomainsdomain_ nameserversserver-soalogssoa-diagnostic.log For more information about searching and viewing log files, see Oracle Fusion Middleware Administrators Guide. ■ Packaged-application adapters: These adapters do not implement the LogManager interface because it is not part of the J2CA 1.5 standard. Therefore, for system components the log outputs are redirected to ORACLE_INSTANCE \diagnostics\logs\component_type\component_ name. For outbound interactions, the logs are directed to the same location. On the other hand, for inbound interactions, logs are redirected to soa-diagnostic.log. Note: To ensure that log levels persist across component restarts, select Loggers With Persistent Log Level State from the View list. By default, the log level is set for runtime loggers. Runtime loggers do not persist across component restarts. 2-44 Oracle Fusion Middleware Users Guide for Technology Adapters ■ Legacy adapters: In addition to the J2CA resource adapter, legacy adapters consists of Oracle Connect, which consists of native adapters for communicating with the mainframe application and data stores. Oracle Connect logs can be viewed using Oracle Studio, which is the mainframe adapter design-time tool and Oracle Connect management tool. Oracle Connect generates various types of logs, such as the daemon log, workspace log, and server process log. For more information, see Section 2.24, Setting the Trace Level of Oracle JCA Adapters .

2.26 Creating a Custom Adapter

You can configure a Custom JCA Adapter wizard as a generic adapter wizard within the JDev IDE that reads and displays its interactionactivation specs, properties and default values from a configuration file. The wizard enables you to select the specs, override the default property values, and add new properties. The Custom Adapter wizard has several purposes: ■ You can use the Custom Adapter Wizard on an as-is basis to support custom runtime adapters. You only need to supply or extend the Custom Adapter configuration file, customAdapter-config.xml to use the Custom Adapter. ■ You can modify or extend the Custom Adapter classes if you want to create a more specific adapter for example, you can change the text to match your adapter ■ You can use the Custom Adapter wizard to see a simple example of how to develop a new adapter wizard by using the JCA Adapter framework and by hooking into the SCAEndpoint interface. After the SOA jdev extension is installed, the Custom Adapter java source files can be found in JAVA_HOME jdeveloperintegrationadapterssamplescustom

2.26.1 Configuring a Custom Adapter

When you select SOA as an installable option with JDev, by default the Custom Adapter is not available. To ensure that the Custom Adapter is available, edit theJDEV_HOME\jdeveloper\integration\seed\soa\configuration\ soa-config.xml file, search for custom, and uncomment its adapterType element. The JDEV Component Palette displays the Custom Adapter for the SOA Diagram. The JDEV_HOME\jdeveloper\integration\seed\soa\configuration\ customAdapter-config.xml file contains the detailed options for the Custom Adapter connection-factory location, interaction-spec className, activation-spec className, and properties. The properties within an activation-spec are properties that are specific to an inbound adapter. The properties within an interaction-spec are the properties specific to an outbound adapter. The property values are the default values shown by the Custom Adapter. See the screenshots below for examples. You can modify the contents of the customAdapter-config.xml to match options needed by your custom runtime adapter. For example, you can change all property names and their default values, add new properties, or add multiple activation or interaction specs. The displayResourceKey and resourceBundle attributes are optional. If an activation-spec, interaction-spec, or property element has a displayResourceKey,