Hi Govindarajan,Although it's not fixed yet, we're now working with the Java developer and ESRI Support. Once we get a fix, I'll update the forum, would it be relevant for others.Thank you very much for your advise.regards,Chapal
Mr.ChapalFirst i have not done this using JAVA but i did the development using .Net. So i given the standard checklists for .Net based development. Not sure whether it is applicable for Java based app framework.Since you had mentioned that it is working on the dev system, i assume that the coding has been done properly. Also i am assuming that you hae registered the SOE properly.You had mentioned that it is relating to two machine configuration. Note that the MXD path being referred by the mapservice should be stored in a folder location on the individual SOCs and ArcSOC user account be given read-write privilege on this folder. Maintain the same folder structure in both the SOC systems.Also check the logs in the ArcGISServerHome/server/user/log folders. In the constructor event of SOE use try..catch and write a message to the logger. Then start the Mapservice. The SOE gets initialised. This is when the exceptions, if any, would be caught and written to the server logs. Of course set the Server log level to DETAILED INFO . Now stop the service and check the logs. The parameters if any that u are passing to this using ArcCatalog property pages, if any shall be retrieved in the IObjectConstruct construct method. Check whether this one is working using logger. If all of these work well then i feel there shouldny be any problem.Also check whether your app in the prod server is trying to access content behind any firewall.Let me know if you face any problemRegardsGovindarajan
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.