Showing posts with label Oracle SOA. Show all posts
Showing posts with label Oracle SOA. Show all posts

Sunday, September 22, 2013

Deploy DVM/Artifacts to MDS



Introduction: 
After reading the heading the first question that strike is wooo!!!! why do we need something to deploy DVM to MDS when we have the DVM local to our SOA project which can be deployed with SAR.

But my dear friends what will happen when you have a same DVM which can be used across several SOA services. Are you going to create a copy of the same DVM across all projects ??

The obvious answer will be No.

Here is a Smart solution for all the above :):).

Create a Separate Project :

Create a separate SOA Project (EMPTY) and create structure (in case you want to create some structure across projects) and copy the DVM inside as shown in the screenshot below:


Now this DVM can be accessed across every project with the below simple function:
dvm:lookupValue("oramds:/apps/test/DVM/ConnectionDetails.dvm","code","SupplierName","value","No Description").
Deployment:
You can have Ant scripts to deploy the project to MDS.
 To use Ant scripts click here 

But if you don’t have time for that then here is a simple solution for that too.

Execute below commands:
     1)   Cd $SOA_Home/common/bin/wlst.sh 
         (for linux environment, Also SOA_HOME is according to your installation).
             
      2)   You will get offline screen. Now you need to execute connect(). You will be asked for the admin username and password.
       

Once you will get connected you will get the below message:

Successfully connected to Admin Server 'AdminServer' that belongs to domain 'my_domain'.

wls:/my_domain/serverConfig>
      3) Now execute the command:

importMetadata(application='soa-infra',server='soa_server1',fromLocation='DVM Location with the same structure as mentioned in docs ',docs='/apps/test/DVM/*.dvm').

e.g.


     4) Now open your MDS connection and there you go with your DVM on MDS :):)



In case of any queries, you are welcome to comment or write us at letslearnoraclesoa@gmail.com 


Cheers,

LetsLearnOracleSOA Team

Tuesday, August 27, 2013

“Caused by: java.lang.UnsupportedClassVersionError: unsupported classversion 51.0”



Error:


“Caused by: java.lang.UnsupportedClassVersionError: unsupported classversion 51.0”

Replication Of Issue: 


When we try to deploy any service which has been developed/Migrated on JDK which is higher than the JDK version used by the server

Error Stack:


[04:04:30 PM] [Deployer:149193]Operation 'deploy' on application 'ServiceName' has failed on 'Server1'
[04:04:30 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application 'ServiceName' on Server1.: Failed to load webapp: ''ServiceName'.war'.
[04:04:30 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: ''ServiceName'.war'
[04:04:30 PM] Caused by: java.lang.UnsupportedClassVersionError: <Package Name> : unsupported classversion 51.0
[04:04:30 PM]   See server logs or server console for more details.
[04:04:30 PM] weblogic.application.ModuleException: Failed to load webapp: ''ServiceName'.war'
[04:04:30 PM] ####  Deployment incomplete.  ####
[04:04:30 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)


Resolution:

  
1)      1) Check the JDK Requirement of the JDeveloper version which is to be installed. Eg. As per Oracle documentation for Jdev 11.1.1.6.0 the JDK shall be JDK_6.0_27 or above.


2)       2) Check the server jdk version.To do the same t go to location WL_HOME/common/bin/commEnv.cmd ad Look for lines like the ones below (examples are from a WLS install on a Unix machine)

#JAVA_USE_64BIT, true if JVM uses 64 bit operations.


3)      3) Install JDK version which is either server version or lower than that version and then build/migrate your service.
  


Reference: To find the JDK version of your server click here.