Language configuration Portal/ backend system

hi all
I have a Iview that launch some backend system R/3 with SAP GUI
if i open the R/3 with some language the language of the portal changes too
this is a problem i don't like that portal language changes
have you got any ideas
regards

Hi Ruben,
Try changing the property "Forced Request Language" for that iview. Let me know whether it works out.
Regards,
Siva
P.S: Award points if you find this useful.

Similar Messages

Web Dispatcher - Portal & Backend systems load balancing

Good Day,
I am currently in the process of setting up a web dispatcher for the Backend systems via the Portal.
I have already installed a web dispatcher to handle the Portal load balancing and this works perfect.
The SAP system landscape will be created using load balancing, currently it is set to Dedicated.
Question:
Do i change the ITS and WAS settings to point to the web dispatcher or leave them currently pointing to the backend systems?
ITS = hostname :8000
WAS = hostname : 8000
Many thanks,
Morgan Moodley

Hi Morgan,
You point them at the web dispatcher.
Paul

EP6 Backend System Configuration

Dear All,
we have develoed a custom iViews in EP5 .. and we have used the HTMLB,JSPDynPage and JCO for Connecting SAP and calling for ABAP RFC enabled function modules and BAPIS.
in EP5 we have used System.xml and JCO Destination.xml configration for connecting back end system..
and we have configured the system alias name in propert file(default.properties) and passed this to the connection class for establishing a connection SAP
now we want to move all our iViews to EP6 Netweaver Component and i heared that there are no System.xml and JCODestination.xml in EP6 Netweaver can any one suggest me that how to configure these backend system to run successfully my all iviews
Thanks and Regards
Prasad.Yedlapalli

Hi Prasad,
Well There are no mauanl edits of the Systems.XMl and the JcoDestinations.xml files , but there are visual tools to available for you to configure these systems in the same way. http://help.sap.com
cheers

NetWeaver Backend System Configuration

Dear All,
we have develoed a custom iViews in EP5 .. and we have used the HTMLB,JSPDynPage and JCO for Connecting SAP and calling for ABAP RFC enabled function modules and BAPIS.
in EP5 we have used System.xml and JCO Destination.xml configration for connecting back end system..
and we have configured the system alias name in propert file(default.properties) and passed this to the connection class for establishing a connection SAP
now we want to move all our iViews to EP6 Netweaver Component and i heared that there are no System.xml and JCODestination.xml in EP6 Netweaver can any one suggest me that how to configure these backend system to run successfully my all iviews
Thanks and Regards
Prasad.Yedlapalli

Hi Prasad,
I think you answered your question your self in one of your other postings. You have to define a system object.
Regards,
Jochen

Connecting EP7.0 to iSeries backend system using the connector framework

Hello All,
We are trying to setup a backend connection in EP7.0 to an AS/400 Legacy database using the JDBC Connector framework.
We use the driver and url syntax from OSS note 773401 "Configuring Portal JDBC System connection properties"
Driver:
com.sap.portals.jdbc.db2.DB2Driver
URL: jdbc:sap:db2://<server>:<port>;DatabaseName=<database_name>
When performing a connection check using the Support Platform, we can see on the legacy system that the connection is being established but for some reason the Portal doesn't get a confirmation and runs in to an endless loop...
Does anyone have a experience with such a connection?
Can we use the standard db2 driver class as mentioned in note 773401 or do we need to create/deploy our own?
Thanks in advance
Ron

Hello All,
We are trying to setup a backend connection in EP7.0 to an AS/400 Legacy database using the JDBC Connector framework.
We use the driver and url syntax from OSS note 773401 "Configuring Portal JDBC System connection properties"
Driver:
com.sap.portals.jdbc.db2.DB2Driver
URL: jdbc:sap:db2://<server>:<port>;DatabaseName=<database_name>
When performing a connection check using the Support Platform, we can see on the legacy system that the connection is being established but for some reason the Portal doesn't get a confirmation and runs in to an endless loop...
Does anyone have a experience with such a connection?
Can we use the standard db2 driver class as mentioned in note 773401 or do we need to create/deploy our own?
Thanks in advance
Ron

Backend system

