Destinations of a portal

Hi,
I'm quiet new with SAP and NetWeaver.
I've installed the sap netweaver sneak preview 2004,
the pdk for .net and the .net connector. I can deploy
a very simple application (like the "Hello World" example)
on my deployment server and view it in the portal.
Now I'm trying to set up a proxy to communicate with
a sap system. For this, I need to make a connection to a
sap system. In Visual studio server explorer I have to
specify a destination for my portal. I can choose a
destination from a list (pdkDummySystem, WEB_AS_DB,
WEBDynpro and WebEX). If I Choose for example PDKDummySystem,
I see the BOR and Functions folder. If I click on the BOR
folder, I get the following error:
Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
Can somebody tell me what's the problem? Do I have to configure
the destination or do I have to configure something in Visual
Studio or ...?
Thanks

Hi,
Yes, you need to configure the destination in the portal (talk to your portal system admin) to have all the connection details to an SAP system, and also you need to set user mapping for this system (alias).
Note that for runtime you can use SSO instead of user mapping (this is for when you use the portalDestination as a connection source for the proxy you create).
See this:
https://media.sdn.sap.com/html/submitted_docs/dotnet/Programming%20with%20PDK%20for%20.NET/Connecting%20to%20SAP%20NetWeaver%20Systems/Using%20SAP%20.NET%20Connector.htm
and this:
https://media.sdn.sap.com/html/submitted_docs/dotnet/Programming%20with%20PDK%20for%20.NET/Connecting%20to%20SAP%20NetWeaver%20Systems/Portal%20Destinations%20Folder.htm
Regards,
Ofer

Similar Messages

Use WebDynpro JCO Destination in Abstract Portal Component

Hello,
I was wondering if it is possible to use a WebDynpro JCo Destination in an Abstract Portal Component? I have a portal component that make as JCO call to run an rfc. I get the MYSAPSSO2 ticket from the cookie and pass this in to the JCO client. This works fine. Now I need to be able to run this for anonymous users as well. I was hoping to be able to retrieve a WebDynpro JCo destination that is set up as a userid/password type and use this to make the connection to run my RFC. This way I could avoid having to store the userid and password somewhere and encrypt/decrypt it etc...
Thanks,
Bert

Yes Asusha
You can use JSP , JSPDyn pages in Abstract portal component.
You can call a Jsp file from the abstract portal component.
    public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
     com.sapportals.portal.prt.resource.IResource somePage =
               request.getResource("jsp", "pagelet/test.jsp");
               response.include(request, somePage);
Then you can made your desired UI in JSP.
Hope this helps..
Cheers
Chinmaya
Reward for helpful answers

URGENT: Failed to resolve JCO destination name 'WD_GPMS_RFC_METADATA_DEST'

Hi,
when logging in am getting com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_GPMS_RFC_METADATA_DEST' in the SLD.
I had restarted the Server & and also System.
Exception:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_GPMS_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
Accessing the System Landsape Directory (SLD) failed. Depending on the concrete reason (see root cause) check the following:
is the SLD Supplier in the J2EE engine configured correctly? See the SLD documentation for more details about the SLD and about how to configure it.
are all JCO destinations maintained correctly? Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the
Content Admin to verify that each destination is properly configured.
Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
Please help me resolving it.
Thanks,
Hussain

Hello Hussain,
It looks like your Basis team has added another JCO destination to your Landscape....just check with them and create the jco destination on the portal...to fix it.
Let me know if it helps.

How to access the SAP MDM destinations using mdm java api in 7.1

hi,
I have SAP MDM 7.1 SP11 and SAP Portal 7.3 and developing the custom webdynpro application using the JAVA MDM API. I want configure the SAP MDM destinations in SAP Portal .
How to access the MDM destinations in java code using API? and how to create the connection with MDM using the MDM destinations.
Please provide the code for access the SAP MDM destinations in java code using MDM java api and creating the connection to MDM.
Thanks

