Oracle SOA 12c. 12.2.1.3. Auto Purge

Auto Purge

Auto Purge can be used to free up the database from the older data associated with flow instances, adapter reports and fault alerts.

·         Navigate to the SOA Infrastructure Menu and Right Click

·         Navigate to SOA Administration and then Auto Purge

·         

•  Click on Auto Purge:-

• ·         Click on Enable and then enter the Schedule for the job

• ·         Click on Apply.

Oracle® Fusion Middleware SOA-11g Release 2 (11.1.1.7) Configure SAP IDocs On Oracle SOA-B2B platform

Oracle® Fusion Middleware SOA-11g Release 2 (11.1.1.7) Configure SAP IDocs On Oracle SOA-B2B platform

This BLOG thread discusses the steps for Oracle B2B setup for SAP IDocs. The thread discusses the use of

• Oracle EDIFECS Spec Builder Version 7.0.5
• Oracle B2B Console for version 11.1.1.7  

Steps for building the ECS file, the Parser and XSD

• Start the B2B Document Editor 
• Click on File->New
• Choose Positional Flat File
• Choose Blank Positional

• Press Next
• You should be able to see a blank PFF guideline

• Click on File-> Import
• Select the SAP IDoc Guideline. Press next

• Ensure the IDoc type is correct.

• Please see below when the IDocs file is sucessfully imported

• Click on File
• Click Save
• Give the Name to the ECS File

• On the Analyzer /  Data window, open a sample Data File

• On the Analyzer Wizard, verify the record terminator, Un-check the "First record in the guideline starts a new message and press Next, Press Finish in the subsequent window.

• For each tag in the sample data displayed on the Analyzer / Data window, verify the tags, in the event the tags are different, 

• Select the Record ID whose tag needs to be set, 

• Click Edit, set Tag Value E2EDK14 (in this case). Click Set Current. Click Close

• Ensure the Tag field is set to "Value" and  Tag Value is set to "E2EDk14"

• Repeat this for all the elements.

Generate the Parser File

• Click on Edit.Click on Generate Parser Schema

• Ensure that the Record Terminator is correct and click on the browse button and give tne name to the parser file.

• Give the name to the parser file and Click o Save

• Copy the parser ecs  file in the directory $Oracle_SOA_Home\soa\thirdparty\edifecs\XEngine\config\schema (for eg. - D:\OFMW11g\PS3MWHome\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\config\schema)

• Add an entry for this parser ecs in $Oracle_SOA_Home\soa\thirdparty\edifecs\XEngine\config\XERegistry.xml

• To add this entry, edit the XERegistry.xml in a text editor and add below “Positional flat parser schemas”

Oracle SOA 11.1.1.6 Create RMA (Return Merchandise Authorization) using Oracle SOA B2B on AS2 Part 2

Oracle SOA 11.1.1.6 Create RMA (Return Merchandise Authorization) using Oracle SOA B2B on AS2 Part 2

Please refer to my earlier post on Generation of 180 B2B artifacts by navigating to the thread
Oracle SOA 11.1.1.6 Create RMA (Return Merchandise Authorization) using Oracle SOA B2B on AS2 Part 1

This thread discuss configuration of the AS2 communication channel using B2B console. To navigate to the SOA B2B console , please use the URL http://hostname:port/b2bconsole where hotname is the name of the host where Oracle SOA stack with b2B is installed, port is the port where the SOA Managed Server is listening.

1.) Click on administration.

2.) Click on document.

3.) Click on Document Types (EDI X12)

4.) Create a Version Type. (4010)

5.) Create a Document Type 180.

6.) Create Document Definition  by using the XSD and ECS file that were created using document Editor.

Oracle SOA 11.1.1.6 Create RMA (Return Merchandise Authorization) using Oracle SOA B2B on AS2 Part 1

Oracle SOA 11.1.1.6: Create  RMA (Return Merchandise Authorization) using Oracle SOA B2B on AS2 (Part 1)

A return merchandise authorization (RMA) or return goods authorization (RGA) is the process of having a product repaired or replaced in order to receive a refund or credit for another product from the same retailer or corporation. This thread discusses creation of X12 180 ECS file Version 4010 using Oracle B2B Document Editor Tool version 7.0.5.

• Using the B2B document Editor Shortcut, start the B2B document Editor. Click File->New

• Choose X12 option under EDI, Choose Version 4010, Choose 180-Return Merchandise Authorization and Notification. Click Next.

• Click Finish

