Sap Sales Manager 2.5.4 & SMP 2.3 (SP4)

[Former Member]

Hello

Thank you for your helpful response and taking your time for reading this.

My Team are having some issues when installing sales manager 2.5.1 with S.M.P 2.3 SP 04.

After migrating the application (Sales Manager 2.5.1) with SMP SDK 2.3 Eclipse 3.7.2.

These are the steps for migrate the app (Sales manager 2.5.1 with Agentry 6.0.38.1.) to SMP 2.3 SP04 Sales manager 2.5.1 with Agentry 6.1.4.179.

1. Install the Agentry Server 6.1.4, the same verion included with SDK 2.3 SP 04.
2. Importing Sales manager 2.5.1 app inside the Eclipse v3.7.2 (Agentry Pluging 6.1.4.x).
3. After the application has been imported succefully to Eclipse v.3.7.2 (with Agentry Pluging 6.1.4.x), then i export the app to the Agentry Server (installed on step 1), for upgrade.
   
4. Finally i got these files on the Agentry Server 6.1.4 with the Sales Manager Application, now what i need is to create the .ZIP files witch is needed to import to SMP 2.3 SP 04 Sap Control Center.
   
       In this image you can see the Agentry Server (6.1.4) with the application Sales Manager 2.5.1.
5. The infocenter Guide said that i Manager.jar wich is needed to connect within the JavaBe.ini... (this files is not here too).
      In this image after export the application sales manager to 2.3 Agentry Server (inclueded into the SDK folder), there not JavaBe.ini or SAP-SALES 2.5.4.jar.

               What is wrong?, Wich files should i include into the Zip File for importing to SMP 2.3?

Let me explain you what i did.

After i exported the project into the Agentry Server Folder,
I copied all these files in this folder :

"JavaBe.ini"

"ini4j.jar"

"librfc32.jar"

"sapjco.jar"

"sapjcorfc.dll" all this files into into the < root > folder

(please check this out this picture, where i explain in detail ).

finally i copie the Sales Manager Applicacion Jar file.

"SAP-SALES-2.5.4.0.jar" into the folder < \Java >

After all these steps, i tried to run the AgentryServer.exe, however the application getting those errores from the log file.

[Former Member · Accepted solution]

I don't see any files attached for the log files, can you please attached?

Stephen

[Former Member · Accepted solution]

Steve, I just imported the application to SMP enviroment successful,

The error was the agentry server version, i was exporting the application to Agentry Server 6.1.4 and
my Smp's Agentry version was 6.1.3..

but when i try to connect the application Sales Manager 2.5.4 it shows this error :

  Im sure the password is ok.

The Log files Startup.log

