Portal connectivity

Hi,
While connecting MDM Server to the Portal in Step where you create the system and enter the MDM server name and password.
The MDM server connectivity is fine and works if used to connect to MDM system-Sql server. This is remote server.
When I try connecting MDM server - Oracle based installed locally on my PC (localhost) the MDM server the connectivity to portal fails mentioning "Failed to connect to MDM server. Check your system"
Any ideas why such a strange behaviour or am missing something.
Thanks you guys, KP.

Hi Kris,
Your system with 1st MDM server is working fine right!!.... did you create new system while connecting to other MDM Server or you just changed the connection parameters? Ideally, this should not cause any problem but then also try creating a new system and try to point it to the new MDM server.
Hope this works for you.
Regards,
Mausam

Similar Messages

How to use the Portal Connection Service in a standard J2EE application

Hi,
We want to use portal connection service to connection backgend system from a standard j2ee application.
But the connection need a connectionProperties object which is created in this way:
ConnectionProperties connectionProperties =
new ConnectionProperties(
request.getLocale(),
request.getUser());
Because the "request" object is IPortalComponentRequest object, which is a portal object. In our standard application, we can use this way.
So how?
Thanks and Best Regards,
Xiaoming Yang

Does anybody has any idea? Many thanks and points will definitely be awarded.
Best Regards,
Xiaoming

Two portals connected to one BW system

Hello
Do you have any experience or just some information on the solutions when two portals are connected to one BW system? I am just wondering, is it possible?
Thanks in advance,
Arelis

We have done the same thing for ESS we had to portals connected to one r/3 but beaware when we change the config for one on the backend r/3 side the settings for the other is also affected.
there is no issue with the load in this scenario and applications work fine independently as well.
but before doing this just ask your self it is really required cant i create 2 differnt roles and manage the display of the same using the themes?
but still if u wan tot do the same it is possible

Com.sap.portal.connectivity.destinations.PortalDestinationsServiceException

Hi
I am getting this error for some users in the portal.
com.sap.portal.connectivity.destinations.PortalDestinationsServiceException:User is missing credentials for connecting to alias SAP_R3_humanResources.
This is only happenning for some of the users at the moment and I cannot figure out what is causing it.
We have:
EP7 for Online Expenses
ECC6
I have re-registered the WebFlowConnector just to see if thats the problem.
I have checked the users portal roles and his backend roles and all are OK
I have also checked the Web Dynpro connector for SAP_R3_HumanResources.
Can anybody help me out on this please.
Many Thanks
Steve

Got this from SAP
1st reply
The UWL_service was introduced in NW 700. So, 1133821 will not be relavant for NW 6.40. However, in 640 system we use Basis plugins.
So, to check that please provide me the complete backend system version. The UWL uses functions from the Basis plug in instead of the Enterprise Portal plug in (WP-PI 6.0) for back end systems using Release 640. Support Package 12 makes the necessary functions available in the Basis. You can make the necessary changes in the Basis plug in (PI_BASIS) using notes or Support Packages.
Could you please check which release are you on? Remember after you applies this (SP12), you will need to reregister the UWL system in the system admin on the portal. *This is not only for substitution, but for other functionality as well* We recommend this for 640 systems in general that the PI_BASIS is maintained at the highest level.
This warning message will occur for users that do not have access to the systems that are configured in the UWL UI. For example, if we have 1. BW system 2. SRM system, and you 'steve', are able and have access to the BW system, but do not have a Userid in SRM backend, you will receive this msg. This is normal behaviour for the Universal worklist. So your option there would be to create a dummy id for you on the backend system so that your id can connect but that you don't have auth to.
2nd reply
You seems to be on lower version for Basis Plug-ins. The basis plug in should be at version 12 or higher and is at version 9. You will need to ensure that the users exist in both systems to get rid of the warning messages. Details for the Basis Plug-ins can be found on Note:883558.
3rd reply
If I am right then you are talking about the solution provided to get rid of the warning message.
So, in this regard as Steve already mentoned The Portal is an EP7 portal running on NW 7.0 SP20. It has to connect to {2 different R3 backends}.
1. ECC 6 running on NW 7.0 and UWL is configured with a SAP_ECC_TRAVEL WebFlow Connector (this works perfectly)
2. ECC 5 running on NW 6.40 and UWL is configured with a SAP_R3_HumanResources WebFlowConnector (please see attachment for error)
So, In reply to this I mentioned that to get rid of the warning message you have create users in both the systems. May be you do not grant authorization as per your requirement.
because these warning message are been displayed because the UWL UI havebeen configured to pull tasks from 2 backends. and User logging in mighthave access to only one backend system so, that's the reason for other R3 system they get the warning message.
Or if there is a concern with basis Plug-ins then it will be adviced to refer to the Notes, as those are system requirement.

