SMP3 - AppDevelopment (Agentry):

Hi, I have a question on SMP3 and AppDevelopment (Agentry):
In previous projects we have typically run Agentry Server processes on our development machines so that we can unit test the enhancements that we are making prior to publishing to a more public DEV server.
I'm guessing that this is a pretty standard practice.
My question is: Does this model of having Agentry developers run their own Agentry Servers still hold for SMP3.0 now that Agentry has been incorporated into the main SMP server process.
We are on Ramp-Up for SMP 3 and I'm just about to setup our dev environments. Your comments would be appreciated!
Anyone know of any good articles that cover this topic for SMP 3.0?
Regards
Marty

In terms of environments here is what we commonly see and use. This actually applies to any Agentry version but yes also applies to SMP 3.0 as well.
Typically each developer will install an SMP 3.0 server as a developer installation on their development machine for their individual configuration activities. This instance would be setup in Agentry Developer mode (equivalent to ServerDev in previous releases). This instance would be pointing to your developement backend environment and be used for initial unit testing of their changes.
If you have multiple developers the would either checkin code to the Agentry share or go through a merge process to create a master version (Agentry Production Publish) that would then be promoted forward to the next environment.
The next environment is sometimes an integration test instance running in Agentry Production mode (ServerProd) SMP 3.0 (probably still as a developer installation) where the application is deployed for initial testing still against the development backend environment.
If everything looks good on the integration test instance, next would be deploying to your QA/Acceptance instance pointing to your QA/Acceptance backend environment. This should mirror production in terms of load balancing / clustering / data volumes etc. As such for SMP 3.0 it should be configured for a Production installation. Here is where your test team would execute their acceptance test scripts to confirm everything is ready before moving to the final Production environment.
Hope this helps!
--Bill

Similar Messages

SMP3 - AppDevelopment (Agentry):how to use GCM (Google cloud Messaging) for Agentry Application.

Hi, I have a question on SMP3 and AppDevelopment (Agentry): how to use GCM (Google cloud Messaging) for Agentry Application for PUSH notification

Pratik,
Let me walk you through the flow with the assumption that the user is on an Android device and "connected" to the Agentry server.
An emergency workorder is created in SAP and assigned to the technician.
The SAP backend system will notify the Agentry server via an XML message that there is a workorder to send.
Agentry will get the details and if the user is connected attempt to send the workorder to the device via the Push mechanism
If the push fails to reach the Agentry client, the Agentry server will send a GCM message to the user
When the user returns to the Agentry client, the normal push processing / fetch will occur to receive the workorder from the server assuming the push retrys are in effect.
So, essentially you should not have to do anything to get the GCM to work as a secondary notification mechanism.
If you are looking to do something else with GCM that would be outside of Agentry.
--Bill

SMP3 - AppDevelopment (native):

Hi, I have a question on SMP3 and AppDevelopment (native):
I want to create an Agentry App on SMP3.0 for iOS platform. The connectivity to the backend would be with a MS SQL Server. I would be loading the data from SQL to Agentry Complex tables. I would like to know how these Agentry Complex tables can be read from the OpenUI framework provided in SMP 3.0. ie, read data from a specific complex table based on a search criteria and the values updated back to Complex table, and the transaction updated the SQL DB.
Let us know if we are in the right approach.
Reagrds,
Ashwin
Tags edited by: Michael Appleby

Thanks Bill for reply. Adding on to your above query.
Our Objective is to build forms dynamically and our understanding is we will send the forms and its fields and its properties queried from SQL DB to the form engine what we are want to build using OpenUI. The data queried will be stored in Collection accessed by OpenUI to build the form.
The Agentry application has two system connections one with SAP Backened using JCo (for Workorder information) and SQL Connection (for Forms,fields and its attributes) queried to build a form in Agentry. My understanding was to store the data related to Form and its fields in collection property({Form1,Field1,Field2,Field3...FieldN},{Form2,Field1A,Field2A,Field3A...FieldNA}) for N Forms.
In OpenUI I need to read this collection property(using SMPCollectionDisplay model) and build a Form for Agentry iOS Platform.
Are we following the right approach or is there any gap in our understanding to achieve our goal.