• Create an XSD so that we can configure B2B on Oracle SOA 11.1.1.6 stack. 
• Click File. Choose Export.

• In the Export Wizard, choose Oracle 2.0. Press Next.

• Choose the folder where you want the XSD file to be created and Press Next.

• Click Finish.

The ECS File and XSD file is ready. We we use these files in configuring the SOA - B2B using B2b Console in my next post.

Oracle SOA Suite 11.1.1.6: Monitoring SOA Composite Behavior with SQL Queries

Oracle SOA Suite 11.1.1.6: Monitoring SOA Composite Behavior with SQL Queries


The standard information obtained from Oracle Enterprise Manager Fusion Middleware Control might not be sufficient and adequate for fine grained monitoring. By querying some core product tables in the [PREFIX]_SOAINFRA schema such as the COMPOSITE_INSTANCE, CUBE_INSTANCE, and MEDIATOR_INSTANCE tables, you can get detailed metrics that include success/failure counts, composite instance performance, and durations of invokes as well. Here, we provide two main
queries to obtain performance metrics on BPEL processes and Mediator services, specifically the duration of time that each component took. Though Oracle typically does not recommend querying the product tables directly (since the structure of the tables may change after a patch or upgrade), note that these queries below run fine on Oracle SOA Suite 11g PS3 (11.1.1.4), PS4 (11.1.1.5), and PS5 (11.1.1.6).


The following query outputs a list of all BPEL component instances, their state,
average, minimum, and maximum durations, as well as counts:

SELECT DOMAIN_NAME PARTITION,COMPONENT_NAME,
DECODE(STATE,'1','RUNNING','5','COMPLETED','6',
'FAULTED','9','STALE') STATE,
TO_CHAR(AVG((TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATECREATION_
DATE),12,2))*60*60) +
(TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATE-CREATION_DATE),15,2))*60) +
TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATECREATION_
DATE),18,4))),'999990.000') AVG,
TO_CHAR(MIN((TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATECREATION_
DATE),12,2))*60*60) +
(TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATE-CREATION_DATE),15,2))*60) +
TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATECREATION_
DATE),18,4))),'999990.000') MIN,
TO_CHAR(MAX((TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATECREATION_
DATE),12,2))*60*60) +
(TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATE-CREATION_DATE),15,2))*60) +
TO_NUMBER(SUBSTR(TO_CHAR(MODIFY_DATECREATION_
DATE),18,4))),'999990.000') MAX,
COUNT(1) COUNT
FROM CUBE_INSTANCE
GROUP BY DOMAIN_NAME, COMPONENT_NAME, STATE
ORDER BY COMPONENT_NAME, STATE


The following query displays a list of all Mediator component instances, their state,
average, minimum, and maximum durations, as well as counts:

SELECT SUBSTR(COMPONENT_NAME, 1, INSTR(COMPONENT_NAME,'/')-1)
PARTITION,
SUBSTR(COMPONENT_NAME, INSTR(COMPONENT_NAME,'/')+1,
INSTR(COMPONENT_NAME,'!')-INSTR(COMPONENT_NAME,'/')-1) COMPONENT,
SOURCE_ACTION_NAME ACTION,
DECODE(COMPONENT_STATE,'0','COMPLETED','2',
'FAULTED','3','ABORTED','4','RECOVERY
NEEDED','8','RUNNING','16','STALE') STATE,
TO_CHAR(AVG((TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIMECREATED_
TIME),12,2))*60*60) +
(TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIME-CREATED_TIME),15,2))*60) +
TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIMECREATED_
TIME),18,4))),'999990.000') AVG,
TO_CHAR(MIN((TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIMECREATED_
TIME),12,2))*60*60) +
(TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIME-CREATED_TIME),15,2))*60) +
TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIMECREATED_
TIME),18,4))),'999990.000') MIN,
TO_CHAR(MAX((TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIMECREATED_
TIME),12,2))*60*60) +
(TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIME-CREATED_TIME),15,2))*60) +
TO_NUMBER(SUBSTR(TO_CHAR(UPDATED_TIMECREATED_
TIME),18,4))),'999990.000') MAX,
COUNT(1) COUNT
FROM MEDIATOR_INSTANCE
GROUP BY COMPONENT_NAME, SOURCE_ACTION_NAME, COMPONENT_STATE
ORDER BY COMPONENT_NAME, SOURCE_ACTION_NAME, COMPONENT_STATE

How Oracle WSM Locates Keystore And Key Passwords