Jun,
Thanks for the reply and api information.
I have got this api information from the following sap documentation. But i am looking for the code by implementing this class and creating the mdm connection.
Creating an MDM Connection Using Java Code - SAP NetWeaver Master Data Management (MDM) - SAP Library
if any thing can you share it.
Thanks

JCO destination created but NOT showing up in SLD.

We have a portal with a centralized SLD which is tested successfully.
We created a JCO destination on the portal successfully.
However,
1) we cannot test the new jco , all buttons are disabled except the "create" button;
2) if we click above "create" button, we end up with "Jco already exist, cannot create";
3) we go to the centralized SLD, see no jco destination there for this portal.
Very strange. Please help. Thanks!

Which user id are you using to login? Please check the authorization of the user.

Connection problems portal - BI

Hello,
We are trying to connect the BI system with a BI portal (same system)..
However, when running the template installer on the portal, we get some errors such as:
"Element 'SAPConfigLib.ABT.Unclassified.maintainJcoDestination':Error during executing Java Reflection: Failed to delete JCO client connection 'WD_ALV_METADATA_DEST'"...
When checking in the BI report 'rspor_cust01' I get the following:
"Status för Steg 1 - skapa RFC-destination i J2EE-Engine
   Status 1 - Skapa RFC-destination i J2EE-Engine         Okay
   Status 2 - Skapa RFC-destination för portal            Okay
   Status 3 - Underhåll portal-server-inställningar för p Okay
   Status 4 - Underhåll single sign-on i BI               Okay
   Status 5 - Exportera BI-certifikat till BI             ABT_certificate.crt is not existing.
   Status 6 - Importera BI-certifikat till portal         Existence of BW certificate in Portal cannot be checked automatically.
   Status 7 - Skapa BI-system i portal                    Existence of BW System in Portal cannot be checked automatically.
   Status 8 - Konfigurera användaradministration i portal Configuration of User Management in Portal cannot be checked automatically.
   Status 9 - Exportera portalcertifikat till portal      No check with Portal SID
   Status 11 - skapa repository-hanterare för BI i portal Setup of Repository Manager for BW in Portal cannot be checked automatically.
   Status 12 - Underhåll användarallokering i portal       System failure during call of function module RSWR_RFC_SERVICE_TEST
   Status 13 - Importera SAP NetWeaver Plug-In till BI     Okay"
.. In other words, there seems to be problems with the certificates. Could anyone please provide me with input on how to resolve this issue. How do I handle the certificates when using only one system for both Java and ABAP?
thanks and regards,
F C

make sure you have done all the pre-requisites for running the template installer.
Note 917950 provides some attachments which will be really helpful.
Also try to update ABAP and JAVA to the latest SP levels.

Connect EP7 Portal to 2nd BW7 system

Hi All,
I have EP7 and BW7 . Both SP11 and configured as BI7 system.
I want to "disconnect" the BW7 system and connect other BW7 system to the portal.
Can I run template configurator?
I know that I'll need to change the RFC's destinations in the portal but do I need to delete/change some more settings before setting the connection between the EP and the new BW?
Thanks,
Omri

Solved it my own.
Deleted SAP_BW system in the Portal.
Deleted RFC destination in SM59.
Deleted RFC destination in VA.
Ran "Template Installer" and it worked!

Migration of WDJ Connecting MDM5.5 to MDM 7.1

Hello Experts,
Currenlty we are migrating WDJ and a EJB created for webservice connecting to MDM from 7.0 to 7.3. Out MDM was 5.5 the new MDM is 7.1.
I could migrate WDJ code successfully and deployed as well. We have installed MDM_JAVA_API and also imported as SC in NWDI track.
WDJ application is to perform test connection of the given MDM server details. But we are facing a issue called "Error while trying to invoke the method com.sap.mdm.session.NetWeaverMdmDestinationProperties.getServerName() of an object loaded from local variable 'destination'"
Since this is a migrated code we have not used any MDM destination in the code. But just for testing i created a MDM destination and its test is success.
Also i creating portal system with MDM server details and when we test the system connection test it throws the same error ""Error while trying to invoke the method com.sap.mdm.session.NetWeaverMdmDestinationProperties.getServerName() of an object loaded from local variable 'destination'".
Our portal vesion is NW7.3 with SP7.
Regards,
Karthi Velayuthan

