DMS Connector for KM - index issues - single sign on

[former_member540174]

We are at EP 7.0 SPS 14 with an ECC at 5.0.

I had our basis install the BP DMS ConnectorKM 1.0 and then the support pack BPDMSCONN01 9-20000787.sca.

I wound up with two repositories being created one called dms and the other dmsrm. The dmsrm repository is working fine and we are seeing the expected data. The problem comes in with searching the dmsrm repository. We receive logon errors when trying to create the index. We use single signon. I found note 686776 referencing problems loging on to ABAP though KM which is my problem exactly (Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect. Please re-enter)

When I went to index_service to put the ABAP user id we want to use the System drop down does not contain my ABAP system.

Here are the Potential reasons listed in the error box

• The selected principal does not have end-user permissions for the system.

• The system's logon method does not require any user mapping data for the system (such as "SAPLogonTicket" for a system that is not the SAP reference system). This is true - do I create another system and not enable logon ticket?

• The system's user mapping type is not set correctly or not set at all.

• There is no system alias defined for the system.

• There is no system landscape registered, for example, the one contained in Enterprise Portal.

Any guidance on how to get my ABAP system to display in this drop down?

dmsrm

Description:DMS Repository Manager

Prefix: /dmsrm

Repository Services: Not set

Property Search Manager:

Versioning Manager:

Security Manager: Not set

ACL Manager Cache: Not set Windows Landscape System:

Lock Manager:com.sap.pct.plm.dmsrmconnectorforkm.DMSRMMutableLockManager

ReadOnly: YES

ShowClassification: Yes

ShowObjectsLinks: Yes

ResourceValidity:30000

StorageCategory: DMS_C1_ST

SystemAlias: SAP_R3_QWA

VariantPrefix:KM

Regards,

Diane

[Former Member · Accepted solution]

Dear Diane.

1.Check if either the user index_service or the group Everyone ( index_service user is a member of this group) has End User Permissions on your system SAP_R3_QWA.

2.Then make sure that you have configured your SAP_R3_QWA system as SAP reference system. If necessary repeat all steps described in [Configuring a Reference System for User Mapping|http://help.sap.com/saphelp_nw70/helpdata/en/4d/dd9b9ce80311d5995500508b6b8b11/frameset.htm]. In your scenario the following system properties for User Mapping will be enough:

a) User Mapping Type is set to admin

b) Logon Method is set to SAPLOGONTICKET

Do not hesitate to ask further questions.

Best regards,

Aliaksandr Zhukau

[former_member540174 · Accepted solution]

1- Everyone group has end user authority

2- System Alias SAP_R3_QWA

*User Mapping Type = admin, user

*Logon Method = SAPLOGONTICKET

System does not show on the mapping tab on the index_service user.

So I started digging to see if I could change the userid used by the index - found that but didn't help in the end....

Changed the userid used by the index via the Global Services>Index Management Services

User management exception: Could not get service user "xxxxxxxxx" - this user is the ID we use on our web dynpro JCO connections. So that didn't help - set it back to "index_service"

Looking at my System definition - it works and has about 10 alias defined. The User Mapping was already populated in fact all items you listed were already defined as requested...the only problem is that the system doesn't show up in user mapping (WebEx is the only thing in User Mapping - comparing them nothing really stands out to me other than the systems are based on totally different templates).

Any other fields I should check?

Regards,

Diane

[Former Member · Accepted solution]

Hi Diane.

System SAP_R3_QWA should be defined as a reference system:

1. Start User Management Configuration (for more information, see [Configuring User Management|http://help.sap.com/saphelp_nw70/helpdata/en/e5/618a3eacd49076e10000000a114084/frameset.htm]).

2. Choose the User Mapping tab.

3. In Reference System, select the system alias SAP_R3_QWA.

4. Restart the AS Java.

Best regards,

Aliaksandr Zhukau