Oracle JCA Adapters Log File Locations

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-71 For Partitioned Distributed Topics, configure the JMS adapter to use unrestricted clientid and a shared subscription policy that is, set SubscriptionSharingPolicy property to SHARABLE, which are the default settings. Also, to ensure subscription name uniqueness, set the TopicMessageDistributionAll property to true default value is false. This property can be defined by setting the FactoryProperties property of the connection instance in weblogic-ra.xml. An example usage snippet of connection instance from weblogic-ra.xml is: property nameFactoryPropertiesname valueClientID=SOACLient2; TopicMessageDistributionAll=truevalue property For Replicated Distributed Topics, configure the JMS adapter to use unrestricted clientid and shared subscription policy as well that is, set SubscriptionSharingPolicy property to SHARABLE, which are the default settings. As with the Partitioned Distributed Topic case, to achieve subscription name uniqueness, the adapter requires that the property TopicMessageDistributionAll be set to true the default value is false. The property can be defined by setting the FactoryProperties property of the connection instance in weblogic-ra.xml. An example usage snippet of connection instance from weblogic-ra.xml for a local cluster is shown above. For Replicated Distributed Topics to guarantee one copy per adapter endpoint, the message selector NOT JMS_WL_DDForwarded needs to be used when defining an activation spec, as shown in the following .jca file example: activation-spec className=oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec property name=DestinationName value=jmsDemoInTopic property name=UseMessageListener value=false property name=DurableSubscriber value=dsub1 property name=MessageSelector value=NOT JMS_WL_DDForwarded property name=PayloadType value=TextMessage activation-spec Note, though, that this type of configuration is highly inefficient and not recommended, because it distributes messages to all consumers, but then does the rejection on the consumer end. To achieve better performance it is recommended to use Partitioned Distributed Topics. Outbound - Distributed Topics There is no change to adapter behavior when producing message to a distributed topic. AvailableUnavailableFailure notification shall have no impact on the working of outbound adapter reference. The message is produced by creating a MessageProducer for the Distributed Destination and not for a specific member.

5.10.2.5 Oracle JCA Adapters Log File Locations

You can view the logs for Oracle JCA Adapters as follows: Oracle JCA Adapters and Oracle Adapter for Oracle Applications: For both outbound and inbound interactions, the log files are redirected to the soa-diagnostic.log file.The Note: Oracle BAM does not support durable distributed topics, but it does support non-durable transient distributed topics. 5-72 Oracle Fusion Middleware High Availability Guide log files for Oracle Fusion Middleware SOA Suite that is deployed to the server-soa managed server are located in: MW_HOMEuser_projectsdomainsdomain_ nameserversserver-soalogssoa-diagnostic.log Packaged-application adapters: These adapters do not implement the LogManager interface because it is not part of the J2CA 1.5 standard. Therefore, for OPMN-managed 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. 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.

5.11 Oracle Business Activity Monitoring and High Availability Concepts

The information in this section guides you through the issues and considerations necessary for configuring Oracle BAM for high availability.

5.11.1 Oracle Business Activity Monitoring Single-Instance Characteristics

Oracle BAM provides the tools for monitoring business services and processes in the enterprise. It allows correlating of market indicators to the actual business process and to changing business processes quickly or taking corrective actions if the business environment changes. Oracle Business Activity Monitoring Oracle BAM provides the necessary tools and runtime services for creating dashboards that display real-time data inflow and define rules to send alerts under specified conditions. Figure 5–31 illustrates the main services and dependencies that characterize an Oracle BAM instance.