Quest Midwest on August 17-18 in Chicago

[DMiller]

Do you have a unique story to tell as to how you are utilizing the software? Have you gone through an upgrade or applied a tool release and have lessons learned that others can benefit from? Have you been waiting for the chance to showcase your success? Would you like a complimentary registration to Quest Midwest (if your presentation is selected)?

If so... submit your abstract TODAY or before the call closes on May 27th! We are really looking for JDEdwards customer driven presentations, success stories, tips and techniques, etc.

Go to the Quest Midwest page at: http://www.questdirect.org/QuestDirect/Events/Quest+Midwest/default.htm for more information.

Thanks!!

 

[LongsPeak]

The Enterprise Server that will be used by the BSSV Server i.e. by the BSFN's called from a BSSV running on a BSSV Server will be determined by the settings done in jdeinterop.ini file for the BSSV Server.

If in the jdeinterop.ini file of the BSSV Server - in the OCM section - if the OCMEnabled setting is set to False then the Enterprise Server to be used (for executing the BSFN's) will be picked up from the enterpriseServer setting in the INTEROP section of jdeinterop.ini file .

[OCM]
OCMEnabled=true/false
[INTEROP]
enterpriseServer=XXX

If in the jdeinterop.ini file of the BSSV Server - in the OCM section - if the OCMEnabled setting is set to True - then the BSSV Server should honour the OCM configuration when deciding which Enterprise Server to execute the BSFN's on.



It seems that in your case if you have the OCMEnabled setting set to True then BSFN's called from BSSV should execute on the ES configured in the OCM
If thats the case then make sure that your users who are not getting routed to the expected Enterprise Server could have multiple roles and the role heirarchy is causing OCM to route the BSFN to an unexpected ES