CCO Manager installation with many CCO Clients

[Former Member]

Hello Community,

we have the following situation: 110 CCO Clients with Release 2.07 FP03 - They all have set the Web Point Information for the CCO Manager with the Admin User credentials. At the Server the CCO Manager doesn't exist.

Now i try to install yesterday the CCO Manager 2.0 FP07 PL08 at the server. I use the same Admin User credentials like the Web Point Information in the CCO Client. I hoped they can all connect after installation at the same time. After successful message of installation the logging file from the "CustomerCheckout Central Server" runs full with error logs like the following:

------------

2020-01-21 15:06:20,148 [http-nio-8080-exec-68] INFO  com.sap.scco.cs.security.UserAuthManager - Login failed for User with uuid c82f2c2f-0319-40d1-85dd-fcb7fc1cc9a82020-01-21 15:06:20,149 [http-nio-8080-exec-68] ERROR com.sap.scco.cs.webapp.DefaultExceptionMapper - Exception occured: javax.persistence.NonUniqueResultException......

------------2020-01-21 15:06:20,273 [http-nio-8080-exec-43] INFO  com.sap.scco.cs.security.UserAuthManager - Login failed for User with uuid c82f2c2f-0319-40d1-85dd-fcb7fc1cc9a82020-01-21 15:06:20,274 [http-nio-8080-exec-43] ERROR com.sap.scco.cs.webapp.DefaultExceptionMapper - Exception occured: javax.persistence.NonUniqueResultException......

------------

And in additional, i can't connect with the Admin User after installation to the CCO Manager. (Screenshot)

My Questions:

1.) Can i use this way of installation with the CCO Manager in case that all Clients do have the Web Point Information already set? Or do i have to close the Port 8080 while installation running the CCO Manager Setup.

2.) Is it even possible that CCO Manager can add/connect 110 CCO Clients directly after installation?

3.) What happpend if one or more CCO Clients are configured with an incorrect password in the Integration settings? Will the Admin user then automatically locked?

Hope i explained the situation clearly enough and someone can give me an hint.

Thank you very much.

Kind Regards, Daniela

[JoergAldinger · Accepted solution]

Hello Daniela:

I can't speak of any "official recommendations", but based on our experience, here are my suggestions:

1. You should be able to keep everything up, although I would suggest to upgrade CCOM during non-work hours, and if you want to go one step further, yes you could probably block port 8080 during the upgrade, although I don't think it's necessary.
2. Yes, I don't see any reason why it shouldn't.
3. The password issue is important. We have learnt that the best way to connect CCO clients to CCOM is using a "technical user" (there's a checkbox for that in the CCOM user administration). You should never use an admin user for synchronization (technical) purposes so you can keep your technical and administrative credentials separate.

I hope this helps...

Best regards,

Joerg.

[Former Member · Accepted solution]

Hello Joerg,

i installed the CCOM again and used another User for fisttime logging. In further step i go the way you sugessted and create an runtime ["technical user"] user only for the connection via WebPoint to CCOM. I think there are some POS with wrong credetianals and thats the reason, why the Admin User locks itself out. I guess i have no other chance, to go on every single POS and set the new technical user.

Thank you very much...

Best Regrads,

Daniela

[Erlasr]

Hello Experts,

Has anyone experienced an issue with SAP CCOM Admin user as We're facing strange issue with SAP CCOM Admin user login; when we tried to login with Admin user after initial setup, its giving error message 'MESSAGE_LOGIN_FAILED'

I'm open for suggessions in this regards.

[JoergAldinger]

Hello Daniela:

As an additional note, I believe somewhere I have also seen a recommendation on not using the same technical user for all CCO clients. This would help minimize any synchronization issues for authentication reasons. E.g. you could create 4 technical users and set up approximately 25% of all CCO clients to use one of those technical users. That way, if a problem does occur with one of those users, you could still have 75% of the terminals up and running...

Just an idea, I don't know if it makes sense in your situation...

Best regards,

Joerg.

[Former Member]

Hello Joerg,

thank you again for your hint :-). I've read in the Documentation the following recommendation for the Technical User:

For performance-related reasons, we also recommend using several users with the Technical user role in large system landscapes. For example, maintain a separate communication user for every 10 SAP Customer Checkout applications.

So we gone this way and created serveral Technical Users.

Best Regrads, Daniela