Portal runtime default language

Hello,
I am trying to set the default portal runtime to French.
In the System Administration - System Configuration - Service Configuration - Portal Runtime - Central Configuration, I set these properties as followed:
request.defaultcountry=ca
request.defaultlanguage=fr
After a restart of the portal, the portal is still displayed in English. Note that I don't have any language selected in my portal user profile. And in Internet Explorer, I also have no language selected (under Internet Options).
Am I missing anything ?
Regards,
The-Hung Nguyen

Hi The-Hung,
check prtDefault.properties as described [here|How to set Portal to default language English, independend from SU01; and see if following settings are made:
request.defaultlanguage=en
request.defaultcountry=us
If yes, you need to remove "en" and "us" so that the localization works as you want.
Hope this helps,
Robert
PS: You can also check this link for more information about the locale lookup order:
http://help.sap.com/saphelp_nw70/helpdata/EN/42/938297a5061d69e10000000a1553f6/frameset.htm

Similar Messages

ISE 1.2 sponsor portal - disabling default languages

Hi,
We are implementing Cisco ISE 1.2 and have a question on the sponsor portal languages.
The client company's official language is English and so we would like to disable all other languages from the sponsor portal. If we don't do it, the users might select their native language (on the sponsor settings and/or the guest notification language) meaning that we have to customize and maintain all 15 language templates.
It has alread happened during the tests: a sponsor created a guest account and choose a notification language other than English - the SMS was not sent because the "Destination" on the "SMS text message notification" default value is "[email protected]".
Thanks in advance.
Regards,
Telmo Oliveira

Hi all,
This reply to myself is done for documentation proposes, it can help someone with the same challenge.
Today I was at an event at Cisco where ISE 1.3 beta was presented. This version will have already the option to choose between browser locale or static language template. Talking to the Cisco eng. responsible for the presentation, he told me that 1.2 had no way to do it.
Cisco ISE 1.3 is now planned to be release end of 2014.
Regards,
Telmo Oliveira

HOW to define the default language in the portal

Normally the portal take the language of the internet explorer for user.
I want to define a default language for all portal users in our portal, so that every user get the same default language.
Can anyone tell me how to do this?
We are on EP6 SP2.
Thanks Sybille

Hi Olivier,
thank you for the response.
I added
request.mandatorylanguage=de
request.mandatorycountry=de
to
request.defaultlanguage=de
request.defaultcountry=de
Now, I get the default language german, but when I want to changed the portal language over personalize to English, the result is nevertheless the german language.
Can you help me again? Where can I get a documentation about this?
I want a default language: German. Also when the Internet Explorer has a different language. But when the user select manual one of the permitted languages (English and German) over the personalize button, the language should change to the selected language. Is it possible?
Bye Sybille

Change the default language of an existing SAP Portal

Hi,
Our SAP Portal works with two languages, Spanish and English. The default language is Spanish, but since the company is becoming more international, we want to set the default language to English. Need to know if you can change the default language of an existing SAP Portal.
Specifically, it is the case of the standard UWL notifications, which are sent by mail in Spanish. For tasks defined in the application, the message is personalized and sent in two languages at once. However, when the task is not defined, notifications arrive in the default language, which is now Spanish. Could anyone tell me if I change it?
Thanks for the help!

Dear Marciano
I hope you are well and many thanks for using the SAP Discussion Forums .
In relation to the scenario that you have described regarding the language setting for EP and the UWL.
The language that the portal is displayed in depends on the following heirarchy, with the languages at the top of the list taking precedenceover those at the bottom:
1.Component (iview) language (defined in the portalapp.xml)
2.Portal Mandatory language (defined in the prtDefault.properties)
3.User language (defined in the user#s profile).
4.Request language (defined by the browser).
5.Portal Default language (defined in the prtDefault.properties)
6.System Default language (default locale defined by the OS).
So for example, if you have your portal user language (as in point 3)set to Czech, but the language of the iView that is the logon page (as in point 1) set to English, that logon page will be displayed in English.
Regarding the navigation path for the prtDefault.properties kindly refer to the SAP Documentation outlined below which provides a detailed summary and walkthrough regarding the language settings.
Setting Mandatory Language For Portal
http://wiki.scn.sap.com/wiki/display/EP/Setting+Mandatory+Language+For+Portal
- SAP Note: 1013521 - Configuration of supported languages within the portal
- SAP Note: 1661391 - Portal 7.3 is not displayed in the configured language
- SAP NetWeaver Portal 7.3: SAP Documentation and Guides: http://scn.sap.com/docs/DOC-23349
- SAP Note: 1696439 - Changing the Default or Mandatory Locale for a 730 Enterprise Portal
Using Extended Notifications and the UWL
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/ad/d64842d59fb430e10000000a155106/frameset.htmhttp://http://help.sap.com/saphelp_nw70ehp2/helpdata/en/ad/d64842d59fb430e10000000a155106/frameset.htm
Kindly update me as per your findings.
Kind Regards & All The Best
Troy Cronin - Enterprise Portal Support Engineer

How to set default language for Portal?

Hi All,
We use EP6.
Default language is not defined and therefore is being set by the browser's language.
Where do I set default language for all users?
(I don't want that the users will be able to change it by themselves by browser/EU role).
I tried to set the "request.mandatorylanguage" and
"request.mandatorycountry" in prtDefault.properties but it didn't help.
Thanks,
Omri

Hi Omri,
are those to parameters
request.defaultlanguage=...
request.defaultcountry=...
set in the prtDefault.properties, and the J2EE Server restarted after the change?
Check out this thread and the link given there for more info: HOW to define the default language in the portal
Hope this helps,
Robert

Portal Runtime Error while accessing BW reports through portal

Hi,
We are facing portal runtime error(An exception occurred while processing your request. Please send the exception id to your portal administrator) while accessing BI reports through portal frequently.
We are unable to trace the error in the 'default trace' log file and although refreshing the cache solves this issue, it is difficult to explain this to every user individually.
After many such errors, We found one log entry, which we are now not yet sure if it is relevant. The error states:
1.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-ext-sid=<ID[url_ENCODE]>&Language=<Request.Language>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<Authentication>&<Report>&<BusinessParameters>'; the problem occured at position 230. Cannot process expression <LAF.AllVersions>
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
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:540)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Content pass of Application Integrator failed.
Component Name:       'com.sap.portal.appintegrator.sap.BWReport',
Context Name (iView): <iview name location>
Top Layer:            'BWReport/TopLayer',
Producer ID (FPN):    'null',
System Alias:         'Sap_bw',
2.
The cluster server element 111111 is not added in the EP cluster context,
   because prtbridge on 111111 is stopped or not yet started (maybe the server is starting or shuting down).
Please suggest us if the above logs are related to the issue or not
Kindly provide us any inputs or solutions.

Hi All,
We are also having similiar type of error in our portal.
com.sap.engine.services.prtbridge##com.sap.engine.services.prtbridge
#######SAPEngine_System_Thread[impl:5]_13##0#0#Error#1#/System/Server#Plain###
The cluster server element 125898350 is not added in the EP cluster context,
   because prtbridge on 125898350 is stopped or not yet started
(maybe the server is starting or shuting down).
We have implemented the FPN using RRA.
This error comes only for few users when they navigate in Portal. After clearing the cache, it works for all. Kindly help us to resolve this issue.
Regards,
Venkatesh

Need to download com.sap.portal.runtime.logon.par

hello friends
we need to chang the look and feel of the portal display pages and for that purpose we need com.sap.portal.runtime.logon.par file
can you all help us as to where we can find this par file so that we can download this file.
we have still not installed the portal platform,we'll be doing that in the following week.
Thnaking you,
Anurag.

Hi Anurag,
This post will explain the steps involved for each element.
No.      Portal Login page related questions
1.      What is the associated par file for portal login Page ?
2.      How to import the PAR file into Netweaver Developer Studio?
3.      What are the different pages and their associated files in logon.par?
4.      How to change text seen in the logon page ?
5.      What is authschemes.xml file? Do we need to change this file also ?
6.      How to remove standard links like support, Register ...?
7.      How to change or add new images ?
8.      How to change only the branding image displayed in the logon screen of the Portal ?
1. What is the associated par file for portal login Page?
Answer : The par file related to login page of Netweaver Portal is com.sap.portal.runtime.logon.par. This is the standard
logon component containing the code and resources used by the logon screens is shipped in a portal archive (PAR) file named com.sap.portal.runtime.logon.par.
2. How to import the PAR file into Netweaver Developer Studio?
Answer :   - Select File>Import .
- Choose the option PAR file. Select Next and a popup window appears.
- Select File>Import .
- Choose the option PAR file. Select Next and a popup window appears.
- In the window you have 3 text fields:
The location of the par file,
Project name (same as new par file name, preferably) and
location for project to be saved
3. What are the different pages and their associated files in logon.par?
Answer :
Logon page : umLogonPage.jsp
Problem page : umLogonProblemPage.jsp
Help (PW reset) page : umHelpPage.jsp
Reset Password : umResetPasswordPage.jsp
Change Password Page: changePasswordPage.jsp
Certificate Logon : umLogonCertPage.jsp
4. How to change text seen in the logon page ?
The text seen on the logon page is not in the JSP page, but in properties files which are called by tags like the
Welcome text : <%=logonLocale.get("xtit_WELCOME")%>
In order to change "Welcome" to "Welcome to MyTravel" you have to :
           - Unzip the file umelogonbase.jar which you can find under dist\PORTAL-INF\lib
           - Find the file "logonLabels_" which contains your language;
                                       e.g. logonLabels_de.properties for german language, *_en for English etc.,
The default is in the file logonLabels.properties .
- Find the key which is used in the tag and change the text after the equal sign.
- Save the changed file and create a updated JAR file using a zip program. The file needs to be named exactly umelogonbase.jar
- Put the JAR file back to location - dist\PORTAL-INF\lib
You are done on this now.
5. What is authschemes.xml file ? Do we need to change this file also ?
Changing the Authschemes.xml file is required only if you want to change com.sap.portal.runtime.logon.par.bak file and point it to different par file. This is more for anonymous logon with named anonymous users and using anonymous as the authentication scheme. The anonymous users are not issued a SAP logon ticket.
6. How to remove standard links like support, Register ...?
The standard links are controlled with the UM settings
       - ume.logon.logon_help
- ume.logon.selfreg
You could also just comment out the lines if you want to hide.
7. How to change or add new images ?
To exchange the two images, which are by default on the logon page, do the following steps:
                      a. Copy the image(s) you want to use in your project in the the folder dist/layout
                      b. Find the < img src=""   > you want to work on in the umBotArea.txt
Change the src attribute in the img tag to src="<%=webpath + "layout/myPic.gif" %>". The webpath is already defined in the file logon_proxy.txt and ready to use. In the Netweaver portal 6.0 SP9 and higher you have 2 images on the right side.
8. How to change only the branding image displayed in the logon screen of the Portal ?
If you want to change only the branding image displayed in the logon screen, you can configure this using the user management property ume.logon.branding_image
Hope this helps the community in the launch of this ver 1.0, future versions could contain more changes and updations covering all other aspects of Netweaver Portal

Portal runtime error while selecting page layout in WPC editor

Hello,
in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
The logfile shows the following :
#1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
[EXCEPTION]
#1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
usr
sap
EPD
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.netweaver.bc.util
lib
bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
(source unavailable)
1 error
I have the same by clicking on "check assignments"
Any help ?
Thanks

Hello Jego.
We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
Best regards,
Aliaksandr Zhukau

Portal Runtime Error while creating new system in portal content

Hi
Can anyone solve my problem, i am geting error while creating new system in p ortal content
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file

Hi,
Check this link for creating system object
http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
Regards
Arun

How to change the default language of form9i?

How to change the default language of form9i? For example, change the language from Spanish to English.
Regards!
Gerald

Hi,
set the NLS_LANG parameter and make sure the language supplement classes got installed when installing the deesigntime or server. If you need to change the language for runtime, set the value in the default.env file - assuming its a web based appication
Frank

Custom column in a list view web part for a multilingual site does not take on custom language labels. Stays in default language.

Hello all,
I have what so far appears to be a fairly unique problem. We are running a multilingual SharePoint 2010 environment with English as the default language and French as the secondary. We have setup the sites in a variance relationship, but the
issue I am discussing happens outside of a variant as well.
We have created a library outside the variant (but within the collection) that the two sites must share. A list view web part was created via Designer to add to each site to provide a quick view into the list. If we are in the libary and switch
to French, then update the column label it will remember the setting (because of the resource file) and maintain it as the language is flipped back and forth. Where it doesn't work is as a web part in a variant or where the language is different.
If the language is different, the out of the box columns work find, but the custom columns (all site columns not library\list columns) remain as the english label. It doesn't matter if within a variant or outside with the browser language changed.
It always reverts back to English. It's like it isn't using the same resource file that was used in the list itself.
I created a custom view and modified it with xslt as per
http://sharepoint.stackexchange.com/questions/50004/how-to-change-column-title-for-a-view-but-not-modify-the-list but this only worked within the list and did not occur in the list view either.
I can't be the first that has come across it, either I am not performing my searches properly, no one has ever documented a fix for this or this is something we just can't fix with OOTB tools. That's the other thing, the solution has to be accomplised
OOTB or with minor client side changes. I can't fire up Visual Studio because they are piloting Office 365 and have put a "No custom code" mandate on for migration.
Thank you all in advance.

Ok, I have come up with a solution. I edited the XSLT for the web part on the page. I did the following:
1.   Create the variants in the Site Ccollection
2.   Create the library outside of the variants.
3.   Add all the columns you require for the library. It is very important all the columns are there before you move on.
4.   Create a French and English view.
5.   Create the list view web part via designer.
6.   Add the list view web part to each site selecting the appropriate view to use.
7.      Edit the page in SharePoint Designer 2010.
8.      Place cursor in the column you wish to modify.
9.      Click Design in the List View Tools on the ribbon.
10.     Then click Customize XSLT and select Customize Item. Select this option otherwise you will generate a **LOT** of unnecessary XSL code.
11.     You are looking for a piece that resembles the following:
        <xsl:with-param name="fieldtitle">
          <xsl:value-of select="@DisplayName"/>
        </xsl:with-param>
12.      Modify it by typing in the actual column name you want. You should end up with something like this:
        <xsl:with-param name="fieldtitle">
          New Column Name.
        </xsl:with-param>
13.      Now, for this page only, the column will be renamed.
There are some caveats:
1.   Doesn’t appear to work in a publishing portal. I think this has to do with how SP stores the pages in this case. In a publishing portal you can only modify the page layout which won’t work as we need to modify the content.
2.   If you add another column, you will need to repeat the XSLT modification
Anyways, I hope this helps out any others with the same issue or need as I had.

Portal runtime error while creating rooms

Hi,
I installed collaboration and content management on my portal instance
and started basic configuration. Now while creating rooms , i get the
portal runtime error. I have enclosed the screen shot of the error.
I have enclosed the steps that can be followed to reproduce the error.
Portal Runtime Error
An exception occurred while processing a request for :
iView :
pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.netweaver.coll.colcontent/com.sap.netweaver.coll.RoomCreation/com.sap.netweaver.coll.RoomCreationWizard
Component Name : com.sap.netweaver.coll.appl.ui.room.RoomCreationWizard
The exception was logged. Inform your system administrator..
Exception id: 10:23_07/02/07_0037_818308650
See the details for the exception ID in the log file

Hi Detlev,
Thanks a lot. I have enclosed the information from default trace.
<< item 0 : >>#1.5#00306E0AA058008600000060000044AC000428E704E99CFE#1170872586724#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#SAPOSS#13800##srv006_W81_818308650#SAPOSS#11f658b0b6d811db93c800306e0aa058#Thread[PRT-Async 3,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception ID:10:23_07/02/07_0037_818308650
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.netweaver.coll.colcontent/com.sap.netweaver.coll.RoomCreation/com.sap.netweaver.coll.RoomCreationWizard
Component class : com.sap.ip.collaboration.roomui.api.rcwizard.RcWizardComponent
User : SAPOSS
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sapportals.wdf.WdfError
at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:678)
at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.portal.htmlb.PrtContext.render(PrtContext.java:413)
at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
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)
... 7 more
Manoj