SMP3 - AppDevelopment (Mobiliser): Different Machine Between SMP3 and Mobiliser

Hi, Expert I have a question on SMP3 and AppDevelopment (Mobiliser):
Let me explanation an issue,
I Have a mobiliser 5.1 banking system and it running normally on server, and a few month later i want to use mobile application with (SMP3, Cordova with Kapsel and SAPGUI) for use my existing mobiliser system, heBut i find difficult when they want to access te services (SOAP) provided by the mobiliser system.
for information, which i have done for that:
install smp3.0 sp01
configure Eclipse IDE with SAPGUI plugin and integration gateway plugin
create odata service from jdbc -> successfully to access odata service provided from mobile application
create odata service from SOAP -> successfully to access odata service provided from mobile applicationn
But when i tried create Odata from mobiliser service, it failed with message " Could not send Message", i think this happens because the mobiliser service requires authentication. the following my question:
how to create Odata Service from SOAP service with authentication
if point 1 not possible, anyone have another solution for integrate service between SMP3 and Mobiliser (running on difference machine)
difference function the SAP mobile solution (Agentry, Integration gateway(SMP3), Appbuilder, Kapsel, SAPGUI, Afaria, Fiori)
Many thanks for explanation, and if possible can guide me with some example.
Basuki

The Mobiliser server components have been integrated into SMP3.0 and are actually the same components that are used for the standalone Mobiliser 5.1 SP03 release (also referred to as 5.1.3). The difference is in the packaging.
Documentation for the Mobiliser 5.1.3 can be found here : http://sybooks.sybase.com/sybooks/sybooks.xhtml?id=100066&c=firsttab&a=0&p=categories
Now for the less obvious part …
The Mobiliser sample/reference mobile apps (aka Smartphone Mobiliser) and the build scripts required to build for iOS, Android, Blackberry and Mobile Web are part of the Mobiliser 5.1 SP03 release only. The apps didn't make it into the mobile platform, except for the build output of Mobile Web. With the build scripts mentioned, we did create a Mobile Web version that is included in the SMP3.0 server. This is a separate bundle that needs to be activated via the admin cockpit.
If you want to leverage the Smartphone Mobiliser product, you will have to use Mobiliser 5.1.3. Not sure how this works out from a sales/customer point of view. Let me know if you have issues with this.
Technically, the web services used by Smartphone Mobiliser to interface with the server are identical for SMP3.0 and Mobiliser 5.1.3. So Smartphone Mobiliser apps can work with both SMP3.0 and Mobiliser standalone. Mobiliser apps will directly interface with the smartphone web services.
Hope this helps.
Regards,
Ludo Noens

SMP3 - AppDevelopment:

Hi, I have a question on SMP3 and AppDevelopment:
I have SMP3 SP03 (3.0.3) installed and running. I have an application installed/published with app specific configurations displaying in the SAP Administration center. I am receiving the "I am here" via the http request. When connecting using the TestEnvironment, I am receiving the "A certificate needed to verify the certificate received cannot be found" error. I have followed the Sybase documentation (all three Authentication Certificates) to create/install the certificate, albeit some of the documentation doesn't align with SMP3 when updating via the "console", but I am still unable to resolve the certificate error. Are there any tricks or other documents I should consider?