Hi experts.
I am implementing SRM 5.0 in a Extendeed Classic Scenario my backend is Ecc 5.0, I have a problem with shopping cart creation, my system not permit creation of incomplete shopping cart, I opened a message in SAP SERVICE and Sap told me that my configuration for backend system is wrong, I tried several types of configuration but nothing works correctly.
Please someone could say me if is it wrong ?
SPRO - Supplier Relationship Management - SRM Server - Technical Basic Settings - Define Backend Systems
Logical System   Description     RFC Destination   Sys type RFC Local FI valid
DEVCLNT500     R/3            DEVCLNT500          R/3_4.70       X                   0
SRDCLNT500    SRM            SRDCLNT500          LOCAL                        X         0
Thanks
Nilson

Hi
<b>Local flag should not be enabled for R/3 system configuration.</b>
Instead of 'X' it should be blank.
Logical System Description RFC Destination Sys type RFC Local FI valid
DEVCLNT500 R/3 DEVCLNT500 R/3_4.70 'Space' 0
Hope this will help.
Regards
- Atul

Not getting backend systems

Hi I'm new to VC and I'm trying to configure the backend systems to be used. I'm using a user that has been assinged the VCRole and has been properly mapped to the backend system (a R3 type system). However I don't get any system in my list of backend systems.
I have to use the administrator user, because it is the only one that sees the list of systems properly.
Do I have to configure anything else? Any idea?
Thanks in advance.

Eduardo Cabezas López wrote:
> Hi I'm new to VC and I'm trying to configure the backend systems to be used. I'm using a user that has been assinged the VCRole and has been properly mapped to the backend system (a R3 type system). However I don't get any system in my list of backend systems.
>
> I have to use the administrator user, because it is the only one that sees the list of systems properly.
>
> Do I have to configure anything else? Any idea?
>
> Thanks in advance.
Hi,
the user which u r using must have content administartor role
regards
srinivas

Steps to configure R/3 system to Portal implementation

Hi
Please provide steps to configure R/3 system to Portal implementation
when i m opening standard iview in ESS in portal i m getting following runtime error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData' in the SLD. No such JCO destination is defined in the SLD.
Please help
Thanks