How Oracle WSM (Oracle Web Service Manager) Locates Keystore And Key Passwords

Oracle WSM expects keystore and key passwords to be in the Credential Store Framework (CSF). Here is how it works.

• A JKS keystore file is protected by a keystore password.
• A keystore file consists of zero or more private keys, and zero or more trusted certificates. Each private key has its own password, (although it is common to set the key passwords to be the same as the keystore password). Oracle WSM needs to know both the keystore password and key password.
• The CSF consists of many maps, each with a distinct name. Oracle WSM only uses the map oracle.wsm.security.
• Inside each map is a mapping from multiple csf-key entries to corresponding credentials. A csf-key is just a simple name, but there can be many different types of credentials. The most common type of credential is a password credential which is primarily comprised of a username and a password.
  Oracle WSM refers to the following csf-keys inside the oracle.wsm.security map:
  
  • keystore-csf-key - This key should contain the keystore password. The username is ignored.
  • enc-csf-key - This key should contain the encryption key alias as the username, and the corresponding key password.
  • sign-csf-key - This key should contain the signature key alias as the username, and the corresponding key password.
  In addition to these csf-keys, you should add a csf-key entry for every new private key that you want Oracle WSM to use, for example when you want to specify signature and encryption keys in configuration overrides.

Figure  illustrates the relationship between the keystore configuration in the OPSS, the oracle.wsm.security map in the credential store, and the Oracle WSM Java keystore.

Figure 10-8 Oracle WSM Keystore Configuration for Message Protection

As shown in the figure:

• The keystore.csf.map property points to the Oracle WSM map in the credential store that contains the CSF aliases. In this case keystore.csf.map is defined as the recommended name oracle.wsm.security, but it can be any value.
• The keystore.pass.csf.key property points to the CSF alias keystore-csf-key that is mapped to the username and password of the keystore. Only the password is used; username is redundant in the case of the keystore.
• The keystore.sig.csf.key property points to the CSF alias sign-csf-key that is mapped to the username and password of the private key that is used for signing.
• The keystore.enc.csf.key property points to the CSF alias enc-csf-key that is mapped to the username and password of the private key that is used for decryption.
  
  

AIA 11.1.1.6 Develop and Implement a Simple Inbound B2B Flow

AIA 11.1.1.6 Develop and Implement a Simple Inbound B2B Flow




The following figure shows the high-level steps involved in developing a simple inbound business-to-business (B2B) flow from an application to trading partners using Oracle Application Integration Architecture (AIA).

Step 1: Identifying the B2B Document and Analyzing Requirements

1. The source and targets in the mapping are reversed. The B2B document received from trading partners is the source of the mapping. The AIA Enterprise Business Message (EBM) is the target of the mapping.
2. At the end of this step:
1. The B2B document is defined in Oracle B2B.
2. The XML schema of the B2B document is uploaded in the AIA Metadata Repository.
3. The Enterprise Business Object (EBO) and the EBM to be used in the integration are identified. 
4. Functional mapping between the B2B document and the AIA EBM is complete.

Step 2: Adding Inbound Routing Rules to an AIA B2B Interface

1. In inbound B2B document flows, the AIAB2BInterface service listens for new B2B documents received by Oracle B2B and routes them to the requester B2B services.

Step 3: Developing a New Requester B2B Connector Service

The key function provided by a requester B2BCS is to enable inbound B2B document

integration by performing the following tasks:

■ Receive B2B documents sent by trading partners from Oracle B2B.

■ Transform B2B documents into AIA EBMs.

■ Use EBMs as request payloads to invoke AIA Enterprise Business Services (EBSs).

Step 4: Developing or Extending an Existing Enterprise Business Service

1. The next step,   is to develop a new EBS or use an existing EBS that is invoked by the requester B2BCS.

Step 5: Developing or Extending an Existing Provider ABCS

1. The next step,   is to develop a new or extend an existing provider ABCS. The provider ABCS processes the AIA EBM by invoking application APIs or web-services.

Step 6: Configuring Oracle B2B and Defining Trading Partner Agreements

1. The next step, as shown in Figure 18–21, is to create trading partner agreements in Oracle B2B.

Step 7: Deploying and Configuring AIA Services

1. The next step, is to deploy the AIA services. You can deploy the services to a target Oracle SOA server using Oracle JDeveloper.

Step 8: Testing and Verifying

1. The next step, is to test and verify. Before you go live with your B2B integration flows with your trading partners, we recommend that you complete a sequence of tests for your newly developed or deployed AIA services, which make up the B2B integration flow.