I have installed the Agentry Client (win32) and am receiving the same error as the ATE.
I have installed the ATE on a different machine, and prior to installing the "smp_crt.cer", I received this error:
“Certificate received is not found in the trusted list, nor
can it be traced to a trusted root.”
I then installed the "smp_crt.cer" as instructed and the original error has returned. From the ATE events.log, I have the following:
09/16/2014 10:41:18, 1,        22,2148074248, Thr      21108, Error #2148074248(0x80090308): The token supplied to the function is invalid
, ..\..\..\..\Socket\win32\schannelSSLsockets.cpp#615:SchannelSSLstreamSocket::handshake
09/16/2014 10:41:22, 1,        25,         0, Thr      21108, Certificate received is not found in the trusted list, nor can it be traced to a trusted root., ..\..\..\..\Socket\win32\schannelSSLsockets.cpp#786:SchannelSSLstreamSocket::validateContextCertificates
09/16/2014 10:43:53, 1,        22,2148074279, Thr      21108, Error #2148074279(0x80090327): An unknown error occurred while processing the certificate.
, ..\..\..\..\Socket\win32\schannelSSLsockets.cpp#615:SchannelSSLstreamSocket::handshake
Subsequent attempts have only repeated the SchannelSSLstreamSocket::handshake error.
I have also disabled all firewall protection...

SMP3 - AppDevelopment (Mobiliser):

Hi, I have a question on SMP3 and AppDevelopment (Mobiliser):
Which is the most stable version of mobiliser - Mobiliser 5.X standalone or SMP 3.0 AppServices
Which do you recommend for a development team just starting out on mBanking/mCommerce application development?

Both the Mobiliser and SMP are based on OSGI java platform. All the current and future development of Mobiliser features will be tightly integrated into the SMP platform architecture. For example, SMP 3.X provides NFC APIs, web portals, security instruments, etc. for development enablement mainly focus on finance and retails domains. But if you consider customizing existing standard mobile apps based on Mobiliser such as Shopper Experience, mUtility, mLoyalty, etc., then make sure the apps and their features are certified by the SMP Platform.

SMP3 - AppDevelopment (Mobiliser): Deploy the new development

Hi, I have a question on SMP3 and AppDevelopment (Mobiliser):
Is there any documentation available to explain the process involved in developing one sample mobiliser App, and deploying it in the mobiliser.
Including dbmaintain changes.(like adding a table or adding entry to a table).
If it is available please share the link
Thanks.

The Mobiliser server components have been integrated into SMP3.0 and are actually the same components that are used for the standalone Mobiliser 5.1 SP03 release (also referred to as 5.1.3). The difference is in the packaging.
Documentation for the Mobiliser 5.1.3 can be found here : http://sybooks.sybase.com/sybooks/sybooks.xhtml?id=100066&c=firsttab&a=0&p=categories
Now for the less obvious part …
The Mobiliser sample/reference mobile apps (aka Smartphone Mobiliser) and the build scripts required to build for iOS, Android, Blackberry and Mobile Web are part of the Mobiliser 5.1 SP03 release only. The apps didn't make it into the mobile platform, except for the build output of Mobile Web. With the build scripts mentioned, we did create a Mobile Web version that is included in the SMP3.0 server. This is a separate bundle that needs to be activated via the admin cockpit.
If you want to leverage the Smartphone Mobiliser product, you will have to use Mobiliser 5.1.3. Not sure how this works out from a sales/customer point of view. Let me know if you have issues with this.
Technically, the web services used by Smartphone Mobiliser to interface with the server are identical for SMP3.0 and Mobiliser 5.1.3. So Smartphone Mobiliser apps can work with both SMP3.0 and Mobiliser standalone. Mobiliser apps will directly interface with the smartphone web services.
Hope this helps.
Regards,
Ludo Noens

SMP3 - AppDevelopment (native iOS Offline):

Hi, I have a question on SMP3 and AppDevelopment (native iOS Offline):
     when i am online the posting of data to backend is working fine, when i go offline and add an entry the log shows the message as follows
now i came to online , the automatic calling of offline requests are not invoking.
As for postbody i am using a Json format
{"Street":"","CityX":"","BankCountry":"IN","BankName":"Off-Test","City":"","Region":"","BankKey":"32106","__metadata":{"uri":"http://xxxxxxxxx:8080/com.chandu.bankdelta/BankSet(BankCountry='IN',BankKey='32106')"},"BankNameX":""}
help me where i go wrong.
Regards
Siva Chandu

