MSS iviews cannot connect - Connection Test not working

[Former Member]

Hi,

I've just installed EP6 SP11 P3 from SR-1 and imported a role from EP5 that contains some MSS iviews (Business Package 50.4.2).

Connection & SSO is working for the ESS (ITS) & SAPGUI iviews but the MSS iviews are giving a "Could not connect to R3 system" error message.

I've tried the Connection Test for the relevant System - the ITS one passes, but the Connection Test for Connectors doesn't work... it doesn't fail or pass, or give any message at all, when you click on the "Test" button.

The error that keeps appearing in the server.log file is "Failed to get alias mappers sub context in the Portal Registry"...

Anyone come across this before, or have any ideas?

Many thanks in advance.

Regards,

Jane

[former_member194737 · Accepted solution]

Hi,

after changing ume.usermapping.unsecure=TRUE, it worked for me. I don't know the same problem for all of you.

Goto SystemAdministration>SystemConfiguration>UMConfiguration-->DirectEditing, Find the parameter and change, saveallchanges, then restart the EPApplication server.

I think if we use SSL, it'll work without changing this parameter.

I am using EP6 SP11 and MSS 601_5

Cheers,

Selvakumar S

[Former Member · Accepted solution]

Hi Selvakumar,

Brilliant, that did the trick. MSS teamviewer is working & so is the connection test. I remember now that the SR-1 installation doesn't force you to install the strong cryptography extension like the pre-SR1 did, which I guess is why we didn't have this problem before.

Thanks!

Regards,

Jane

[Former Member · Accepted solution]

It worked for me as well though I use SSO without UserMapping. Strange...

Regards

Christoph

[Former Member · Accepted solution]

I'm having this same problem, but the parameter ume.usermapping.unsecure does not exist in Direct Editing under UM Configuration. Why would it not be there and what happens if I add it?

Also, how can I tell if the jco connector is installed? It is not something that I did explicitly.

[Former Member · Accepted solution]

What version of EP are you using? The SAP JCo connector is usually installed as part of EP so you shouldn't have to install it separately.

Jane

[Former Member]

Solving the problem here was as simple as giving the user "end user" rights to the folder where the system landscape is located !!

Tell that one to Ripley ...

[Former Member]

I found part of my problem at least. SSO was not completely configured in R/3. I had imported verify.der into the PSE but not added the certificate to the ACL.

All of my ESS and MSS iviews now function properly, but the test function in the System Landscape Cockpit still gives the errors. As long as everything works, maybe I don't need to care about this, but that makes me a little nervous.

[Former Member]

I've installed EP6 SP2.

I installed jco by unzipping the package into a folder and adding that folder to the path environment variable. I also had to create the classpath env. var. as it did not exist.

I also created the entry in Direct Editing for ume.usermapping.unsecure=TRUE as it did not exist.

None of this has any effect. If I select all test options for the system test in the system landscape cockpit, I receive:

Test failed: Test for logical system portal_content/com.thq.systems/com.thq.SAP_R3DEV02

-

---

Check for launching WinGUI and PlatinGUI transactions

System attribute "Client" not found.

Test failed.

-

---

Check for launching WebGUI transactions, EasyWebTransactions and BW 2.x objects

System attribute "Client" not found.

Test failed.

-

---

Check for launching BSP and BW 3.x objects

System attribute "Client" not found.

No protocol defined for the WebAccessPoint.

The host name for the WebAccesPoint has no value.

Test failed.

-

---

ITS connection test skipped

-

---

WAS connection test skipped

-

---

My logical system SAP_R3DEV02 has aliases for SAP_R3_Cross, SAP_R3_HumanResources, SAP_R3_Financials, and SAP_R3_Travel.

I have the following parameters set for SAP_R3DEV02.

Connector

application host: r3dev02.domain.com

logical system name: dev

remote host type: 3

sap client: 200

sap system name: r3dev02

sap system number: 01

server port: 3201

system template name: sap_r3dev02

system type: sap_r3

ITS

its description: itsdev01

its host name: itsdev01.domain.com:71

its path: /scripts/wgate

its protocol: http

All the ESS iviews that use ITS appear to work. However, Record Work Times displays:

Method getCatsData] java.lang.Exception: SAP_R3_Cross: No connection to SAP R/3 System; check user name and connection

