SMP 3.0: Agentry - Using source=INI in JavaBE.ini
I have previously posted a question and a document regarding this issue:
Previously I have only used this technique in development Agentry instances, but now I am trying to extend the use to production Agentry instances.
And this is where all the troubles start.
If I change JavaBE.ini to use source=INI in a production Agentry instance, then after I restart the instance it will be erroneous.
The Back End configuration of the Agentry Application will be gone, and I get runtime errors when I try to perform a transmit from the client.
Error will be something like: No Backends loaded.
Does anybody know if source=INI is (still) offically supported ?
And if Yes, is it only supported for development instances of Agentry ?
Mark Pe replied
We do not support javaBE.ini on mobile parameters on some setup. Everything is in configPanel as this is what is required to be used. (Verified statement today from our product team). In short, move away from the ini and use the configpanel. Similar to my description above about consolidating all the changes in the ECC/CRM area (for simplicity).
Hope this answers your question.
SAP Senior Support Engineer