GETTING ERROR WHILE DEPLOYING A COM.SAP.PORTAL.RUNTIME.LOGON.PAR FILE

Hi Experts,
I need to change the text in logon screen i.e,
2006-2007 SAP AG ALL RIGHTS RESERVED
for this i changed the copyright and deployed the par file
but it is giving error like this
operation failed:please make sure the server is running or check the log(sap-plugin.log)
what should i do plz suggest me na.....
i searched the file sap-plugin.log in program files -> sap>IDE>eclipse-->plugin but i couldnt find the
plz specify the directory na...
waiting for u r response.....
Regards,
Shilpa

HI SHILPA....really sorry for the late response.
here is the error log which i m getting...(its not 500 error)
[13.08.08 / 16:49] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Startup in progress
[13.08.08 / 16:49] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Factory initialized !
[13.08.08 / 16:50] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Server returned HTTP response code: 502 for URL: http://hostname:50000/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=Administrator&j_password=EPDJ2EEADM&j_authscheme=default&uidPasswordLogon=Log%20on
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:808)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
     at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:179)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:84)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
     at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
     at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
     at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)

Portal Runtime Error when opening Webflow workitem in UWL

Hi,
I have recently configured the UWL to pick up workitems from SAP workflow on a background system. The workitems are appearing OK in the Task folder. However, when I try to open a workitem by double-clicking on it, I get the following error:
Portal Runtime Error
An Exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 05:33_30/09/10_0010_24209150
Refer to the log file for details about this exception.
NB. This only seems to happen for items that would be shown via the SAP GUI (E.g. a Confirming a task completion or user decision). The workitem runs OK if it is for a task that is visualised as a Web Dynpro app and specified in transaction SWFVISU.
I have not configured Delta Refresh options in the Workflow Administrator so do not know if this is a possible reason (I assumed that this would not cause a problem and would simply mean that refreshes only occur once every 60 seconds). Any help would be greatly appreciated. I am fairly new to Portal & UWL I would also be grateful if someone could tell where I can find the relevant log files referenced in the original error.
Regards
Simon