How to check ABAP and Portal connections

Hi
I was told to check ABAP and Portal connections. What does that mean? And what and where to check?
Thanks
Annie

Hi
Thanks for your reply.
We are on BI 7. SP16.
When i run that in se38, i am getting the following information: No default in RSPOR_T_PORTAL and no user parameter RSPOR_DEFAULT_PORTAL" when i clicked on yes(tickmark), view BI_Content of web template 0ANALYSIS_PATTERN(A) is displayed
There are two options with check box are present 1. 30 template present (Unchecked) 2. BI- Template Present (checked), and a big XML code is displayed.
When i executed in browser mode, it says Windows cannot find'/irj/servlet/prt/portal............... make sure you typed the name correctly and then try again. to serch for a file, click the start button, and then click search"
What does that mean?
Regards
Annie
Edited by: Annie on Nov 17, 2008 5:38 AM

Portal connection to BW production

hi,
can anyone help me on this please:
its regarding portal connection(SPP) to BW production (SBP).
while trying to upload BW role to portal i am getting the erro mesag - "connection to BW system failed".

Hi Muthaiyan,
For Integrating BW with EP, these links will be helpful
[Integration of SAP BI 7.0 and SAP EP 7.0|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a]
[How to Connect to BW System through Enterprise Portal 7.0 Using an IView|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/EP/HowtoConnecttoBWSystemthroughEnterprisePortal7.0UsinganIView.&]
[Configuring EP for connecting to BW|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4378]
[SSO between BW and EP|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/EP/SSOtoBWinEP+6.0&]
Hope this helps,
Regards,
Shailesh Nagar

Use webdynpro without portal connection

Hi friends,
Is there anyway to use webdynpro at home pc without any portal connection?
Is it possible using any other software?
Thanks...

Hi,
Web Dynpro as you know is server side application which will be rendered by client on request by browser." webdynpro at home pc without any portal connection", ---means you are trying to access(not develop) Web Dynpro appln from home...which is possible since Web Dynpro's APPLICATION part is accessible using URL.
If you want to develop Web Dynpro application from home, you should be able to access server(WAS) to deploy application.
Regards,
Ganga.

Error while testing ECC and Portal-Connect to SAP gateway failed

Dear Experts,
While testing ABAP connection in Portal i am getting below error.

Dear All,
My error is rectified with below thread.
SLDCHECK: Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMIT'...
Hi,
You need to create an RFC to the SLDCHECK:
1. In your web browser, enter the URL of SAP NetWeaver Administrator using the following pattern:
http://<host>:<port>/nwa
2. Choose Configuration Management u2192 Infrastructure u2192 Jco RFC Provider.
3. Choose Create.
4. Enter the connection and transport parameters as required.
Field
Description
Program ID
We recommend that you use the following pattern: SLDAPI_<SAPSID>, where SAPSID is the system identifier of the AS Java system.
Gateway host
Gateway service
If your AS Java is an add-on installation to an ABAP system, use the gateway of the ABAP system. You can look up the gateway parameters of an ABAP system using transaction SMGW.
If your AS Java is a standalone installation, we recommend using a gateway on the Central Services Instance host. As of SAP NetWeaver 7.1, usage type AS Java that comprises SLD also contains an SAP RFC Gateway.
Server Count (1..20)
Enter 3.
5. Choose Next.
6. Enter logon data to the ABAP repository. You can either use an existing RFC destination from SAP NetWeaver Administrator u2192 Configuration Management u2192 Security u2192 Destinations or you specify the ABAP repository explicitly. The destination should point preferably to an AS ABAP close to SLD. If SLD is running on an AS Java standalone installation, the calling AS ABAP can be used instead. We recommend to create and use an RFC destination instead of explicitly specifying the connect parameters here. In both cases, the following parameters are required
Field
Description
System Landscape Directory 15
User Manual 03.04.2008
Application Server Host
System Number
Client
Language
User
Password
Enter the logon data for the AS ABAP system. You must specify an existing user with appropriate authorizations for RFC.
If you are running a system with both usage types AS ABAP and AS Java, use the logon data for this system.
If your AS Java is a standalone installation, use the logon data for the calling ABAP system.
7. Choose Next.
8. Leave the default values in the next steps.
9. Create the Jco RFC destination by choosing Finish.
Result
The Jco RFC destination creates a number of u201CServer Countu201D RFC server threads on your AS Java. These RFC servers register at the RFC Gateway specified. You may configure multiple ABAP systems to connect to these RFC servers. In this case, the Server Count should be increased when TIME_OUT exceptions are observed.
Creating an RFC Destination for the SLD ABAP API on the AS ABAP Side
Use
If you want to configure an ABAP application to access data in the SLD through the SLD ABAP API, you have to create an RFC destination on the ABAP system side.
Prerequisites
An RFC destination for the SLD ABAP API is created on the AS Java side.
Procedure
1. Call transaction SM59.
2. Select TCP/IP connections and choose Create.
3. In the RFC Destination field, enter SAPSLDAPI.
4. On the Technical Settings tab page, select the Registered Server Program indicator.
5. In the Program ID field, enter the same program ID as the one you entered when you created an RFC destination for the SLD ABAP API on the AS Java side. We recommend that you use the following pattern: SLDAPI_<SAPSID>, where SAPSID is the system identifier of the AS Java system.
6. Choose MDMP & Unicode and select the Unicode indicator.
7. Choose Save.
8. Test the RFC destination by choosing Connection Test.
If the display shows the response times, you have configured the RFC destination correctly.