Step 9: Going Live and Monitoring

Setup Oracle SOA B2B for Secured payload (Digitally Signed & Encrypted) using AS2 2.0 protocol

For a large EDI initiative MindTelligent Team was involved in, the assignment was to setup a Oracle B2B exchange for payload using AS 2.0 protocol  This blog discusses the steps to configure Oracle SOA suite 11.1.1.4 B2B server to exchange secured payload (Digitally Signed and Encrypted) using AS2.0 protocol. The post assumes that the user has some prior knowledge of Oracle SOA B2B servers

• Setup Two WAY SSL on Weblogic 10.3.4 using the link.
• Ensure that the B2B console can be accessed by using the https://hostname:7002/b2bconsole

• Document Definition: as2XMLOrder_def 
• In this example, we are processing a XML using AS  2.0. The option we choose is
  "XML"
• Identification Expression://*[local-name()='PurchaseOrder']

Setting up "Delivery Channel" for you outbound payloads.

• Click on Partners-->Channels
• Select Protocol as AS2-2.0
• Enter Transport Protocol Parameters
• URL: http://hostname:port/b2b/httpReceiver
• User Name: Weblogic user name of remote server
• Password: Password of the remote server

• Security Attributes
•  Ack Signed Checked
• Message Signed Checked
• Message Encrypted Signed

Develop a composite to initiate the process. Ensure that the following assignments are made in the composite

<assign>
            <copy target="$out.property.b2b.fromTradingPartnerId"
                  expression="'AskMind'"/>
            <copy target="$out.property.b2b.toTradingPartnerId"
                  expression="'DST'"/>
            <copy target="$out.property.b2b.documentTypeName"
                  expression="'as2XMLOrderType'"/>
            <copy target="$out.property.b2b.documentProtocolRevision"
                  expression="'as2XML_Version_1.0'"/>
          </assign>

For questions, comments and feedback,  please contact:
 Harvinder Singh Saluja

Setup Oracle SOA B2B for ebXML documents using ebMS 2.0 protocol

For a large EDI initiative MindTelligent Team was involved in, the assignment was to setup a Oracle B2B exchange for ebXML using ebMS 2.0 protocol  This blog discusses the steps to configure Oracle SOA suite 11.1.1.4 B2B server to exchange ebXML using ebMS 2.0 protocol. The post assumes that the user has some prior knowledge of Oracle SOA B2B servers

• Set up the document definition.
• Document Protocol Version: ebXML_Version_1.0
• Document Type: ebXMLOrderType
• Action Name ebXMLOrderAction
• Service Name ebXMLOrderService
• Service Type ebXMLOrderServiceType
• From Role AskMind
• To Role DST

• Document Definition: ebXMLOrder_def 
• In this example, we are processing a flat file using ebMS 2.0. The option we choose is
  "Flat"
• Identification Start Position: 1 (Depending on identification of your flat file)
• Identification End Position: 1 (Depending on identification of your flat file)
• Identification Value: C  (Depending on identification of your flat file)

Setting up "Delivery Channel" for you outbound payloads.

• Click on Partners-->Channels
• Select Protocol as ebMS-2.0
• Enter Transport Protocol Parameters
• URL: http://hostname:port/b2b/httpReceiver
• User Name: Weblogic user name of remote server
• Password: Password of the remote server

• Channel Attributes
• Ack Mode Async

Develop a composite to initiate the process. Ensure that the following assignments are made in the composite

<assign>
            <copy target="$out.property.b2b.ebms.Service"
                  expression="'ebXMLOrderService'"/>
            <copy target="$out.property.b2b.ebms.ServiceType"
                  expression="'ebXMLOrderServiceType'"/>
            <copy target="$out.property.b2b.ebms.action"
                  expression="'ebXMLOrderAction'"/>
            <copy target="$out.property.b2b.fromTradingPartnerId"
                  expression="'AskMind'"/>
            <copy target="$out.property.b2b.toTradingPartnerId"
                  expression="'DST'"/>
            <copy target="$out.property.b2b.documentTypeName"
                  expression="'ebXMLOrderType'"/>
            <copy target="$out.property.b2b.documentProtocolRevision"
                  expression="'ebXML_Version_1.0'"/>
              <copy target="$out.property.b2b.action"
                  expression="'ebXMLOrderAction'"/>
          </assign>

For questions, comments and feedback,  please contact:
 Harvinder Singh Saluja