Hey Simon,
Welcome to UWL :). Portal Runtime Errors in UWL don't always signify that there is a UWL issue. This could be a permissions problem, etc. I'm not sure what version of the portal that you are using. But here is a little trick for you when checking logs...you can enter in the following: irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.admin.logviewer.default
and check the log file with the id that was given in the error.
Exception ID: 05:33_30/09/10_0010_24209150 is your exception id. Search for the log files in the default trace and see what the exact error message is. If you can post this here it would be great.
The log files can be found in the following location:
/usr/sap/<SID>/JC<InstanceNumber>/j2ee/cluster/
server<number>/log
or by entering the URL that I mentioned above.
Please let me know in the next reply what the portal version is:
You can get this information by doing the following:
a. log on to the portal
b. backspace out the irj/portal section of the URL
c. click enter.
d. You are now at the J2EE administration page.
e. Next, click on the system information link
f. Please click on the all components link
g. Please attach this information to the message.
I am interested mostly in the UWLJWF component but if you can attach the full software component info to this post that would be great...
Please note, that note number 1133821 is an important note that is needed in the UWL. Did you maintain your RFC destination accordingly?
Here is some additional information to help you too since you are new to UWL:
[UWL Wiki|https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq]
[UWL Forums|SAP Enterprise Portal: Application Integration;
[Business Task Management|http://help.sap.com/saphelp_nw70/helpdata/en/9e/ccf62fff3e4a45a634e592dabb45d5/frameset.htm]
[Using Universal Worklist|http://help.sap.com/saphelp_nw04s/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm]
[JavaDocs UWL API|http://help.sap.com/javadocs/NW04S/current/uw/overview-summary.html]
I hope that you find this information useful!
Best Regards,
Beth Maben
EP - Senior Support Consultant
AGS Primary Support, Business Suite & Technology
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq ***

Portal Runtime Error: Unable to parse template

Hi!
I integrated SAP BW system with SAP Portal. All the connection tests (Sap Web AS connection, ITS connection, Connection Test for connectors) run successfully.
I also installed a BI add on u201CBI Administratoru201D on Portal and performed all the steps on SAP BI system.
When I try to access one of the functions of BI Administrator I get Portal Runtime Exception on all the windows in Portal (bellow, in the middle, etc.).
BI System Selection
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 12:26_20/01/09_0013_21754250
Refer to the log file for details about this exception.
I have looked into log file for Portal and detected the following error text:
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException:
Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>
/sap/bw/BEx?sap-client=<System.client>&sap-language=<Request.Language>&accessibility=<User.Accessibility
[SAP_BOOL]>&style_sheet=<LAF.StylesheetUrl[url_ENCODE]>&<TrayInformation[IF_true PROCESS_RECURSIVE]>&<Authentication>&<Report>&<BusinessParameters>&\#39;; the problem occured at position 82. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
Question:
How can I correct this error?
Any helpful information will be very appreciated!
Axel

Hi Alex,
It seems that the iview (of the type Application intergrator) cannot read or interperet the "client" parameter from your system object.
I can also see that the systemobject-alias that is reffered to is "SAP_LocalSystem".
Find the System Object called SAP_BW and see if all settings to connect to the backend are correct.
In addition in the iview try to set the system-alias from SAP_LocalSystem to SAP_BW and retry.
Good Luck.
Benjamin

Portal runtime default language

Similar Messages

Maybe you are looking for