Hi Midhun,
     i have add these libraries
    this is the code i am using for post.
    ODataEntry *newBank = [[ODataEntry alloc] initWithEntitySchema:[self.smpCont.serviceDocument.schema getCollectionByName:@"BankSet"].entitySchema];
    ODataPropertyValueObject* filterValue = [newBank getPropertyValueByPath:@"BankCountry"];
    [filterValue setValue:@"IN"];
    ODataPropertyValueObject* filterValue1 = [newBank getPropertyValueByPath:@"BankKey"];
    [filterValue1 setValue:self.idTF.text];
    ODataPropertyValueObject* filterValue2 = [newBank getPropertyValueByPath:@"BankName"];
    [filterValue2 setValue: @"Off-Test"];
    ODataPropertyValueObject* filterValue3 = [newBank getPropertyValueByPath:@"Street"];
    [filterValue3 setValue: @""];
    ODataPropertyValueObject* filterValue4 = [newBank getPropertyValueByPath:@"CityX"];
    [filterValue4 setValue: @""];
    ODataPropertyValueObject* filterValue5 = [newBank getPropertyValueByPath:@"Region"];
    [filterValue5 setValue: @""];
    ODataPropertyValueObject* filterValue6 = [newBank getPropertyValueByPath:@"BankNameX"];
    [filterValue6 setValue: @""];
    ODataPropertyValueObject* filterValue7 = [newBank getPropertyValueByPath:@"City"];
    [filterValue7 setValue: @""];
    ODataEntryBody *entryBody1 = buildODataEntryRequestBody(newBank, ENTRY_OPERATION_CREATE, self.smpCont.serviceDocument, NO, BUILD_STYLE_JSON);
[RequestBuilder setRequestType:HTTPRequestType];
    [RequestBuilder enableXCSRF:YES];
    NSString *url = [NSString stringWithFormat:@"%@%@",self.appEndPointURL,urlString];
    url = [url stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding];
    id<Requesting> request = [RequestBuilder requestWithURL:[[NSURL alloc] initWithString:url]];
    [request setRequestMethod:@"POST"];
    [request setUsername:self.username];
    [request setPassword:self.password];
    [request addRequestHeader:@"X-SUP-APPCID" value:self.appConnectionID];
    [request addRequestHeader:@"Content-Type" value:@"application/json; charset=UTF-8"];
NSString *postBody = [entryBody1 body];
NSMutableData *data = [NSMutableData dataWithData:[postBody dataUsingEncoding:NSUTF8StringEncoding]];
    [request setPostBody:data];