Multiple ESS's in one Portal connected to different backend systems?

Hi,
We have two backend systems installed.
We have one portal.
We want to create a second copy of the ESS Portal content connected to the the second backend.
Datawise this is not a problem.
But what about the JCo's and the Homepage Framework?
The WebDympro application seems to look for two specific JCo (for example SAP_R3_HumanResources and ...MetaData) and then both copies of ESS want to use this. Is it not possible to have each copy of ESS use it own JCo's and connect to its own backend system for the Homepage Frameworks?
Thanks,
Adriaan

Adriaan,
Its NOT possible to even talk to different clients in same backend system because you cannot duplicate the JCos and while creating them you need to specify the system and client details.
Also it uses a system alias which also has to be unique.
Per my knowledge one portal instance can talk to only backend client and to talk to another backend / client you will need to create a new instance within the Portal.
This [help|http://help.sap.com/saphelp_nw2004s/helpdata/en/82/76a2406546ba15e10000000a1550b0/frameset.htm] talks sometihng on multiple backend support. I am not much aware about it but see if it helps you.
Chintan

Content Server and Portal Connectivity

Dear Experts,
I m using this content server to connect with the Portal 7.0, as I m working with LSO and my content server is working fine as below....
serverType="SAP HTTP Content Server";serverVendorId="Copyright SAP AG, All rights reserved 1998, 2001";serverVersion="6400";serverPatch="1";serverBuild="190";pVersion="0046";serverStatus="running";serverStatusDescription="";serverDate="2009-02-05";serverTime="10:47:29";startUpDate="2009-02-05";startUpTime="10:40:34";lastAccessDate="2009-02-05";lastAccessTime="10:41:40";
contRep="ZADGAS_LSO";contRepStatus="defined";contRepStatusDescription="";contRepDescription="Content Server for LSO";contentStorageHost="xxx-xxx-cont";contentStorageName="LSO";secKeyVerification="y";defaultDocProt="";
Now, I want to connect Portal and content server with the URL...for data storage in the content server.
I m trying to use this URL, but is is not working...
http://xxx-xxx-cont:1090/ConTentServer/ContentServer.dll?adminContRep&operation=docIdList&contRep=ZADGAS_LSO
Can you please let me know what is the issue or should I make some configuration to this and please send the config documents to me ...at
ahmad.siddiquee at gma!l
Thanks in advance.
Ahmad

Dear All,
I want to connect SAP content server through Authrouing Environment for uploading the data in the content server.
I want to use content server as WEBDAV REPOSITORY for access the docs.
I think ... shared drive thing would work...only if the repository is created in the file systems isnt it?
I m not sure about it
Any help will be appreciated .
Thanks,
Ahmad

NW2004s Connect to Message Server Host Failed - BW to Portals connection

Hi,
I am trying to connect a SAP BW NW2004s Patch 8 system to a NW2004s Portal. All of the checks in RSPOR_SETUP are successful.
However when I try to launch a query from Bex Query it fails with the following message.
"Connect to message server host failedConnect_PM TYPE=B MSHOST=SAPMSCR6 GROUP=webshop1_biw R3NAME=CR6 MSSERV=01 PCS=1"
The message server entry in the System Landscape object for the BW Server is "SAPMSCR6". Is this right?
I have searched for information about this and can't find anything. I am sure it is something basic. As anyone else resolved this issue or do they have an idea what might be causing the problem?
Any suggestions gratefully received.
Dave

Guys look at the below SAP note. it will help
SAP Note Number: 764881 Inf. Broad.Connect to message server host failed - sapms

ECC6 and Portal connectivity

Hi all,
when i try to connect to the portal with my ECC6 account user, i can't,
i filled UME, Abap tab with connection data.
the user mentionnned on the portal is of COM type. created on ECC too
Please help

Dear Nabil,
Please try to the Refreshing the User Caches in the UME from System Administration > System Configuration > UME Configuration > Support. Refer to the SAP Note 1118873 - UME Cache settings for Netweaver
Also look for default trace log file for more details about old user issue. May be Old users are not synchronized in UME.
Hope it will helps
Best Regards
Arun Jaiswal

MDM 7.1 Portal Connectivity to MDM server

Hi all
I was running the MDM 7.1 ramp up version so far with full connectivity from the portal to MDM. I had configured both the standard business partner and a custom repository using the Portal Business Content . Now that I have migrated to the just released MDM 7.1 (GA ) , I am encountering the following error at the portal level . I am using the standard "Using Mapping" to connect to the MDM server from the portal and not the newly introduced "Trusted Connection" . Any body has any clue as to whats going wrong ..
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)... [see details]
DETAILED MESSAGE
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)
at com.sap.mdm.admin.utils.MdmConnectionProvider.createBlobObjectCache(MdmConnectionProvider.java:308)
at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.initContexts(MdmeBaseDynPage.java:364)
at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.doProcessBeforeOutput(MdmeBaseDynPage.java:154)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:127)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:126)
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:56)
... 38 more
Thanks
Ray