Please look at, Hope this is helpful for you...
http://scn.sap.com/thread/1627412
Regards
Vijay

JCOClientConnection for logical System

Hello Experts,
I get this error when i launch my HR application, can anyone inform wht i have to to correct this error. Currently the portal run on SP7.0 sp15.
JCOClientConnection for logical System: HRSC_MODELDATA_DEST - Model: class com.infineon.hr.hrsc.formdatamodel.masterdata.MasterDataModel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
Thank you
BR
Ramesh

Hi,
The error HRSC_MODELDATA_DEST saying that you haven't configured the JCo destination.
To configure a JCo destination, login to portal ---> content Administration ---> WebDynPro Content
Then click on "Maintain JCo Destinations" tab, there you can see all the available JCo destinations. Here you have to configure the required JCo destination.
Note: If a JCo destination is not configured you can see a Red Color simbol and if it is configured you can see a Green color simbol......
For Creating JCo destinations:
http://help.sap.com/saphelp_nw70/helpdata/EN/6f/1bd5c6a85b11d6b28500508b5d5211/frameset.htm
Regards,
Srinivas.

Information broadcasting in BI7.0

Dear friends,
Could you pls help me with the procedure to configure the information broadcasting in BI7.0.
Pls help us with the below information
1.prerequiste for information broadcasting
2.How to configure bex broadcaster?(is there any step by step procedure doc?)
3.As per our understanding we can access bex broadcaster in web environment only(in browser).Is there any other way to access bex broadcaster to email the reports to the users?.
4.Is precalculation server is mandatory to execute and email the reports?
Thanks in advance for your time and help.
Regards
Soujanya