The Time Recording Calendar displays:

[Method connectToSAP(SAP_R3_Cross)] java.lang.Exception: R3_CONNECTION_FAILED

Clock In/Out displays:

[Method connectToBackend(SAP_R3_HumanResources)] java.lang.Exception: R3_CONNECTION_FAILED

For MSS, the Attendance Overview and Reminder of Dates iviews display:

Could not connect to the R/3 System

Could my problem be that I used aliases for the R/3 systems in my landscape? Should I have created them individually? Can one not be both Connector and ITS? Do I need additional parameters set in my landscape? I'm at a loss. Any help is certainly appreciated.

[Former Member]

Hi. I think you might have created the System using a false template. Your SAP system should be defined as a Dedicated Application Server for SAP R/3 System. Her you can define the necessary parameters for HOST and PORT and your connector (in the connection test) should come out with a result.

BR Kurt

[Former Member]

Hi Kurt,

I have checked that I am using the Dedicated Application Server for SAP R/3 System template & have defined the Application host & port (3200) parameters.

Rgds,

Jane

[Former Member]

I have the same problem with SP11, on another SP10 Portal the connection test works with MSS iViews. I opened up an OSS, as soon as I get a solution I will post it.

Bye

Christoph Schulz

[former_member194737]

Hi,

I am also facing the similar problem. My other two systems are working fine,those systems also of SP11, but after installing the Business package i upgraded from SP9 to SP11. 3rd system, i installed BP after upgrading to SP11. If you people get any info on this please post it.

Regards

Selvakumar.S

[Former Member]

Hi everyone,

have you checked that the user you are using to display the mss iviews has the permission to use the system object? Go to the system definition -> permissions tab and check that the user roles are assigned for the system.

I've seen this happening some times myself, make sure also to check End user with the role assignment.

-Mikko

[Former Member]

I've also opened an OSS but if anyone has any more information, I would be very grateful to hear it since this is now holding up our upgrade to EP6.

Many thanks,

Jane

[Former Member]

Hi Jane,

Lot of the MSS iviews are built in JAVA. Have you installed sap java connector on your portal(SAPJCO)?

[Former Member]

Hi Prakash,

I thought the SAP JCo came pre-installed with Enterprise Portal - I didn't have to install it on SP10 or below to get the MSS iviews to work... However I have now installed the latest version of the SAPJCo on the portal server but this still hasn't resolved the problem.

Are there any logs for the SAPJCo that perhaps would show what the problem is?

Many thanks,

Jane

[Former Member]

Hi Jane,

Could you search for a trace file rfc.trc file. Can you post the trace file.

Prakash

[Former Member]

Thank you all for your comments.

Aatar - The System Identifier setting on the iview is SAP_R3_HumanResources - which is the same as the default Alias on the System. R/3 is not load-balanced.

Other iviews (mainly ITS ones) use this alias and work - only the MSS ones do not.

Nagesh - I have tried importing the latest EP6 Business Package Team Viewer from another EP6 system and get exactly the same error so I am not convinced that importing the BP will help but will give it a go if no-one else can offer a solution. Thanks.

Nick - The connection test for connectors doesn't work - i.e. it doesn't give a result. I have checked (and double-checked!) the aliases. I don't think the problem is with the aliases or the iview... but don't know what else it could be either!

Thanks,

Jane

[Former Member]

I believe all the biz pkgs require specific system alias names to be used for connectivity. So while the system connection tests may be successful you get errors when an iView tries to connect.

Make sure your alias' are set to end-user read permissions and that the proper alias is the default.

Nick

[Former Member]

We do have the similar problem. Fixed it ith the following steps.

We have Portal EP 6 SP9.

1) Reimport MSS package. Not the content export followed by import. Instead reimported the MSS package.

2) Checked system aliases and system definitions

MSS is working fine now.

Please check system aliases carefully. MSS uses WebAS and JCO. Please make sure to have the correct port for WebAS.

[Former Member]

Nagesh,

I tried importing the MSS BP package but the error still occurs. Which version of the Business Package did you import?

Many thanks,

Jane

[Former Member]

Hi Jane

What is your R/3 Alias setting? is your R3 load balanced or not?

Regards,

AAAttar