Blogs by

Søren Hansen

All. A long time ago I created this post regarding the same topic: http://scn.sap.com/thread/3678950 Disclaimer: The following is a hack, allowing you to add parameters directly to your local (development) instance of an Agentry application

Intro The new Eclipse based Integrated Test Environment, which takes over the functionalities of the old ATE (Agentry Test Environment), has been awaited for quite some time, and has been released for a while now.

Intro In this document I will show the basics of Agentry Transaction Failure Handling and how to enable it for SAP Work Manager 6.1 on SMP 3.0. The Administration Cockpit on SMP 3.0 has settings

All. I have just build a new version of the Android Agentry Client based on OpenUI in the SMP 3.0 SDK version SP06 PL02. When you import the OpenUI projects into Eclipse you will be

All. One of the things that has troubled me the most regarding Agentry on SMP 3.0 is the way the URL endpoint is constructed. The default URL endpoint is https://<FQDN_SMP>:8081/<AgentryAppName>, where <AgentryAppName> is SAPWM for

All. In our company we are building a custom SAP Work Manager 6.1 solution for our Oil & Gas OffShore technicians, who are to be working in an ATEX Zone 2 environment, where explosion proof

In Agentry 6.x (prior to SMP 3.0) one would add the following line to the [Java-1] section of the Agentry.ini file of the Agentry Server:      nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7090,server=y,suspend=n In this case the debugging port would

I have previously posted questions related to setting up an SMP 3.0 connection for Business Objects Mobile iOS application in this thread http://scn.sap.com/thread/3629468, unfortunately I didn’t get any responses One of my colleagues has been

All. I have done some findings in the area of JVM memory analysis and adjustment that I wanted to share. Background In the Agentry Server prior to SMP one had the option to adjust the

Problem: 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