All SAP Mobility users of Agentry and SMP 3.0,

As a proactive effort to describe the newest features of SMP and Agentry, we would like to discuss or define the new changes made to the platform to support Agentry/SMP clusters.

In SMP 3.0 SP03 there was an SMP architectural change to support clusters. The Agentry configurations (setup in the agentry.ini) are now stored in the SMP data store and available to Agentry cluster nodes (or all server nodes), so the standalone agentry.ini is no longer needed in production. Most of the former agentry.ini settings that are needed to configure the connection are now in the SAP Management Cockpit. There may be some other agentry.ini features not built-in to the cockpit due to the change but it may show up later or removed completely.

Symptoms that you may see:

  • The Agentry.ini disappears whenever you restart the SMP 3.0 server
  • Agentry.ini (SMP 3.0) is not taking your last configuration changes (edits) and is being ignored by the SMP 3.0 platform

What is the definition of an Agentry production or development publish?

Please refer to the following documents:

  1. Publishing to Development.
  2. Publishing to Production. (In particular – “When you are ready to perform final quality assurance testing or need to deploy the application to users, you perform a production publish in the Agentry Editor, which zips the application files in preparation for importing in to SAP Mobile Platform Server – via the SAP Management Cockpit). In Production mode, the agentry.ini by designed is deleted from the deployed folder as it is stored in the SMP product-name data store or share. Also nobody can edit an Agentry.ini (or copy it) and expect it to exist in the production deployment folder to be taken in by SMP 3.0 with this architectural change. This is by design.


Troubleshooting:

  1. Agentry Editor – Publish Server Configuration Error. (SMP 3.0 SP05 SDK).
  2. Agentry Editor – Publish Server Configuration Error. (SMP 3.0 SP04 Server). – Adaptive Server Enterprise database (cluster).

Most of the products designed in Agentry: SAP Work Manager, SAP Inventory Manager, SAP Sales Manager and others can be downloaded from the service market place. All of the zipped files released are production zip files.

Referenced feature number (SAPJira SMPAGENTRY-867 and SMPAGENTRY-952).

Design recommendation: Before using the design in production mode (zip publish), make sure you tested everything in development. Once you do a zip production publish and import this in the Management Cockpit (in production), your Agentry.ini is not used (or cannot be used for updates) in the SMP configuration Agentry deployment folder (ex: \SMP\Server\configuration\com.sap.mobile.platform.server.agentry.application).

Workaround: Sometimes user may need to do some last minute changes in production. In this case, you may follow the Quick Start Guide Work Manager 6.1 technique where you will need to recreate the Agentry node (From the presentation: check the pictures on how the agentry.ini gets removed after you import the Agentry zip file).

As we continue to improve our documentation and release notes, we appreciate your time in reviewing this blog. Please share this with your common designers and users to share the knowledge.

Best Regards,

Mark Pe

SAP Platinum Support Engineer (Mobility)

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. SACHIN R

    HI i trying to install SMP as a development server after install if i want to test application in the Agentry Test environment is  it possible to test it because to test app the without  Agentry.ini is file.

    (0) 
  2. Mark Pe Post author

    Sachin,

    Thank you for reaching out.  Let me try to answer you.

    Let us try to clarify definition of what “Development” means.

    Scenario 1: If you are simply using SMP as a development machine for testing then it is assumed you simply installed SMP during installation stating that it is for development + you are using development database.

    In this case, you are still going to use an application.zip (Agentry export from the editor) that contains all of the needed files to constitute your mobility application. Inside this applicationName.zip will have an application folder with production folder in it.

    After loading in the SMP 3.0 cockpit, normally the agentry.ini gets absorbed to be copied in the SMP 3.0 cockpit.  All the needed changes can be done dynamically in the cockpit settings instead. To get the agentry.ini back out again, you will need to use your SMP 3.0 cockpit to export the application into a zip file.  In this new SMP 3.0 exported zip file you will see the agentry.ini again.

    Scenario 2: In the older Agentry standalone server, there is a concept of publishing as a development version.

    In this scenario, the Agentry designers or developers are geared to constantly tweak and edit the logic in the Agentry Eclipse Editor. This causes them to constantly change and publish their version into what we call a “Development” published.  They would constantly have only one version.  The dev version.  In this version, the concept of production number publish is not followed (ex: AppName-v1-0-0.agpz).  You will only have one version.

    If this is your scenario, then normally the application folder will have something like application/development/ in it.  This type of publishing from the Agentry editor is known also as a development published.

    From your question above, I am leaning that you mean Scenario 1.

    Both cases can use the Agentry Test Environment for testing.  All you need is to provide the Eclipse Editor ATE with the URL of your application.

    Hope this helps.

    Best Regards,

    Mark Pe
    SAP Platinum Support Engineer

     

    (0) 

Leave a Reply