Hi Ray,
This is a trusted connection problem. For this you need to create allow.ip and deny.ip files in your server. In allow.ip you need to give those ip address through which you would be connecting to MDM server executable file(mds.exe) like in your case your portals ip address. And in deny.ip you need to specify those ip which you feel shouldnt connect to MDM server. After assigning this ip remember to restart your mds.
Also the users through which you are trying to connect to an MDM repository, their usernames must exist on the MDM repositoryu2019s Users table.
For more details please see page 299 from MDM 7.1 Console refernece guide
I hope I am able to solve your problem
Thans & Regards
Dilmit Chadha

Portal connection to multiple backend BW app servers.

When our portal was installed (java stack intended for Integrated Planning with ABAP BW system) the BW system only had a Central Instance. Since then an application server has been added on the BW side. However, Integrated Planning only works from the CI because that is what the Portal JCo's are configured against. so it cannot connect with the new app server. Integrated Planning (via RSPLAN) from the app server will fail as the connection will now work. This is causing some issues with users logging into BW. If they want to do integrated planning, they must be on the Central Instance, not the app server. For one thing, this defeats the purposes of load balancing if everyone logs onto the CI. The question is can the portal be configured to connect to an additional server for the same BW system. I'm not seeing any options in the JCo's for multiple servers for the same system. Any pointers or feedback would be greatly appreciated.

Running RSPLAN from the Central Instance brings up a browser with a logon screen and the the correct URL:
http://<portal server>.mikl.com:<port>/webdynpro/dispatcher/sap.com/biplanworkbench1/Modeler?
But running RSPLAN from the new app server brings up a brower with an error message, and the URL is:
http://<BW server>:0/sap/public/myssocntl?sap-client=100
error message:
Error 401
FW-1 at cpwgw: Unauthorized to access the document.
Authorization is needed for FW-1.
So a translation is not happening somewhere. I verified that the myssocntl service is turned on. And it works just fine for the CI.

User creation in Portal Connected to LDAP

Hi Gurus,
   i want to know if we have LDAP connected to a Portal and someone creates a user on Portal UME , will the user get created in LDAP or portal UME.
   The situation is where any registerd user accessing the portal should be authenticated against LDAP and he can also do a self registration from portal.So if he self registers, does his user id/Password gets created in LDAP or it stays in Portal UME.If it gets stored all the way to LDAP then we are fine, if not , then is there a way to replicate this user id password to LDAP.
Thanks in Advance!

>
Gaurav Garg wrote:
> Hi Gurus,
>    i want to know if we have LDAP connected to a Portal and someone creates a user on Portal UME , will the user get created in LDAP or portal UME.
User will be created in UME only not in LDAP.
>    The situation is where any registerd user accessing the portal should be authenticated against LDAP and he can also do a self registration from portal.So if he self registers, does his user id/Password gets created in LDAP or it stays in Portal UME.
No the user is created in UME database and not in LDAP. If you are setting up your user persistence in LDAP (authenticating users from LDAP) then you have to setup users in LDAP. UME has a read only access to things that it pulls from LDAP.
Regards,
Zaheer

Portal connectivity

Similar Messages

Maybe you are looking for