if([[Reachability reachabilityForInternetConnection] currentReachabilityStatus] != NotReachable)
        [request setDelegate:sender];
        [request setDidFinishSelector:finishSelector];
        [request setDidFailSelector:failSelector];
        NSLog(@"Starting initial asynchronous POST request for Travel Agency Create");
        [request startAsynchronous];
        return;
    else{
        [RequestBuilder setDelegate:self];
        [RequestBuilder setDidFinishSelector:@selector(OfflineRequestSuccesSelector:)];
        [RequestBuilder setDidFailSelector:@selector(offlineRequestFailedSelector:)];
        [request setCacheUrlKey:url];
        NSLog(@"Starting initial synchronous POST request for Travel Agency Create");
        [request startAsynchronous];
        return;
note : I am using Mac OS 10.7.5
ref : 1933862 - SAP Mobile SDK 3rd Party Installation Version Requirements
Regards
Siva Chandu.

SMP3 Agentry Server SQLBEException - SAInvalidLogin

Hello Experts,
I am creating from scratch Agentry app.
Our Department have on-Premise SMP3 SP3 PL1 Server with running Agentry Server.
Steps done:
On the Server installed MS SQL 2012 Expressactivated "sa" user with default password
On the Server configured ODBC Connection via "Set up data sources (ODBC)"
used driver is "SQL Server Native Client 11.0"
name of the connection is "smp3sqlserver"
server is "(local)\sqlexpress"
verification is done by login ID and password. "sa" user is used.
the ODBC Data Source Connection is working and verified
using the SMP3 cockpit Agentry app was created
the App was named "com.sap.agentry.swatapp"
Security profile contain "No Authentication Challenge"
On the Server within SMP folders, the agenry application folder with the agentry.ini" file was created.
Network drive mapped - on server folder "..\Server\configuration\com.sap.mobile.platform.server.agenry.application"
on my machine the Agentry app was created using Eclipse
application is called: "com.sap.agentry.swatapp
System Connection - "smp3sqlserver" SQL System Connection
app compiles without errors.
deployed app via Eclipse to the mapped network drive
"https://<server>:8082/comsapagentryswatapp" gives "I am here!" message
The problem I am having is logged inside the Server startup.log
<---------------------------------------------------------------------------- startup.log ---------------------------------------------------------------->
12:50:19 06/19/2014: Starting Agentry (64-bit Windows)
12:50:19 06/19/2014: Reading system ini file.
12:50:19 06/19/2014: Starting log file.
12:50:19 06/19/2014: Loading message groups.
12:50:19 06/19/2014: Starting threads.
12:50:19 06/19/2014: 1 initial threads. Threads will auto-scale.
12:50:19 06/19/2014: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
12:50:19 06/19/2014: Event: 0, 2, Key pair loaded successfully.
12:50:19 06/19/2014: Starting Agentry: Agentry Server Agent v7.0.3.205
12:50:19 06/19/2014: Event: 0, 2, Agentry Startup
12:50:19 06/19/2014: Loading 0 front ends
12:50:19 06/19/2014: Loading front end from angelvine
12:50:19 06/19/2014: WebSockets Front End: loading configuration
12:50:19 06/19/2014: Event: 17, 14, WebSockets Front End v7.0.3.205
12:50:19 06/19/2014: Starting Agentry Server Agent
12:50:19 06/19/2014: Agentry Server Agent: Starting threads.
12:50:19 06/19/2014: 1 initial threads. Threads will auto-scale.
12:50:19 06/19/2014: Agentry Server Agent: Adding messages.
12:50:19 06/19/2014: Event: 1, 4, Agentry Server Agent v7.0.3.205
12:50:19 06/19/2014: Loading agent from ag3.dll
12:50:19 06/19/2014: Starting Server
12:50:19 06/19/2014: Server: reading config file
12:50:20 06/19/2014: Event: 20, 150, Loading Production application definitions using file "comsapagentryswatapp-v1-0-0-app"
12:50:20 06/19/2014: Event: 20, 152, Loading Production application definitions for default localization
12:50:20 06/19/2014: Initializing SQL-smp3sqlserver from ag3sqlbe.dll
12:50:20 06/19/2014: smp3sqlserver Back End: reading config information.
12:50:20 06/19/2014: smp3sqlserver: name set to 'SQL-smp3sqlserver'.
12:50:20 06/19/2014: SQL-smp3sqlserver Back End: reading query config information.
12:50:20 06/19/2014: SQL-smp3sqlserver Back End: initialized
12:50:20 06/19/2014: Event: 21, 4, Loaded SQL-smp3sqlserver (SQL v7.0.3.205) from ag3sqlbe.dll
12:50:20 06/19/2014: SQL-smp3sqlserver Back End: connecting 'sa' to database 'smp3sqlserver'
12:50:21 06/19/2014: Exception: 12:50:21 06/19/2014 : 16 (SQLBEException), SAInvalidLogin (3: SA_DBMS_API_Error, DB Code: 0, DB Text:IM002 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, ), sqlBE.cpp#1353:DbConnectionPoolMgr::create
12:50:21 06/19/2014: SQL-smp3sqlserver Back End: started
12:50:21 06/19/2014: Event: 20, 153, Finished loading Production application definitions for default localization
12:50:21 06/19/2014: Event: 20, 151, Finished loading Production application definitions using file "comsapagentryswatapp-v1-0-0-app"
12:50:21 06/19/2014: Server: Starting threads.
12:50:21 06/19/2014: 1 initial threads. Threads will auto-scale.
12:50:21 06/19/2014: Event: 20, 4, Server v7.0.3.205
12:50:21 06/19/2014: Starting front ends
12:50:21 06/19/2014: WebSockets Front End: Opening WebSockets servlet for sub-URL /comsapagentryswatapp
12:50:21 06/19/2014: Event: 17, 10, WebSockets Front End v7.0.3.205
12:50:21 06/19/2014: Event: 0, 0, Old log files moved into D:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-06-19-125019
12:50:21 06/19/2014: Event: 0, 23, Agentry startup is complete.
<---------------------------------------------------------------------------- startup.log ---------------------------------------------------------------->
Thanks & Regards
Peter Vargovcik
MIC Dublin Intern

Hi Jason, here is the screenshot:
The ODBC connection definition is made via 64bit ODBC Data Source Administrator
Thanks.
Peter

SMP3.0 Sizing Guide for Agentry Apps

Hi All,
I'm looking for a sizing guide for Agentry Apps (Work Manager in particular) on SMP3.0. I only found the SMP2.3 sizing guide and the quicksizer has a SMP3.0 entry but only seems to refer to Mobilizer and Odata.
Has anyone SMP3.0 Agentry sizing information to share?
Thanks,
Christian
Tags edited by: Michael Appleby

Hi,
The sizing guide to SAP Work Manager 6.0 is avaliable in SAP Service Marketplace.
Go to http://service.sap.com/instguides > Installation & Upgrade Guides > SAP Components > SAP Work Manager 6.1 or SAP Work Manager 6.0
Is there a specific Agentry CoTS application whose sizing guide you were looking for ?
Have a nice day
Amardeep Verma

SMP3 - Agentry - User Authentication

Hi all,
I created an Agentry Application using SMP 3.0 and Agentry 7.
SMP 3.0 is installed locally on my machine. The Agentry Application is connected to a local SQLServer that contain Northwind database.
For the test phase, I create a security profile for the application using an online LDAP Server (Online LDAP Test Server | Forum Systems)
The application is correctly deployed on the SMP 3.0 and now I'm trying to test it using ATE (Agentry Test Environment).
The application can download the certificate and it can connect to the SMP. Now I got a problem in the authentication phase.
I insert the correct username/password (tesla/password) as described in the online LDAP guide (I also tested it using an LDAP Client).
Attached you can see the LDAP security profile configuration.
In event.log I got this entries
05/23/2014 17:48:57, 0, 0, 12, Thr 11912, AG-3ea-3A424B5A-3C65-47F6-B1F2-174EDAABA049
05/23/2014 17:48:57, 0, 0, 6, Thr 11912, tesla: Invalid Password
In XXX-smp-server.log this one:
2014 05 23 17:48:57#+0200#WARN#com.sybase.security.core.CertificateValidationLoginModule##anonymous#http-bio-8081-exec-2###The certificate (chain) is not valid. |
I restarted the server after the configuration change.
Any ideas? How do I configure the application for the authentication?
Up to now I just need to test the application, so the configuration is a "nice to have" now.
I also tried with "No authentication Challange" configuration, but with no results.
Thanks
-- Marco

Marco,
In SMP3.0 Agentry is not yet fully tied into the SMP server for authentication and will handle the authentication itself. As such when you define your Agentry application you should select No Authentication Challenge in the Security profile.
For you application, you will then need to configure at least one Agentry backend connection to handle the authentication. Since you are using SQL as the backend, the default sql user check authentication accepts any user / pwd combination.
Depending on how you are intending to authenticate your users you can either modify the query to check against a table in the database or add an additional backend to handle the authentication using some other source.
For example you could setup a File backend and then use that to authenticate users against Active Directory or add a Java backend and write custom authentication code to validate against a generic LDAP source or some other mechanism.
--Bill

Is there any way to restart Agentry Server without restarting SMP3.0 server?

Hello Experts,
Is there anyway to restart Agentry server, without restarting SMP server? I want to modify the setting of Agentry app and restart the Agentry to make change effective. Each time I restart Agentry, I have to restart the SMP3.0. It is very inconvenient.
Please assist me on this issue. Thank you very much.

That is something I believe they are working on for the next SP release (along with multiple Agentry apps on the same SMP 3 server). I don't know if there is an offical way to do this but will see if I can get any answer.
--Bill

Remove Imported Agentry Application in SMP3

I have published a Production Agentry application (version 1-0-1). This created the appropriate "app.zip" file. I then went into the Management Cockpit and imported this new version. So now my SMP/Agentry has two applications under the "Application/Production" folder -- version 1-0-0 and version 1-0-1 that I just imported.
I made another application change and published out a new application version 1-0-2, and similarly imported it via the Management Cockpit. At this point I now have 3 applications in the "Application/Production" folder -- 1-0-0, 1-0-1, and 1-0-2.
I am 100% certain that all devices have connected and now have the latest 1-0-2 version downloaded to them.
What I want do is is remove the first two versions of the application so they don't get loaded by the SMP server (don't need to waste the memory for versions that will never be executed again). I've tried deleting the "1-0-0" and "1-0-1" files from under the "Application/Production" folder, then stopping/starting the SMP server. When I do this, the "1-0-0" and "1-0-1" versions re-appear.
I've tried delete the application versions (as described above) and deleting the "app-1-0-0.zip" and "app-1-0-1.zip" files, stopping/starting the SMP server. Same results -- all 3 version re-appear and get loaded into SMP.
I don't see anything in the Management cockpit to remove these "old" application.
How do I go about removing these so they do not get loaded up into the SMP server because I do not want that memory to be taken up for applications that will never again be distributed to a device?
Thanks,
Ed

