on 01-11-2010 6:27 PM
We are performing a technical upgrade of ECC5.0 to ECC6.0 and we are seeking confirmation and instructions for connecting our existing ISA4.0 system to ECC6.0. I have searched OSS and SDN and queried our SAP account manager for some confirmation and documentation on ISA4 and ECC6.0 compatability
Any advice, confirmation and documentation on connecting Internet Sales version 4.0 component to ECC 6.0 is greatly appreciated.
Here are the details of our ISA4 system
Kind regards
ISA System
sap.com SAP-JEE 6.40 SP9 (1000.6.40.9.0.20041119045409)
sap.com com.sap.mw.jco (6.4009.00.0000.20041026130530.0000)
sap.com com.sap.security.dbschema (6.4009.00.0000.20041115123517.0000)
sap.com crm.b2b (400.200904212104)
sap.com crm.b2b_lanl (400.200904221705)
sap.com crm.b2c (400.1020060105115443.0000)
sap.com crm.mcm (400.1020060105115443.0000)
sap.com crm.shopadmin (400.1020060105115443.0000)
sap.com crm.trexr3 (400.1020060105115443.0000)
sap.com IAIKSecurityFS (1.3.12)
sap.com isacoreddic (400.1020060105115443.0000)
JDK 1.4.2_11-b06
TREX6.1
Windows 2003 (x86) 5.2
Warm regards
Lee Lewis
Hi Lewis,
For me it looks like nothing wrong with B2B ISA Application, Might be missing some thing at B2B user creating at backend level, roles, contact person settings, assigning shops to B2B user.
Reagrds,
Dev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To all, and others that might experience this issue, here is the cause and a solution.
In java method:
com.sapmarkets.isa.user.backend.r3.rfc.RFCWrapperUserBaseR3.getCustomerFromUser
There is a rfc call to BAPI_USER_GET_DETAIL, with ecc6, the parsing of the customer identifier was turning up null:
JCO.Table par = function.getTableParameterList().getTable("PARAMETER");
if (par.getNumRows()>0){
par.firstRow();
for (int i = 0; i < par.getNumRows(); i++) {
if (par.getString("PARID").equals("KUN")) {
customer = par.getString("PARVA").toUpperCase();
}
par.nextRow();
}
}
Upon defining a new kind of user, with the parameter implied by the code block above, we were able to log into the application successfully, and so far testing has been very promising.
This was the second part of the puzzle, the first part was defining JCO userid with a password that uses UPPER CASE ALPHA's.
Hi Lee,
As per the ISA application you can go with the same XCM setting just changing the ECC parameters from ECC 5.0 to ECC 6.0
eg. ip address, jco parameters.
Copy all the custom function modules related to ISA.
Regards,
Devender V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Devender,
My name is Ed Lizewski, I'm a J2EE programmer employed by Summit Electric, working with Lee who first posted the message.
Using your advice, I conducted a test by creating a XCM test jco component configuration profile, using the parameters for our ECC 6 installation, i.e. server host name, client, lang, user, passwd, sap sys number. When I run the jcoping test, I get the following error:
Connection failed com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon)
We verified that the user name and password are correct. Is there something else I need to do, such as replace the jar file(s) for the jco connector?
Thanks, Ed
When an incorrect password is entered, the expected message:
"Name or password is incorrect (Please repeat logon) "
is displayed. When the correct password is entered, this message is displayed:
"Error in user administration"
No error messages are logged during the login attempt, only the following:
Message , Datasource
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='end' [actionclass]='com.sapmarkets.isa.isacore.action.b2b.LoginAction' [path]='/b2b/reallogin' [forward]='/b2b/login/login.jsp' [exectime]='94' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='BAPI_USER_GET_DETAIL' [ashost]='sapsbx' [sysid]='SBX' [exectime]='31' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='BAPI_USER_GET_DETAIL' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='SUSR_LOGIN_CHECK_RFC' [ashost]='sapsbx' [sysid]='SBX' [exectime]='15' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='SUSR_LOGIN_CHECK_RFC' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='RFC_SYSTEM_INFO' [ashost]='sapsbx' [sysid]='SBX' [exectime]='0' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='RFC_SYSTEM_INFO' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='begin' [actionclass]='com.sapmarkets.isa.isacore.action.b2b.LoginAction' [path]='/b2b/reallogin' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='end' [actionclass]='com.sapmarkets.isa.isacore.action.DetermineBrowserVersionAction' [path]='/b2b/login' [forward]='/b2b/reallogin.do' [exectime]='15' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='begin' [actionclass]='com.sapmarkets.isa.isacore.action.DetermineBrowserVersionAction' [path]='/b2b/login' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.