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
Subscribe to:
Post Comments (Atom)
Linux : Create a new user for the machine
Creating a new user in linux is sometimes needed, when you want to share the user access with anyone. SSH to the machine over the newly cre...
-
In some of the corporate networks, you will need to set the proxy settings for Docker to be able to communicate with external world. Usuall...
-
If your machine has Python 3 installed (or upgraded to Python3), then running yum will fail with below error [sbetha@host:pwd]$ yum ...
-
Krishna is the Supreme Godhead - He is the cause and effect of all & everything around us Hare Krishna Hare Krishna Krishna Krishna...
No comments:
Post a Comment