Stephen,
This did not work. I exported the application. I deleted the application from the Cockpit. I modified the exported application ".zip" file to remove the older versions. I then tried to import it back into the Cockpit and it gives me an error saying "Import of application failed! Content of the file is not in expected format".
All I did was to remove the applications from the embedded "Application/Production" folder.
Fortunately I made a backup copy of the original export and tried to import that. It partially imported. The application name imported, but nothing for the "agentry.application" got imported. I had to stop the SMP service, delete the "agentry.application" folder (which didn't get deleted when I deleted the application from the Cockpit), then I could import the original one.
Is there something specific about how the exported application ".zip" file needs to be modified?
Ed

SMP3 - Agentry - No Backend tab available

Hi,
I installed the new 3.0 SP03 PL01 (EBF 22961) as fresh installation. I tried to create a new Agentry application in the Management Cockpit, but the "Backend" tab is empty. See attached picture.
Any suggestion?

Have you published your agentry app? then only you can define back-end connections for a particular agentry based app.
I suggest you to check Defining Back-end Connections for Agentry
Rgrds,
JK

SAP Moble Platform 3.0 with Agentry 7.0 application configuration

Hi,
we try to migrate from SMP 2.3 to SMP 3.0.
We installed the MobilePlatform3 as development server and the SDK 3.0 SP04 PL01.
After that we import the 2.3 project in the new eclips with the agentry editor plugin for 7.0.3. We checked if all transmit configurations are set to WebSockets over HTTPS as connect type.
After that we create a application for Agnetry Apps in the management cockpit and found the agentry.ini in this directory: "SMPHome Directory/\Server\configuration\com.sap.mobile.platform.server.agentry.application. We publish the agentry app to this agentry.ini and see the BACK END configuration in the management cockpit. As authentication we use "no authentication challenge".
Afte restart the SMP server we see in the logs no errors. In the agentry server log we see that the application was loaded. We test the agentry server in the browser with this adress https://{servername}:8081/{sub-url} prüfen and get the "I am here!" message
Now we try to connect from the ATE (version 7.0.3.605)(installed on the same server like the smp) to the agentry server with this adress:"{servername}:8081" and get this error:
Unexpected disconnection from server (11)
Connection failed
Ending transmission
if we try only the server without the port we get this message:
Requesting Public Key from Server
The printer queue is full.
Communications error (14)
Connection failed
Ending transmission
We check the smp3 server logs and the agentyr logs but nothing is in. We set the log level to debug but nothing.
We dont know where we could search for the error. What can we do or where is the error in our configuration.
Thanks,
André
Message was edited by: Michael Appleby

Hi Stephen i do not know how to upload a file to the forum so here is the the startup.log file:
17:55:56 09/03/2014: Starting Agentry (64-bit Windows)
17:55:57 09/03/2014: Reading system ini file.
17:55:57 09/03/2014: Starting log file.
17:55:57 09/03/2014: Loading message groups.
17:55:57 09/03/2014: Starting threads.
17:55:57 09/03/2014:    1 initial threads. Threads will auto-scale.
17:55:57 09/03/2014: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
17:55:57 09/03/2014: Event: 0, 2, Key pair loaded successfully.
17:55:57 09/03/2014: Starting Agentry: Agentry Server Agent v7.0.3.159
17:55:57 09/03/2014: Event: 0, 2, Agentry Startup
17:55:57 09/03/2014: Loading 0 front ends
17:55:57 09/03/2014: Loading front end from angelvine
17:55:57 09/03/2014: WebSockets Front End: loading configuration
17:55:57 09/03/2014: Event: 17, 14, WebSockets Front End v7.0.3.159
17:55:57 09/03/2014: Starting Agentry Server Agent
17:55:57 09/03/2014: Agentry Server Agent: Starting threads.
17:55:57 09/03/2014:    1 initial threads. Threads will auto-scale.
17:55:57 09/03/2014: Agentry Server Agent: Adding messages.
17:55:57 09/03/2014: Event: 1, 4, Agentry Server Agent v7.0.3.159
17:55:57 09/03/2014: Loading agent from ag3.dll
17:55:57 09/03/2014: Starting Server
17:55:57 09/03/2014: Server: reading config file
17:55:58 09/03/2014: Event: 20, 150, Loading Development application definitions
17:56:01 09/03/2014: Initializing SQL-MietraSQLConnection from ag3sqlbe.dll
17:56:01 09/03/2014: MietraSQLConnection Back End: reading config information.
17:56:01 09/03/2014: MietraSQLConnection: name set to 'SQL-MietraSQLConnection'.
17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: reading query config information.
17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: initialized
17:56:01 09/03/2014: Event: 21, 4, Loaded SQL-MietraSQLConnection (SQL v7.0.3.159) from ag3sqlbe.dll
17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: connecting 'dba' to database 'CDB_SDRSUP2'
17:56:01 09/03/2014: Event: 21, 101, dB Connect
17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: started
17:56:01 09/03/2014: Event: 20, 152, Loading Development application definitions for default localization
17:56:01 09/03/2014: Event: 20, 153, Finished loading Development application definitions for default localization
17:56:01 09/03/2014: Event: 20, 151, Finished loading Development application definitions
17:56:01 09/03/2014: Server: Starting threads.
17:56:01 09/03/2014:    1 initial threads. Threads will auto-scale.
17:56:01 09/03/2014: Event: 20, 4, Server v7.0.3.159
17:56:01 09/03/2014: Starting front ends
17:56:01 09/03/2014: WebSockets Front End: Opening WebSockets servlet for sub-URL /Mietra
17:56:01 09/03/2014: Event: 17, 10, WebSockets Front End v7.0.3.159
17:56:01 09/03/2014: Event: 0, 0, Old log files moved into C:\SMP\MobilePlatform3\Server\log\agentry\rolled\2014-09-03-175556
17:56:01 09/03/2014: Event: 0, 23, Agentry startup is complete.

SMP3 - AppDevelopment (Agentry):

Similar Messages

Maybe you are looking for