Overview: Integration into the Portal
Use
A number of settings need to be made in the BI system for the integration of SAP NetWeaver BI and SAP NetWeaver Portal. Some settings depend on one another, which is why we recommend that you follow the given sequence when you maintain settings in the BI system and in the portal. The report Maintain Settings for Integration into the Portal (report RSPOR_SETUP) supports BI system and portal administrators in setting up a secure connection in both directions, step by step. First the report asks you to make the required entries and then automatically determines additional specifications that you either have to enter manually, or that are entered automatically when the steps are performed.
Template Installer
As an alternative to report Maintain Settings for Integration into the Portal (report RSPOR_SETUP), you can use the template installer. The portal-based template installer enables the automatic configuration of the settings required in the portal and in the BI system. For more information, see Template-Based Configuration.
Requirements
Before you start to maintain settings, you enter general information. This information is used, in part, by various steps. If you determine this mandatory information at the start, you can perform the steps in a simple, logical sequence.
The report summarizes these specifications in the selection screen. The specifications are saved for the current session so that the transactions for the individual steps can be called separately from the SAP Reference IMG.
BI administrators require authorization for transactions SM59, SMGW, RZ10, STRUSTSSO2, SM30 (table RSPOR_T_PORTAL) and, in some circumstances, STMS.
Portal administrators need to have the portal roles super_admin_role and com.sap.ip.bi.business_explorer_showcase assigned to them. They also need to have access to the portal file system.
It is recommended that, from an organizational point of view, BI and portal administrators work together closely.
Connections Between SAP NetWeaver BI and SAP NetWeaver Portal
This report supports you in establishing connections between BI and the portal. The portal communicates with BI using the Web protocol http or https. Communication is establised based on the system object in the portal.
BI uses an RFC connection to communicate with the portal. The portal is the RFC server and BI is the RFC client. The report is used to create an RFC destination.
Single Sign-On Between SAP NetWeaver BI and SAP NetWeaver Portal
Single Sign-On saves you having to log on to BI and the portal separately. Single Sign-On uses SAP Logon Tickets. SAP Logon Tickets are created in the source system and contain the system ID, user, validity, and a digital signature. The digital signature is created by using the private key of the certificate. In the target system, the signature is verified by using certificates with public keys. The target system must trust SAP Logon Tickets from the source system; this requires the source system to be entered in the access control list (ACL).
For single sign-on to work correctly, the URL must be fully specified with the host name and domain. For this reason, you must also specify the portal URL prefix and domain in step 3. When you call BI iViews within the portal, the hostname from SAP NetWeaver AS determined in step 7 is used if this is a Web template from BEx Web Runtime 3.x For this reason, you must also specify the domain there. See the documentation for different domains under SAP Library -> SAP NetWeaver -> Security -> User Authentication and Single Sign-On -> Authentication on the Portal ->Single Sign-On -> Single Sign-On with SAPLogon Tickets -> SAP Logon Tickets for Multiple Domains.
Standard settings
The individual selection screen values are now described. For a more detailed description of these values, see the documentation on the individual steps.
Creating RFC Destinations in the J2EE Engine
Program ID: The program ID is the name of the registered server program (see step Creating RFC Destinations for the Portal).
Portal Directory: The Portal Directory is used to start the SAP J2EE Engine Administrator tool. The file ./admin/go.bat has to be in the directory. The SAP J2EE Engine Administrator can also be installed locally on the administrator's PC for remote access to the portal server.
BI User and BI Password: The BI user and the BI password are used by the J2EE Engine to request signatures from the RFC function modules in the BW system. Users can be compared using ALEREMOTE.
Creating RFC Destinations for the portal
User-Defined RFC Destination, Program ID as RFC Destination and RFC Destination : This report allows you to choose any name for the RFC destination. Otherwise the program ID is used (see above). If you choose a user-defined name, enter the name under RFC destination.
RFC Description: The RFC description is the text that is displayed in the BEx Web Application Designer and BEx Query Designer applications as the description of the connected portal.
Maintaining Portal Server Settings for the Portal
Default: To select a portal as the default portal, select the Default indicator. A warning will be produced if another portal is already marked as the default portal.
Portal URL Prefix: The Portal URL prefix is required for input help in the BEx Broadcaster. The report uses the portal URL prefix to list particular iViews for maintaining or testing the settings. The portal roles super_admin_role and com.sap.ip.bi.business_explorer_showcase are required for calling these iViews.
Prefix of RM for BI Metadata: The RM prefix for BI metadata is required in the step Setting up Repository Managers for BI in the Portal and also has to be maintained in the portal server settings. The prefix determines the path in Knowledge Management under which BI metadata is accessed by the Repository Manager.
Exporting the BI Certificate into SAP BI
Export Path and Export File Name: The BI certificate is saved under the specified path and file name and can then be imported into the portal.
Creating BI Systems in the Portal
Path in Portal Content and Name in Portal Content: The BI system in the portal is created under the specified path and name in the Portal Content Studio.
Template for Defining BI Systems in the Portal: As a template, you can choose either System with Load Balancing orSystem with Application Server when creating a BI system in the portal. The necessary information is determined and displayed depending on the template you select.
BI Properties: The following properties are specific to a BI system. If the identifier BI Directory Provider is activated, the BI system is displayed in open dialog when selecting queries or InfoProviders. The properties BI Documents for InfoProviders, Master Data, and Metadata contain the path to the respective CM Repository Manager for storing BI documents in Knowledge Management. These properties are used when the documents are migrated to Knowledge Management.
The property BI Master System means that the BI system is the central persistent store in the portal. The BI master system is used to read and execute Web templates. The running BI Web Runtime requires exactly one BI master system within a portal.
System Alias: Every system in the portal requires a system alias. You can enter any value. SAP recommends that you use the logical system name as the alias.
Creating System Alias SAP_BW: For the portal role Business Explorer com.sap.ip.bi.business_explorer_showcase, a BI system is required in the portal with the system alias SAP_BW. Note that there can only be one system with the alias SAP_BW.
Configuring User Management in the Portal
Logon Ticket Client: The logon ticket client can be any value between 000 and 999. The client is necessary if several portals with identical portal SIDs are connected. This is not normally the case and the default value can usually be transferred. You have to enter the client when you import the portal certificate into the BI system.
Exporting the Portal Certificate into the Portal
Portal SID: The portal SID is required so that naming conventions are observed. It has to be entered when you import to the BI system.
Import Path and Import File Name: The portal certificate should be saved under the specified path and file name and can then be imported into the BI system.
Maintaining User Mapping in the Portal
User-Mapping User and User-Mapping Password: The user-mapping user and password are used to check user assignment. This information is not absolutely necessary but does ensure that all settings have been made for a secure connection from the BI system to the portal.
Activities
1. Determine the mandatory information described above.
2. Execute the activity (= report Maintaining Settings for Integration into SAP Enterprise Portal ).
3. Enter the mandatory information on the selection screen.
4. Choose Execute.
5. Choose Previous Step or Next Step to switch between the individual steps.
6. To execute the step, choose Execute Step. The system either starts the necessary application so that you can enter information manually, or executes the step automatically. For each step the report supports the start-up of the appropriate application for executing the step manually.
Sequence of Steps
SAP recommends that you perform the necessary steps in the following order:
7. Create RFC Destination in J2EE Engine
8. Create RFC Destination for the Portal
9. Maintain Portal Server Settings for the Portal
10. Maintain Single Sign-On in the BI System
11. Export BW Certificate to the BI System
12. Import BW Certificate to the Portal
13. Create BW System in the Portal
14. Configure User Management in the Portal
15. Export Portal Certificate to the Portal
16. Import Portal Certificate to the BI System
17. Set Up Repository Manager for BW in the Portal
18. Maintain User Mapping in the Portal
19. Import SAP Basis Plug-In to the BI System
The documentation for the individual steps describes the manual process. The report Maintaining Settings for Integration into the SAP Enterprise Portal (report RSPOR_SETUP) executes some of these steps automatically..

