Friday, 19 July 2013

What are the files creates when DBAdapter Configuration complete in Jdev?

Once the DBAdapter Configuration complete below files will be create:
1. <ServiceName>.wsdl
2. <ServiceName>_table.xsd
3. <ServiceName>_or-mappings.xml
4. <ServiceName>_db.jca
5. <ServiceName>.properties

What is the basic step to troubleshoot the DBAdapter?

1.       The basic step to troubleshoot the adapter is to set the oracle.soa.adapter logger level to Trace: 32(FINEST) in the FMW Console.

2.       Once this configuration is done, reproduce the issues and check the SOA Manager Server log fileMW_HOME/user_projects/domains/<domain_name>/servers/<soa-server>/logs/soa-diagnostic.log …Look for JCABinding and BINDING.JCA-xxxx strings and take actions accordingly.

Thursday, 18 July 2013

What are Mimimum Age, TriggerFilePhysicalDirectory and TriggerFile?

MinimumAge – This parameter specifies the minimum age of files to be retrieved. This enables a   large file to be completely copied into the input directory before it is retrieved for processing. The age is determined by the last modified time stamp

TriggerFilePhysicalDirectory- The directory path where the Oracle File or FTP Adapter   looks for the trigger files.

TriggerFile-The name of the trigger file that activates the inbound Oracle File or FTP   Adapter

About SOA 11g MDS Repository?

About SOA 11g MDS Repository:

1. MDS Facilitates greater re-use of SOA artifacts such as XML Schemas,WSDLs,FaultPolicies,Rule repositories and Service Data Objects(SDOs) among others..

2. MDS can be File based or Database based.

Below are the steps to create MDS in Jdeveloper.
3. MDS is created under <jdeveloper-home>/integration/seed directory.

4. Default folder “soa” is used to store common system soa artifacts.

5. All custom artifacts are supposed to be stored under a folder called “apps”, since this folder already exists in server.

6. Deploy MDS Repository to Weblogic Server.

First, we need to create JAR file bundle to include schemas we need. Then we need to include this jar file into a SOA bundle that can be deployed to the SOA Server.


    Step1: Create Generic Application – MediatorMetaData
In Jdev àApplication àGeneric Application àSay “OK”….Give Application Name as “MediatorMetaData” and choose Directory.

Step2: Create project as “MediatorLib” and choose Directory.

Step3: Right Click on MediatorLib and select NewàDeployment Profile àJAR File.

Step4: Enter mediatorlib as the deployment profile name.

Step5: In the JAR deployment properties dialog, click on Contributors, click on Add button and select appsdirectory from JDeveloper seed location – <jdeveloper_home>/integration/seed/apps and say “OK”.

Step6: Click on Filters and select the schemas you would like to be deployed.
 Click on OK. This completes creation of JAR file. We now need to create an application deployment profile to install these schemas in SOA Server.

Step7: Right click on MediatorMetaData application and select Deploy –> New Deployment Profile. Select “SOA Bundle” as Profile type.

Step8: Enter mediatorlib for Deployment Profile Name. From the properties dialog, open Dependencies and select mediatorlib.

Step9: To deploy MediatorLib to SOA Server, right click on MediatorMetaData and select Deploy –> mediatorlib.

Details on oracle integration cloud.

It Integrates applications across clouds, on-premises and Hybrid. Easy to use for LOB/Apps IT & IT developed integration. Prebuil...