Skip to Content
Author's profile photo Søren Hansen

SMP 3.0: Setup local Agentry development environment with source=INI in JavaBE.ini


You want to setup a local Agentry development environment on your PC to modify an existing Agentry application you have installed in your system landscape. You install an SMP 3.0 and publish an Agentry Application to your SMP (check SMP 3.0: Custom development of SAP Work Manager 6.1 on Agentry Server).

Now you need to setup the mobile application parameters for the interaction between Agentry and your SAP backend. You will want your production instance (central SMP 3.0 server) to use source=SAP, meaning you maintain the parameter values on the backend. However if you want to make changes to the parameters, which only influence your local installation there are 2 ways of doing this:

1. Copy the (productive) mobile application in the Configuration Portal on the Backend, and setup your environment to use this.

2. Use source=INI in your JaveBE.ini file, and maintain all parameters in the JavaBE.ini file.

If you are working in sprints and needs to do this over and over, solution 1 may not be a good solution for you, and you will wish you could just do changes locally on your SMP server.

The problem with solution 2 is that there’s is no standard way of getting the mobile application parameters from the productive mobile application to the JavaBE.ini file.


I have created a small ABAP program (please excuse the state it is in, consider it to be a draft). It is attached to this post and can easily be copy-pasted in your local system.

Run it and it will generate a text file with all the key/value pairs of the parameters for your (production) mobile application.

Then change the value (in your local server) of source to INI (from SAP) in the JavaBE.ini file.

Append the content of the generated text file at the end of the JavaBE.ini file.

If you want to make local modifications do this also in JavaBE.ini.

Publish to SMP.

Restart SMP.

Now you can test you local changes to the parameter value.

When your test is done, you can save the new value in the SAP backend, and afterwards you can easily realign your local environment with your central one.

Hope this may help somebody.

Søren Hansen

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Srikanth Palla
      Srikanth Palla

      Soren / Murali,

      Followed the steps above, but my SMP server was not reading the definitions from JavaBE.ini file.

      Anything I am missing here?

      Author's profile photo Søren Hansen
      Søren Hansen
      Blog Post Author

      I don't know exactly what you may have missed.

      I am regularly using this technique and know it works for parameters referencing Java classes. However I am a little uncertain with parameters regarding Complex Tables, which I have had some trouble with.

      Can you be a little more detailed on how you are using this ?

      Søren Hansen