SOA Cloud 12c GIT Repository

When a project is created, you can choose to initialize the project with one project Git repository for the project. A Maven repository is also created. If required, you can add more project Git repositories, external Git repositories, import Git repositories, and configure auto-cleanup of the to the project Maven repository.

This BLOG discusses steps to create the GIT repository :- 

• Login to the Oracle Developer Cloud Services and Select Create New Project.

• Click Next

• Choose the option to create a Empty Project
• Choose Wiki Markup as Mark Down

• A few seconds of provisioning later the Project will be accessible – navigate to the Code Section of the Developer Services Project and hit the New Repository button. This will start the process to create a new git repository. Make sure not to initialize it, but simply create an Empty Repository.

• Project successfully created
• The Next Step is to create a GIT Repository
• Enter the Name and Description
• Choose the option to create "Empty Repository"
• Click Create

• 
  

Calling Oracle SOA Cloud REST service from SOAP UI

On creating a SOAPUI project using the WADL, for a REST Service deployed on SOACLD. The WADL import process throws an SSL handshake exception.

This exception can be resolved by adding the following properties to the SOAPUI VM.

• Navigate to the directory 

<SOAPUI_HOME>\ bin\SoapUI-5.3.0.vmoptions    

For Example: 
C:\Program Files\SmartBear\SoapUI-5.3.0\bin\SoapUI-5.3.0.vmoptions

• Edit the file and add

-Dweblogic.security.SSL.minimumProtocolVersion=TLSv1.0

-Dsoapui.https.protocols=SSLv3,TLSv1.2

• Restart SOAPUI and the issue will be resolved

SOA 12.2.1. View SOAP Header information.

Default SOA settings do not allow to view SOAP message (header & body)out-of-the-box on the EM Console or in the logs.

In order to see these SOAP conversations for a SOA composite service you can follow below steps: Please note the log file to be checked is OWSM

• Using the Enterprise Manager, attach the management policy named oracle/log_policy to the webservice reference to which the SOAP headers needs to be monitored. 

• Restart the composite

• Check the below log file to view the SOAP messages whenever the webservice call is made.$DOMAIN_HOME/domain_name/servers/mserver_name/logs/owsm/msglogging/diagnostic.log