Java Problem with Web Application

Hi Experts
I have a new poblem of connexion with my tools ( Web A
In fact when I execute my template, I have this error of communication:
ERROR JAVA : INCOMING CALL IS NOT AUTORIZED
I do a lot of thing like :
Create RFC Destination in J2EE Engine.
Create RFC Destination for the Portal.
Maintain Portal Server Settings for the Portal
Maintain Single Sign-On in the BI System
Export BI Certificate to the BI System.
Import BW Certificate to the Portal.
Create BI System in the Portal.
Configure User Management in the Portal
Export Portal Certificate to the Portal
Importing the Portal Certificate to the J2EE Engine
Import Portal Certificate to BI System
Set up Repository Manager for BI Documents and BI Metadata
Maintain User Assignment in the Portal.
Import SAP Basis Plug-In to BI System.
Thanks

Let's take this one step at a time.
1. You have successfully configured ABAP/Java communication using template installer? See note 917590.
2. Did you assign the portal user appropriate portal roles?
3. Can you start a web query from 7.0 query designer?

How to Create Certificate at the ECC 6.0 ( Trusting System ) in STRUSTSSO2

Hi Experts,
We are in the process of setting up Log On Ticket Based SSO Back End Connectivity from Portal to ECC 6.0 .
But, in STRUSSO2 when I try to Export the Certificate it has text file cert. And this cert is not
being accepted by Portal side i.e. at keystore Page while I try to import this Cert there , it say that
invalid Cert . Beside this, .der and .pse ..which one we need to use ?
So, I need to create first the Cert at the ECC side so that I can export and then import at the Portal.
How do I create Cert in STRUSSO2 at the ECC Side ?
Also, do I need to create the RFC JCo destination at the Portal side ? Or Just the User Mapping at the Portal side is enough .
Any / ALL Help is most welcome and would sure, be rewarded with appropriate point in addition to the
sincere appreciation of your time and help in the matter.
Thanks,
Regards,
- Ishan

Hello. You need to export sertificate in "binary" mode, from MENU --> Certificate --> export. Read for example http://help.sap.com/saphelp_nw70/helpdata/EN/fa/741a403233dd5fe10000000a155106/frameset.htm
I'ts about BW but the same sense.
P.S. you say "SSO Back End Connectivity from Portal to ECC 6.0" ,you need to create iViews in portal and see the ECC pages? For this you need to export Certificate from "Portal" and import in ECC ,and add in ACL in required client. Export from portal : System Configuration --> system administration --> keystore administration --> export verify.der
Read :
http://help.sap.com/saphelp_nw70/helpdata/EN/0a/a354426fdeb430e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/78/f1a8490e7011d6999500508b6b8a93/frameset.htm
Regards.
Edited by: Sergo Beradze on Jul 13, 2008 2:41 PM

Rapid Publish Content - SAP LSO - Soap Error

Hi All,
Iam trying to Publish Course Content using Training Administrator role. i have browsed for the source file and when i click on the folder it is throwing the below error.
SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")
I have clicked on show folder of original files and it is showing the location.
I have checked the authorizations and they are fine.This is working in Cloud system and in Dev it is not.
Please let me know if anyone faced the same issue.
Thanks,
Anil

Hi Please ensure the following nodes are set. you could also ask basis team to perform it:
SPRO of ECC backend system:
CMCFG CMMR
/documents/ECC_400Rep
CMCFG RFCDE
rfc destination created in portal Visual admin for ECC backend system.
REPEX MRURL
http://<portal.domain.com:50000>/irj/go/km/docs/documents/ECC_400Rep
CPCFG RSURL
http://<portal.domain.com:50000>/irj/go/km/docs/documents/ECC_400Rep
/ECC_400Rep is the folder created in KM contents of portal for LSO master repository
you must have above nodes set.
thanks,
Hiral

JCo creation

Hi experts..
I want to create a JCo destination in my portal serever but when i open the webdynpro content adminstrator the JCo creation, Maintain JCo, check SLD, start SLD are in disabled mode..
so how can i enable those things..?

Hi,
Check the following links.
SAP JCo Functions,Architecture,Applications,Installation,Client & Server Programming :
http://help.sap.com/saphelp_nw70/helpdata/en/6f/1bd5c6a85b11d6b28500508b5d5211/frameset.htm
Creating Jco destination:
http://help.sap.com/saphelp_nw70/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/frameset.htm
Maintaining Jco destination:
http://help.sap.com/saphelp_nw70/helpdata/en/94/3c1b40fcdd8f5ce10000000a155106/frameset.htm
The SAP JCo Repository :
http://help.sap.com/saphelp_nw70/helpdata/en/01/43e13d82fcfb34e10000000a114084/frameset.htm
Dynamic Jco creation Blogs:
/people/anilkumar.vippagunta2/blog/2007/02/06/dynamic-jco-creation
/people/gregor.wolf3/blog/2004/09/23/from-function-module-to-jco-application--part-1-of-3
Jco Pools :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a

RSBOLAP 017 Java Communication Error

Hi,
When iam opening query in Report Designer following error occurs :RSBOLAP 017 Java Communication error : RFC DEstination NOT_CONFIGURED does not exist.guide me for the same to resolve this one.i want basis support for to resolve the same.
Thanku

Hello,
I have tried to use BEX Web Application Designer and I have recieved this error.
I think that I need to configurate the SAP Netweaver portal with the previous mentioned steps.
   1. Create RFC Destination in J2EE Engine
   2. Create RFC Destination for the Portal
   3. Maintain Portal Server Settings for the Portal
   4. Maintain Single Sign-On in the BI System
   5. Export BW Certificate to the BI System
   6. Import BW Certificate to the Portal
   7. Create BW System in the Portal
   8. Configure User Management in the Portal
   9. Export Portal Certificate to the Portal
   10. Import Portal Certificate to the BI System
   11. Set Up Repository Manager for BW in the Portal
   12. Maintain User Mapping in the Portal
   13. Import SAP Basis Plug-In to the BI System
Do you know any guide that can helps me to configurate the SAP Netweaver portal?
Your answer will be gratefully received.
I am looking forward to hearing from you.
Best regards,

Destinations of a portal

Similar Messages

Maybe you are looking for