JDev Startup Issue

Many times, we may encounter JDev doesnt startup in our linux environment after installation.
The JDev studio when started may throw the below exception as,


oracle.ide.marshal.xml.Object2DomException: Error parsing XML --
/home/user/.jdeveloper/system11.1.1.7.40.64.11/o.jdeveloper/applications.xml
at
oracle.ide.marshal.xml.Object2Dom.newO2DException(Object2Dom.java:1229)
at
oracle.ide.marshal.xml.Object2Dom.getDocument(Object2Dom.java:1189)
at
oracle.ide.marshal.xml.Object2Dom.getDocument(Object2Dom.java:1134)
at oracle.ide.marshal.xml.Object2Dom.open(Object2Dom.java:544)
at oracle.ide.model.DataContainer.loadImpl(DataContainer.java:552)
at oracle.ide.model.Node.load(Node.java:2220)
at oracle.ide.model.Node.open(Node.java:959)
at oracle.ide.model.Node.open(Node.java:922)
Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element
expected.
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)


Its because of an existence of a system directory inside ' /home/user/.jdeveloper' i.e
' /home/user/.jdeveloper/system11.1.1.7.40.64.11'


Resolution: Remove the system directory in /home/user/.jdeveloper and Start the JDev Studio.


Note: the directory ".jdeveloper"is a hidden directory, do
la -latr /home/user
to view the hidden directory

Krishnam Vande Jagadgurum

Krishna is the Supreme Godhead - He is the cause and effect of all & everything around us



Hare Krishna Hare Krishna
Krishna Krishna Hare Hare
Hare Rama Hare Rama 
Rama Rama Hare Hare

b2b.donot_initialize

Here comes my first post on Middleware.

Many times, it is indeed needed to isolate your problem for SOA-B2B. One way to do this is to isolate b2b from SOA.

If you are using BPM (or SOA) and you are not using any of the B2B functionality, then you might want to consider disabling B2B on your SOA managed servers.  There are a few good reasons for doing this:

    You will save some memory,

    You will reduce your managed server start (and restart) time, and

    You avoid any potential problems that may be introduced by running unnecessary modules – think security.

This can be done by setting the b2b server property in EM for the following parameter as
b2b.donot_initialize=true


Restart the servers and observe that B2B is not loaded at startup of soa_server1.

1) Login to EM
2) Goto soa-infra
3) SOA-Infrastructure -> SOA Administration -> B2B Server properties
4) Click on 'More B2B Configuration Properties'
5) Goto 'Operations' tab
6) Click 'addProperty'
7) In key field , enter 'b2b.donot_initialize'
8) In value field, enter 'true'
9) add comment and click 'Invoke'
10) Restart the managed servers