10:01:48 04/11/2014: Starting server (64-bit Windows)
10:01:48 04/11/2014: Administration client command port is 52111, status port is 52112
10:01:48 04/11/2014: Looking for initial status connection...
10:01:55 04/11/2014: Event: 0, 30, Admin client 172.25.131.25:52394 authenticated successfully.
10:01:55 04/11/2014: Event: 0, 27, Admin client 172.25.131.25:52394 has connected
10:01:55 04/11/2014: Reading system ini file.
10:01:55 04/11/2014: ID: SAP Sales Manager Server v2.5.4.0, Name: ???, Location: ???
10:01:55 04/11/2014: Starting log file.
10:01:55 04/11/2014: Loading message groups.
10:01:55 04/11/2014: Starting threads.
10:01:55 04/11/2014:    1 initial threads.  Threads will auto-scale.
10:01:55 04/11/2014: Starting Server: Agentry v6.1.3.10212
10:01:55 04/11/2014: Event: 0, 2, System Startup
10:01:55 04/11/2014: Loading 1 front ends
10:01:55 04/11/2014: Loading front end from angelvine.dll
10:01:55 04/11/2014: ANGEL Front End: reading init files.
10:01:55 04/11/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
10:01:55 04/11/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
10:01:55 04/11/2014: Event: 0, 2, Key pair loaded successfully.
10:01:55 04/11/2014: Starting Server Agent.
10:01:55 04/11/2014: Agentry: Starting threads.
10:01:55 04/11/2014:    1 initial threads.  Threads will auto-scale.
10:01:55 04/11/2014: Agentry: Adding messages.
10:01:55 04/11/2014: Event: 1, 4, Agentry v6.1.3.10212
10:01:55 04/11/2014: Loading 1 agents
10:01:55 04/11/2014: Loading agent from ag3.dll
10:01:55 04/11/2014: Starting Server
10:01:55 04/11/2014: Server: reading ini file
10:01:56 04/11/2014: Initializing 1-Java from ag3javabe.dll
10:01:56 04/11/2014: SystemConnection-1: Reading configuration information.
10:01:56 04/11/2014: SystemConnection-1: Setting name to 'Java Back End'.
10:01:56 04/11/2014: Java Back End: Initialized.
10:01:56 04/11/2014: Java Back End: Java Virtual Machine loaded.
10:01:56 04/11/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10212
10:01:56 04/11/2014: Java Back End: Initialized.
10:01:56 04/11/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.7.0_51, AJAPI version 5.0 build 6.1.3.10212)) from ag3javabe.dll
10:01:56 04/11/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
10:01:56 04/11/2014: SystemConnection-2: Reading configuration information.
10:01:56 04/11/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
10:01:56 04/11/2014: HTTP-XML Back End: Initialized.
10:01:56 04/11/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
10:01:56 04/11/2014: Event: 20, 150, Loading Development application definitions
10:01:56 04/11/2014: Event: 20, 152, Loading Development application definitions for default localization
10:02:12 04/11/2014: Event: 20, 153, Finished loading Development application definitions for default localization
10:02:12 04/11/2014: Event: 20, 151, Finished loading Development application definitions
10:02:13 04/11/2014: HTTP-XML Back End Back End: Started
10:02:13 04/11/2014: Server: Starting threads.
10:02:13 04/11/2014:    1 initial threads.  Threads will auto-scale.
10:02:13 04/11/2014: Event: 20, 4, Server v6.1.3.10212
10:02:13 04/11/2014: Starting front ends
10:02:13 04/11/2014: ANGEL Front End: Starting threads.
10:02:13 04/11/2014:    3 initial threads.  Threads will auto-scale.
10:02:13 04/11/2014: ANGEL Front End: opening listen socket on port 7003
10:02:13 04/11/2014: Event: 17, 10, 0.0.0.0:7003 open
10:02:13 04/11/2014: Event: 17, 10, ANGEL Front End v6.1.3.10212
10:02:13 04/11/2014: Event: 0, 0, Old log files moved into D:\SAP\MobilePlatform\Servers\UnwiredServer\logs\sap.manager.2014\Rolled\2014-04-11-100148
10:02:13 04/11/2014: Event: 0, 23, SAP Mobile Platform
10:02:13 04/11/2014: Event: 0, 2, Server startup is complete.
10:02:13 04/11/2014: Agentry Application startup complete

[Agentry]
messageLogFile=messages.log
eventLogFile=events.log
logMaxSize=0
logRollTime=1:45
logRollsAtTime=true
systemName=SAP Sales Manager Server v2.5.4.0


[Server]
autoRegister=true
inactiveTimeout=600
allowRelogin=true
notifyUserOnLogout=false
notifyUsersOnShutdown=false
userKey=POKMHFMHKHKGOKWO
devKey=AVWOILFNCKHCHXMA
expKey=POKDHKMJFEIAAUYG
publicKeyLength=2048


[Server Administration]
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true
;trustedCertificateStore=
;authenticateClient=false
; If you wish to bind the Server Administration ports to specific TCP ports, 
; use the settings below.  Each one takes either "port number" or 
; "interface address:port number".  Only the interface name in commandPipePort
; is significant, and controls which interface both ports will be bound to.
; The statusPipePort must either contain the same host name, or only a port
; number, or the server will fail to start.  Both values default to 0, which
; causes both ports to be allocated dynamically and bound to all interfaces.
;commandPipePort=0
;statusPipePort=0


[Front Ends]
1=angelvine.dll


[ANGEL Front End]
trustedCertificateStore= 
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true
authenticateClient=false
timeout=300
keepAliveTime=60
;Leave the Cipher Strength settings commented out for the system to select them automatically.
;minimumCipherStrength=40
;maximumCipherStrength=512


[ANGEL Front End Ports]
1=7003
;2=127.0.0.1:7013


[TCP Front End]
listenOn=7001
timeout=300


[Configuration]
developmentServer=True
enableOverrideFile=Enables.ini
clientStringsFile=ClientText.ini
applicationStringsFile=ApplicationText.ini
applicationGlobalsFile=Globals.ini
clientStringNamesFile=ClientStringNames.ini
overrideTypesFile=OverrideTypes.ini
transmitConfigurationFile=TransmitConfigurations.ini
enableTransactionFailureHandling=false
enableFailedTransactionLogging=true
failedTransactionsQueue=FailedTransactionsQueue
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
apnsEnabled=true
apnsCertificateDirectory=apnsCertificates
apnsCertificatePassword=Rzdrj~SwixoAqzmbVxgi
apnsCertificatePasswordEncoded=true
gcmEnabled=true
gcmServerLink=https://android.googleapis.com/gcm/send
gcmServerAuthorizationKey=Authorization:key=AIzaSyDi0qWQEewdbmNSV_o9QNtSQrlxPnBXtBM
trustedCertificateStore=


