Oracle SOA Cloud: Deploy MDS Artifacts on SOA Cloud Instance using cloud Enterprise Manager

This BLOG thread discusses the steps on deployment of MDS artifacts on SOA cloud instance.

Setup JDeveloper SOA_DesignTimeRepository

JDeveloper 12.2.1 or 12.2.1.2 by default creates the SOA_DesignTimeRepository. This is a file based repository. At MindTelligent, we link this directory to SVN or GIT master repository. It is imperative that we have a main folder /apps and all the artifacts are stored under the apps folder.

On looking at the Design Time Repository closely, the structure looks like as shown below:

To change the location of the directory, simply right click on the  SOA_DesignTimeRepository, and click on Properties.

  
















Please click on the Browse button and choose the folder you wish to select as File based Repository
Please note that you do not select the /apps folder under which all the artifacts are located.

That is it for JDeveloper Setup. You are ready to build your composites.


Deploy the MDS artifacts on SOA cloud

• Log in to your SOA Cloud Instance 
• Navigate to the "SOA Fusion Middleware Control Console"

• Navigate to SOA Infrastructure-->Administration-->MDS configuration

Choose the option to Import the MDS

Please navigate to the folder where the Zip file for the SOA_DesignTimeRepository is located. 

The zip file SHOULD include the /apps folder

EM will display the following message if all the artifacts are successfully uploaded to the  MDS:

Installation of Apache Spark on Windows 10

Apache Spark is an open-source cluster-computing framework. Originally developed at the University of California, Berkeley's AMPLab, the Spark codebase was later donated to the Apache Software Foundation, which has maintained it since. Spark provides an interface for programming entire clusters with implicit data parallelism and fault-tolerance.

Please follow following instructions on installation Apache Spark on Windows 10.

Prerequisites:

Please ensure that you have installed JDK 1.8 or above on your environment.

Steps:

Installation of Scala 2.12.2

• Please Install Scala after downloading it. 
• Scala can be downloaded from here.
• Download will give you a .msi file. Follow instructions and install Scala

Installation of Spark

• Spark Can be downloaded from here
• I am choosing version 2.1.1 prebuit for Hadoop. Please note, I shall be running this without Hadoop.

• Extract the tar file into a folder called c:\Spark
• The contents of the Extract will look like

Download Winutils

• Download Winutils from these links : 64 bits
• Create a folder c:\Spark\Winutils\bin and copy this winutils.exe there
• The folder structure will look like

Setup Environment Variables

• Following environment variables will need to be setup:
• JAVA_HOME: C:\jdk1.8.0_91
• SCALA_HOME: C:\Program Files (x86)\scala\bin
• _JAVA_OPTION: -Xms128m -Xmx256m
• HADOOP_HOME:  C:\Spark\WinUtils
• SPARK_HOME: C:\Program Files (x86)\scala\bin
• Create a folder c:\tmp\hive and give it read/write/execute privileges for all

Test Spark Environment

• Navigate to SPARK_HOME/bin and execute command scala-shell

You should re ready to use Spark

SOA 12c: How to remove folder and Files from MDS

The folder or individual files can be removed from SOA using WLST scripts. WLST scripts can also be used for deployment of MDS. Enterprise Manager can also be used to export and import the MDS.

Please click here to see how to use Enterprise Manager to import and export MDS

However, for deletion, please refer to following steps

On the FMW server, navigate to #ORACLE_COMMON/bin

cd ${ORACLE_HOME}/oracle_common/common/bin

Execute wlst.sh file:

wlst.sh

Give the command

connect('weblogic','password','t3://WeblogicHost:7001') //Please use the Weblogic Admin Server Port here.

Give The Command to remove a specific folder. This command will remove the /app/Test folder.

sca_removeSharedData(' http://soaHost:ManagedServerPort','Test')

sca_removeSharedData(' http://localhost:8001','Test')

You should see following message:

wls:/soainfra/serverConfig/> sca_removeSharedData(' http://localhost:8000','Test')

serverURL =  http://localhost:8000

folderName = Test

user = None

INFO: Creating HTTP connection to host:localhost, port:8000

Enter username and password for realm 'default' on host localhost:8000

Authentication Scheme: Basic

Username: weblogic

Password:

INFO: Received HTTP response from the server, response code=200

---->Remove shared data success.

Give The Command to remove a specific file. This command will remove the file: /apps/Test/SOAPService.wsdl'

deleteMetadata(application='soa-infra',server='soa_server1',docs='/apps/Test/SOAPService.wsdl')

Salesforce: Generate Enterprise WSDL

To generate the metadata and enterprise WSDL files for your organization:

1. Log in to your Salesforce account. You must log in as an administrator or as a user who has the “Modify All Data” permission.
2. From Setup, enter API in the Quick Find box, then select API
3. Click Generate Enterprise WSDL and save the XML WSDL file to your file system.

Oracle Virtual Box Only Showing on 32 Bit Options

While trying to configure the SOA 12c on a VM running on 64 bit O/S, when trying to install Ubuntu Linux we observed that Oracle Virtual Box only shows 32 bit options

• To fix this issue, we need to ensure that in BIOS settings the VM support is enabled
• Hyper -V needs to be disabled. To do this Enter Windows Key + q and type in turn windows features on or off

         Ensure that the Hyper-V is unchecked and restart your machine.

• You should now be able to see all 64 bit options.

Weblogic 10.3.6: Registering the Jersey JAX-RS RI Shared Libraries With Your WebLogic Server Instances

Shared Java EE libraries are registered with one or more WebLogic Server instances by deploying them to the target servers and indicating that the deployments are to be shared. Shared Java EE libraries must be targeted to the same WebLogic Server instances you want to deploy applications that reference the libraries.

When a referencing application is deployed, WebLogic Server merges the shared library files with the application. If you try to deploy a referencing application to a server instance that has not registered a required library, deployment of the referencing application fails with following exception

[Extension-Name: jsr311-api, exact-match: false], [Extension-Name: jersey-bundle, exact-match: false].>

java.lang.ClassNotFoundException: com.sun.jersey.spi.container.servlet.ServletContainer

        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)

        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

        at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)

        at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225)

        at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209)

The following steps show how to deploy the Jersey JAX-RS RI Shared Libraries With Your WebLogic Server Instances.

• Change to the directory C:\WLS10-3-6\Oracle\Middleware\wlserver_10.3\server\bin
• Execute the cmd file setWLSEnv.cmd

•  Execute the command

java weblogic.Deployer -verbose -noexit -source C:\WLS10-3-6\Oracle\Middleware\wlserver_10.3\common\deployable-libraries\jersey-bundle-1.1.5.1.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -password welcome1 -deploy -library

• Execute the command.

java weblogic.Deployer -verbose -noexit -source C:\WLS10-3-6\Oracle\Middleware\wlserver_10.3\common\deployable-libraries\jsr311-api-1.1.1.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -password welcome1 -deploy -library

Weblogic 12.2.1:Java - JMX to get the Server Name and port

 The following section of code discusses how to get the Server Name and Port for the managed server or a cluster where the API is deployed.

     public static Integer getPort() {

       Integer port=null; 

       try {

            InitialContext ctx = new InitialContext();

            String serverName = System.getProperty("weblogic.Name");

            MBeanServer server =

                (MBeanServer)ctx.lookup("java:comp/env/jmx/runtime");

            ObjectName objName =

                new ObjectName("com.bea:Name=" + serverName + ",Type=Server");

            port = (Integer)server.getAttribute(objName, "ListenPort");

            

            ctx.close();

             

            

        } catch (Exception e) {

            e.printStackTrace();

        }

        return port;

    }