Hello Bhupinder Singh,
To use ESS/MSS services in Portal follow the following Steps
Maintaining jCo Connections
Use
jCo connections are used in iViews to connect directly to a backend. They are delivered with the portal content and must be activated (configured to access a specific system).
jCo connections have two parts: one with <jCo name>, and the other with suffix <jCo Name>_MetaData. The first one transfers user-specific data within the scenario; the other transfers only the needed metadata. For the jCo with name <jCo name>, SAP Logon Ticket is recommended as an authentication method. For the metadata connection, a user ID and password is needed. A system user created before is sufficient.
Procedure
Within this guide we generically describe the step-by-step procedure for an example connection set. Perform all steps for the following jCos:
u2022     SAP_R3_Financials / SAP_R3_Financials_Metadata
u2022     SAP_R3_HumanResources / SAP_R3_HumanResources_MetaData
u2022     SAP_R3_SelfServiceGenerics / SAP_R3_SelfServiceGenerics_MetaData
u2022     SAP_R3_Travel / SAP_R3_Travel_MetaData
u2022     SAP_R3_SelfServiceGenerics_MetaDataFIN
1.     Open the Web Dynpro Tool Applications overview page of your SAP NetWeaver Application Server Java: (http://<host>.<domain>:<port>/webdynpro/welcome)
2.     Select the Content Administrator link (or use a direct link, such as http://<host>.<domain>:<port>/webdynpro/dispatcher/sap.com/tcwdtools/Explorer) and logon with j2ee administrator rights
3.     Choose the Maintain JCo Destinations button.
4.     The available jCos are displayed with a red light, indicating that they are not yet maintained.
5.     In the JCo Destination Details iView, choose the Create button for the jCo you want to create.
6.     In Guided Procedure Section 1: General Data, make the following entries:
Field name     User action and values     Note
Name     <jCo_Name> or <jCo_name>_Metadata     Do not change the client number (for example, 100)
Maximal Pool Size     <keep default value>
Maximum connections     <keep default value>
Connection Timeout (msec.)     <keep default value>
Maximum Waiting Time (msec.)     <keep default value>
7.     Choose Next.
8.     In J2EE Cluster, make the following entries:
Field name     User action and values     Note
Use Local J2EE engine <SID> on <host>     Selected     Keep default values
9.     Choose Next.
10.     In Connection Type u2013 Data Type, make the following entries:
Field name     User action and values     Note
Data Type     Dictionary Meta Data     Dictionary Meta Data selected for <jCo_name>_MetaData; Application Data selected for <jCo_name> maintenance
Destination Type     Load-balanced Connection (recommended)     For Dictionary Meta Data Connection, the value cannot be changed
11.     Choose Next.
12.     In Msg. Server Connection, make the following entries:
Field name     User action and values     Note
Message Server     <select message server for your SAP ERP HR system>     The values are taken from the technical system list of the SLD
Logon Group     <select logon group for your SAP ERP HR system>     The values are taken from the technical system list of the SLD
13.     Choose Next.
14.     In Security u2013 User Authentication, make the following entries:
Field name     User action and values     Note
Used Method     <if using <jCo_name>, select Ticket>
<if using <jCo_name>_Metadata, value cannot be changed>
Name     <enter connection user name>     For example, rfcsysuser
Password/Confirm Password     <enter a password>
Language     English
SNC Mode     Off     For more information on SNC Mode, see the SAP NetWeaver 7.0 Help.
15.     Choose Next.
16.     In the Summary step, verify your settings, then choose Finish. The system displays a positive status message.
17.     In the JCo Destination Details iView, choose the Test link. The system displays a positive status message.
If the test fails, try to ping the ABAP system using the URL link. Check your settings, especially SLD, and certificate upload.
Let me know weather your problem solved or not.
Please reward points if helpful
Please close the thread if problem solved
Thankyou,
Regards
Vijai

Error while trying to open an added backend system in portal

Hi All,
I need one help.
I have added our Backend SAP SRM system in the Enterprise portal and it worked good.
But now if I try to open the added SRM system in the below path
System Administration à System Configuration à System Landscape -> portal contents -> system backends -> MY SRM(added system)
I am facing the error page cannot be displayed error as below
The page cannot be displayed
Explanation: There is a problem with the page you are trying to reach and it cannot be displayed.
Try the following:
u2022     Refresh page: Search for the page again by clicking the Refresh button. The timeout may have occurred due to Internet congestion.
u2022     Check spelling: Check that you typed the Web page address correctly. The address may have been mistyped.
u2022     Access from a link: If there is a link to the page you are looking for, try accessing the page from that link.
Technical Information (for support personnel)
u2022     Error Code: 500 Internal Server Error. The request was rejected by the HTTP filter. Contact the server administrator. (12217)
Please help me to solve it, Thanks a advance.
Thanks,
Senthil

Hi,
Are you using any webdispatcher or some proxy? Is there any URL filter configured in between?
If yes then I think you have to allow these pages.
Regards,
Vamshi.

Could not connect to backend system through portal via Web Dispatcher

Web dispatcher redirecting problem
Dear Experts,
I have implemented a scenario which comprised of customizing that is developed in Portal EP7. What customizing does is getting report from backend system (ERP 6.0)
According to the needs for reaching the portal from internet I configured the SAP Web Dispatcher in the environment as you may see its contents below.
The problem is when I run the customizing in portal system then it requires connecting to backend system (ECC 6.0) to get the data (report). But from this point on web browser comes to a blank page, could not view the data that is from backend system via portal. Because in the time when it tries to retrieve data in backend system, on the left bottom of the explorer the indicator shows internet address that system uses connecting to the backend system as local network address of the backend system which is not known in internet therefore I get blank page.
The question is how to configure the web dispatcher in a way that both portal and backend systems could be reachable from internet?
Contents of profile file of Web Dispatcher as;
SAPSYSTEMNAME = WDP
SAPGLOBALHOST = portald
SAPSYSTEM = 02
INSTANCE_NAME = W02
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_CT_RUN)
Accesssability of Message Server
rdisp/mshost = portald
ms/http_port = 8101
Configuration for medium scenario
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 500
icm/min_threads = 10
icm/max_threads = 50
mpi/total_size_MB = 80
SAP Web Dispatcher Ports
#icm/server_port_0 = PROT=HTTP,PORT=81$$
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=60000
icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/index.html
icm/HTTP/redirect_0 = PORT=50000
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 500
wdisp/HTTPS/max_pooled_con = 500
Configuration for medium scenario
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 500
icm/min_threads = 10
icm/max_threads = 50
mpi/total_size_MB = 80
Regards,
Ali Taner

Hi,
To resovle this you must have registered FQDN for your backend system as well. When you call the report from Portal using internet it should call that FQDN of your backend system then DNS will resolve this & you will get the expected page. This way only you can resolve this issue.
Thanks,
Sachin Sable

Reaching backend systems through portal is a problem via dispatcher--

Hi Experts,
I am having problem when I try to reach backend systems through the portal from internet. I have configured WebDispacher according to information taken from help.sap.com, but unfortunately the result is not satisfactory. Reaching Portal EP7.0 from internet is successful, but when I changed to iviews that are referring to backend systems then browser comes to a blank page with error. If any of you having an idea on the subject that will much be appreciated.
Regards,
Ali Taner

Hi Hari,
I am sorry that it has been a bit sharp response from my side, but I am confused with what you mentioned. Is the Alias that you mentioned reside on R3 side or Portal side that I should look for, and secondly the Alias should address to local URL or External URL? In my understanding if Alias referring to local URL address than it gets error when somebody tries to reach from internet because local address is not known on the internet. I really appreciate your kind help
Kind Regards,
Ali Taner

Publishing through Portal - "Connection to backend system failed"

We are having a problem publishing documents through our SAP Portalu2019s service u201CPublish Course Contentu201D under Course Administration.
When we go to publish, we get a status u201CConnection to backend system failedu201D with the message u201CNo message availableu201D.
We are running:
Portal on NW 7.0 EhP1, Support Package 04.
ABAP on ERP 6.0, EhP4, Support Package 18.
Both the Portal and ABAP systems are running on Linux RHEL5, with an ORACLE 1.0.2.4 database.
Portal and ABAP are on different servers.
Not certain if this is significant but under System Configuration, if I open my ABAP back-end systemu2019s configuration and perform connection tests, the overall Connector test fails.
We also have a sandbox system on which we did the configuration first. We have compared all of the values for the configuration we have done to ensure they are configured the same. On the sandbox, the connection test is successful and we can publish content without error.
I have been trying to review the various trace files, increase trace levels, etc. both on the ABAP back-end system and on the Portal. I have been able to find anything that appears significant but this is probably due to my not knowing what to look for.
Which specific trace files should be reviewed for the root cause of the issue? What are the exact steps the Publish process takes to accomplish its work? If we know the exact steps it takes (how it communicates, what modules it uses, what accounts) we might be able to determine the root cause.
We are using a SAML login to our portal for authentication and have removed the Basic password login module from the Authentication Stack u201Cticketu201D. We have established trusted RFCu2019s between the ABAP and Java instances for the Publishing function. When authentication is configured, we try to use the highest form available in the configuration. We use Assertion tickets if available, it not, we use Logon Tickets, if not available, we would then select X.509 certificates and if that were not available, would select Username and password.
Any ideas as to what we should be looking at would be greatly appreciated. I have searched both SDN and SAPNet for similar situations and not yet found something that corrects the problems.
Thank-you in advance,
Deb Nugent.

Arun,
Thank-you for your suggestions. The ABAP back-end system is up and I have verified the connection properties. I have had others verify as well. All appears correct.
The default trace files, through NWA, show the messages:
BackenConfig not correct. processId = 78775D8D1053B855;
com.sap.hcm.ls.shared.config.backend.BackendConfigException: Destination Exception
Can not get Destination com.sap.security.core.server.destinations.api.DestinationException: The properties for destination ZZ_LSOCP_JP3 of type RFC could not be located.
I have checked all of the trace files both on the ABAP and Java sides and cannot determine the root cause. I have repeatedly tried things suggested by other threads in SDN and others (consultants) have tried as well. We cannot determine the root cause of the connection errors and now, cannot get the Publishing to work properly.
The only system where the connector test works is our sandbox. Our dev and test systems all fail the connector test. We configured them all using the same documentation.
Is there some way to increase trace levels to try and get more details? And what objects would need to have traces increased?
Deb.

How to find the backend system in portals

Hi Gurus,
How to determine the number of backend systems referred in portals.
Higher points will be rewarded for useful inputs.
Thanks in Advance,
Dharani

Hi Dharani,
if u have the system Administration role,
u navigate thro System administration -> System configuration -> System landscape Overview.
this iview will list all the system created for connection.
If u want further clarification , feel free to raise q in forum

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

Change backend system of portal

Hi,
We want our EP7 portal to point to a different backend system. We want no references to the old backend system.
I know the following steps:
1) create new system
2) Change the Webdynrpo Jco connections
Please let me know the other steps that needs to be taken care off while changing the backend system?
Thanks,
Antar

No other steps needed. It is fine.
Once you delete the old system then you can test it by creating a SAP Transaction iview
during the creation it will give you a drop down of all system aliases in the portal.
Raghu

Language configuration Portal/ backend system

Similar Messages

Maybe you are looking for