[Agents]
1=ag3.dll


[System Connections]
2=ag3httpxmlbe.dll
1=ag3javabe.dll


[Web Server Front End]
listenOn=80
permitGetCGI=true
xslDirectory=xsl
resourceDirectory=resource
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true


[Web Server MIME Types]
ico=image\x-icon
wmls=text/vnd.wap.wmlscript
png=image/png
gif=image/gif
css=text/css


[Server Side Clients]
1=ServerSideClient.dll


[SpinDoc]
os=windows
facePath=sql\custom;sql


;Use this section to enter TimeZoneAlias values
[TimeZoneAlias]
[Java-1]
name=Java Back End
constantsFile=
deleteSource=true
enableAuthentication=True
enablePreviousUserAuthentication=True
initialHeapSize=256
maxHeapSize=526
nonStandardJavaOptions=
outputDirectory=.
performCompile=false
printBusinessLogicStackTrace=false
printStackTrace=false
reduceOSSignalUse=true
scriptsPath=
sourceDirectory=.
timeZoneName=
classPath=.\Java\Agentry-v5.jar
serverClass=com/syclo/agentry/Server


[HTTPXML-2]
name=HTTP-XML Back End
authenticationCertificateStore=MY
authenticationCertificateStorePassword=
authenticationCertificateStorePasswordEncoded=false
autoDequote=true
baseURL=http://localhost:81
basicAuthenticationPassword=
basicAuthenticationPasswordEncoded=false
basicAuthenticationUserID=
constantsFile=httpxml_sd.ini
enableAuthentication=True
enablePreviousUserAuthentication=True
httpConnectTimeout=60
httpReceiveTimeout=300
httpResolveTimeout=60
httpSendTimeout=300
listenOn=81
timeout=300
timeZoneName=
useSSL=false
xmlAllowXSLTScript=true
xmlNamespaces=
xmlResolveExternals=true
xmlValidateOnParse=true

What am i doing wrong ?

Thank you .

[Former Member · Accepted solution]

In the [HTTPXML-2]   section change:

enableAuthentication, and enablePreviousUserAuthentication to false.

Also, you need to check your classPath for your Java-1 section as you are misisng Jar file, Your serverClass line needs to be updated to the application's server class.

[Former Member · Accepted solution]

I already tried that. Did you implemented this solution before ? Thank you for your help, I already soled the problem.

[Former Member]

Hi Gian,

I am using SAP Sales Manager 2.5.0.0, and I am looking for the documents for upgrading to version 2.5.4. I am not able to find any related SAP documents about this but fortunately I found your thread here. If I am understand your thread correctly, are you upgrading your Sales Manager from version 2.5.1 to 2.5.4?

I am using Sap Sales Manager 2.5 v.6.0.32 (StandAlone), and it is connected to SAP CRM Backend which is working fine for now. In version 2.5.0, there are a few limitations of the application, and I see that it had been overcome in version 2.5.4. Therefore, I would like to implement this upgrade.

I am not using SMP 2.3 but just Agentry Standalone because Sales Manager 2.5 is working fine in the standalone server. Is SMP 2.3 must be use for Sales Manager 2.5?

I am really appreciate if you can provide me some links of documents which you currently have, and give me some high level details of how to setup Sales Manager 2.5.4.

Thank you.

Regards,

Edison

[Former Member]

Migrating Sales Manager 2.5 to Sap Mobile Platform 2.3 SP4 (Environment)

I Finally solved the problem and these are the steps :

Prerequisites:

1. Sap Mobile Platform 2.3 (SP4) & Agentry (6.1.3.10212).
2. Agentry Server (6.1.3.10212).
   
3. Eclipse Version (3.7.2) & Agentry Editor Plugin (6.1.0.3).
   
4. Sap Sales Manager 2.5 v.6.0.X (StandAlone), it must be installed and correctly setup to connect to your Sap Back End.
   

Migrating process:

1. Import your Sap Sales Manager (6.0.38) to your Eclipse editor pluging.
2. Export the new Sap Sales Manager (6.X) to your Agentry Server (6.1.3.X)
3. Create a zip containing the following files.
   
   
4. Finally go to your SMP 2.3 SCC and Import the ZIP.  ( if you dont konw how to, go to infocenter guide, its easy ).

Thank You.

Gian Vera