Tuesday, 1 July 2014

Oracle Fusion Middleware 12c New Features

1.       OSB will be no longer be part of Eclipse. It has been integrated in Jdeveloper 12c.
2.       OSB will support both REST as well as SOAP. REST Adapters has been added for OSB,SOA in Jdeveloper 12c.
3.       Installer  will  contain only one file which will install all the Oracle Fusion Components.
4.       ReSequencer has been added in OSB.
5.       We can test the services from Jdeveloper itself.
6.       Debugging will be easy as Togglepoints are added in Jdeveloper 12c, which was earlier possible  in Eclipse.
7.       Oracle will provide migration scripts which will migrate existing 11g components to 12C. However, migration only possible for 11.1.1.6 or 11.1.1.7 versions of SOA.
8.       Database will also be migrate during migration.
9.   New adapters for Cloud has been added in Jdeveloper 12C . Example:- Salesforce adapter.
10.   New  feature MFT(Managed File Transfer) is added to support fast file transfers. Easy to track file transfers with better error handling mechanisms. There will
be separate console for MFT.


Sunday, 27 April 2014

DEV_MDS.MDS_INTERNAL_SHREDDED error

When we install SOA suite 11g, after server startup, many a times SOA_INFRA remains down. If we check admin server logs, we will find below error message:-

DEV_MDS.MDS_INTERNAL_SHREDDED

Solution:- In order to resolve this error, please follow below steps:-

1.)Open SQLDeveloper and make a connection with DEV_MDS Schema.
2.)Compile below packages
      a.)mds_internal_common
      b.)mds_internal_shredded
      c.)mds_internal_utils


After that restart the server..

Hope this blog will help you guys...

Friday, 25 April 2014

SOA_Server error AGENT_ERROR_TRANSPORT_INIT(197)

When we install soa suite 11g, sometimes while starting soa_server, we face below error:-

FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]

Starting WLS with line:

In Order to resolve this error, follow below steps:-

1.)Go to $MiddlewareHome\user_projects\domains\soa_domain\bin
      2.)  Open setDomainEnv.cmd
      3.)  Change ‘set debugFlag=true’  to ‘rem set debugFlag=true


      After that restart the server. 

     Enjoy......................






Error occurred during initialization of VM

Generally when we install SOA Suite 11g on windows platform, we face below error while starting admin server:-

Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Stopping Derby server...

Derby server stopped.

We can see this on command prompt as below :-

Solution:-
Go to file <domain home>\bin\setSOADomainEnv.cmd/sh (depending on your platform) and modify the line:
set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
to something like:
set DEFAULT_MEM_ARGS=-Xms512m -Xmx768m


After that , just restart the server...

Setting Up Node Manager in SOA 11g

This blog will explain how to set up Node Manager after SOA 11g server installation.
In order to setup node manager, Please follow below step:-

1.)   After server installation and domain configuration, Startup the NodeManager 
  a.)Go to $MiddlewareHome\wlserver_10.3\server\bin
  b.)Double click on StartNodeManager.cmd
  c.)After that go to path $MiddlewareHome\wlserver_10.3\common\nodemanager
  d.)Notice that one file named ‘nodemanager.properties’ will be created when we double clicked StartNodeManager.cmd

  e.)Open nodemanager.properties file and change default value of StartScriptEnabled from 'false’  to true & save it


2.)After that, again start NodeManager by repeating steps 1a & 1b
3.)Start Weblogic server by following below:-
   a.)Go to $MiddlewareHome\user_projects\domains\soa_domain\bin
   b.)Double click ‘startWebLogic.cmd’
    c.)Admin Server will come to running mode


Friday, 21 February 2014

SOA Java Framework

I was trying to implement Java code with 11g SOA. Gone through a number of blogs. I found bit confusing many of them. The main confusion arises, in which directory java jar file to be place. Some blogs saying move it to domain/lib while others saying /oracle.soa.ext_11.1.1. That motivates me to do research on it and found a best way to implement Java Framework with SOA.
If we are working in Locally installed SOA Suite(windows platform), then need to follow below steps:-

Jdev + windows

1.)Create java project in Jdeveloper.
2.)Create Java class
3.)Compile it
4.)Deploy it by right clicking on project and choosing option Deploy. It will create *.jar file in deploy folder of project location.
5.)Then pick this jar file. Place it inside
$FMWHome\user_projects\domains\mds_domain\lib
6.) Restart server

If we are working in Unix installed SOA Suite(Linux platform), then need to follow below steps:-

Server + linux
1.)Create java project in Jdeveloper.
2.)Create Java class
3.)Compile it
4.)Deploy it by right clicking on project and choosing option Deploy. It will create *.jar file in deploy folder of project location.
5.)Then pick this jar file. Place it inside
$FMWHome/soa/modules/oracle.soa.ext_11.1.1
6.)ant on build.xml placed inside /oracle.soa.ext_11.1.1

Ant command is as below:-

ant -logfile build.log -buildfile build.xml create-manifest-jar -Dbasedir=$FMWHome/soa/modules/oracle.soa.ext_11.1.1

Don't forget to set Java_Home,Ant_Home,ClassPath before running ant.

Will Update this blog with more details in few days.