Ampersand in portal tools entitlements causing exception

There appears to be a bug in the portal tools that ship with 4.0. If you have
a portal page with an ampersand in the name, EBCC creates the XML that is loaded
to the database correctly (with the &). But when you try to create an entitlement
for this page, it will put an entry in the ENTITLEMENTS_RULESET portal page record
that has the ampersand standing by itself. Thereafter, anytime you try to go
to the entitlements page, you get an XML parse exception.
Add to that the fact that this data is stored in a CLOB (making it difficult to
edit), it is a tough situation to deal with.
Please let me know if there is a patch/fix for this.
Thanks.

Paul,
I searched the bugs database and there is a known issue (CR082251) if you
used an ampersand character in the Portal Description. I could not find anything
related to entitlements but I believe this is a bug.
Unfortunately, I don't have a good suggestion for this problem. The best thing
to do I believe (if you don't mind) is to open a case with BEA support.
It is the preferred channel for managing this kind of issue.
Thanks for your feedback,
Michel.
"Paul Merrigan" <[email protected]> wrote in message news:3d66b315$[email protected]..
>
There appears to be a bug in the portal tools that ship with 4.0. If you have
a portal page with an ampersand in the name, EBCC creates the XML that is loaded
to the database correctly (with the &). But when you try to create an entitlement
for this page, it will put an entry in the ENTITLEMENTS_RULESET portal page record
that has the ampersand standing by itself. Thereafter, anytime you try to go
to the entitlements page, you get an XML parse exception.
Add to that the fact that this data is stored in a CLOB (making it difficult to
edit), it is a tough situation to deal with.
Please let me know if there is a patch/fix for this.
Thanks.

Similar Messages

Portal Runtime error - An exception occured : when accessing the SRM Portal

Dear Consultants,
We are logging onto the SRM Portal using url link. SAP Netweaver 7.0
But when we are trying to access any tabs in the Navigation frame of the portal it is throwing an error.
Error - Portal Runtime error
An exception has occured while processing your request.
Can you please let me know how can I find the correct reason for the error.
regards
Arindam

Hi Arindam,
Pls check Default Trace log in the NWA tool, path would be NWA --> Monitoring --> Logs and Traces --> Select Default Trace.
Find the log messages with the Exception ID found on your Portal Runtime error. These logs would specify the exact cause of error.
Thanks,
Swapna Priya.

Portal Runtime Error : An exception occurred while processing a request

Hello friends,
After upgradation of my portal to the following patch level, SAP J2EE 6.20:
Portal Version : EP 6 SP 2 patch 29 hotfix 0
Content Mgmt and Collaboration version : 6 SP2 patch 5
i faced many performance related issues. Portal seems to be very slow. After logging in, most of the time I get 2 errors:
Either
1> Iview remains blank.
Or
2> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
But when I refresh that particular iview, it works fine.
I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."Aug 18, 2005 6:07:42 PM # PRT-Async 2 Fatal Exception ID:06:07_18/08/05_0669
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
Component class : com.sapportals.portal.prt.pom.RootComponentNode
User : tempuser
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
 at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Help needed.(as i am helpless now.)
Regards,
Nilz

Anthony,
I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
I created like this
 project-> rightclick-> export-> par ->selecting project-> givint protal password-> and finish.
The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
but the par file is created in the NW studio Navigation bar.
Let me know any help regarding this
thanks
venkat

Com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP

Hi All,
I am configuring SSO between EP7 and SRM 7.0
1) I have created a SRM system in EP system connections works fine with logon ticket.
2) I have uploaded roles from SRM system
but content from these roles throws following exception
Although i have SAP_SRM as system name exception shows System: &#39;SAP_LocalSystem&#39;,
what is the root cause for this exception.
Full Message Text
12:07_02/04/09_0188_7992050
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.ITS.protocol>://<System.Access.ITS.hostname>/sap<ESID>/bc/gui/sap/its/<IAC[SAP_ITS_NAMESPACE]>?sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&DisconnectOnClose=0&DesignBaseUrl=<LAF.BaseUrl[url_ENCODE]>&~design=<LAF.Theme[url_ENCODE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 121. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
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.sapapplication.bwc.AbstractBWCComponent.doContent(AbstractBWCComponent.java:68)
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:523)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Regards,
Murali

Hi Murali,
First of all activate the integrated ITS on backend system , follow the below link to do so
www.arlati.ch/knowhow/archive/Integrated_ITS_WebGui.pdf
In EP where you have created SRM system , there you have to maintain the ITS defination and test the ITS defination.
Also Check the permission of the SRM system which you have created.
Thanks
Anil

Setting Portal Page Entitlements Painfully Slow

Does anyone have any tips on speeding up the Portal Admin Tool entitlement setup processing? We're trying to setup a new portal with about 180 different entitlements and assigning entitlements to the portal objects (pages and portlets) is taking forever. The response time for clicking the Entitlement tab for a single portal page is about 20 seconds. Add to that the fact that it seems to re-retrieve the entitlement information after each action (select a page, add the entitlement, set the accesses for the entitlement) and you're talking about a significant amount of time to setup each entitlement. Now multiply that over 180 entitlements that need to be assigned.
The bottom line question is, are there tunings we can perform?
Some additional information:
- We are on WebLogic 8.1 SP4
- Our database is Oracle 9i
Any help would be greatly appreciated.

Trying do it in dev - bear the pain and then use the propogation tool to move them to other environments. At least you just have to do it once. Pre-Sp4 -- the prop tool hardly worked.. so u would feel the pain in each environment.
BEA is making progress :)
BTW - 20 secs seems a long time. It takes me just 4-5 seconds. Are u sure that you bea server is tuned properly?
Kunal Mittal

"Portal tools area keeps apearing" EP 6.0 SP 10

We have made the Portal tool area invisible in our Portal by making it invisible in "content provided by SAP -> end user content -> Standard Portal users -> Default framework Page" by "unticking" the visible attribute for iView "tool area".
However once per week it keeps reappearing although no manual changes have been made to the Default framework page.
Any ideas to what that can be caused by - e.g. by some standard Portal restore job?!
Message was edited by: Kurt Frambo

Hi Kurt Frambo
I would recommend that changes related to portal desktops etc should always be done by making copies to the original SAP object, renaming them & storing them in your folders and them modifying them so that after patches/upgrades they do not keep changing and you dont have rework a lot and restoring the original.
I hope this would solve your problem..
Let me know if you have any other queries. Also tell me if you were using the SAP Framework page or have u created a copy of the original and applied that in your theme/rule..?
Regards
Gaurav Gandhi

How to add a custom iview to the portal tool area

Hello:
We want to add some simple text like date,day and some
more things to the portal tool area, where a KM search
box, and collobaration link exists now.
I tried to look up for the tool area iview par file, but
only found, *.ept file only which doesn't contain any
code.
I hope atleast some of the clients might have tried this.
If you will you please shed some light on how to achieve
this task.
Thank you very much in advance for the help,
Prasad Nutalapati

Hi Prasad,
try to do this:
1) download the par file of the standard toolbar. You can find it under:
\usr\sap\P602\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\deployment\pcd
its name is: com.sap.portal.navigation.toolarea.par.bak
2)import it into eclipse with another name, i.e. com.customer.portal.navigation.toolarea
3) modify as you need the jsp contained in it in order to satisfy your requirements.
4) deploy the par into the portal and create a new iview based on it.
5) put this iview into the framework page you want to use, hiding/deleting standard toolbar
these steps are OK if you want simply modify the layout of the toolbar, you cannot modify the logic behind it.
If you need to do that, for example add some buttons which perform some custom actions, you have to develop a new component from scratch using the portal development paradigms.
I hope this could help you
Cheers
Roberto

Error in removing Portal Tool Area from Theme

Hi
In my Portal theme i had a Portal Tool Area with Search options.
My requirment is to removie it from the theme as we don't need it
Go to Content Administration
Portal Content--> Content Provided by SAP->End User Content-> Standar Portal Users
You can see Default frame work page.Open the same and untick the Visible Check box beside tool area iView in the frame work page.
Save the changes and refresh the page..
I made the setting,The tool area is not visible in priview...
But when i logged in as test user it is still there
How can i proceed
Thanks

My suggestion is go through the below help liks for better understanding
Framework pages
http://help.sap.com/saphelp_nw04s/helpdata/en/a6/1c67161be54bc19cfa86e187819fbe/frameset.htm
Portal desktops
http://help.sap.com/saphelp_nw04s/helpdata/en/b2/cf65869fb64552be09e46516dd8062/frameset.htm
Portal desktop and display rules
http://help.sap.com/saphelp_nw04s/helpdata/en/4b/29cf122f414721964269e1b675d62c/frameset.htm
you need to check in the display rules whether you have multiple framework pages or not.
Raghu

Digital graph causes exception in 8.5

Wanted to port some of my older LV panels to 8.5. I noticed that LabView would generate the following message when attempting to load one of my panels:
"Unhandled exception at 0x007513e0 in LabVIEW.exe: 0xC0000005: Access violation reading location 0x00000000"
The following is a snippit of code from the debugger:
007513B0 aaa
007513B1 adc esi,dword ptr [ebp]
007513B4 bound edx,qword ptr [ebx]
007513B6 jne 007513B8
007513B8 jnp 007513CD
007513BA jne 007513BC
007513BC xchg eax,esp
007513BD adc esi,dword ptr [ebp]
007513C0 xor ecx,ecx
007513C2 xor eax,eax
007513C4 test edx,edx
007513C6 je 00751461
007513CC mov eax,dword ptr [edx+4]
007513CF test eax,eax
007513D1 push esi
007513D2 mov esi,dword ptr [edx]
007513D4 jle 0075145B
007513DA mov edx,dword ptr [edx+8]
007513DD push edi
007513DE mov edi,eax
007513E0 mov al,byte ptr [esi] <<<<************************************************ Dies here
007513E2 cmp al,2
007513E4 jne 007513EB
007513E6 or ecx,4
007513E9 jmp 00751412
007513EB cmp al,5
Panels like this one are mid sized, containing 10 - 20 sub VIs. I stripped the panel down to try and find what exactly was causing LV 8.5 to crash. It turns out to be the digital graph. I have attached a very simple panel that just contains the digital graph with nothing wired to it. If you try to run this in 8.5 I am guessing it will cause the problem. I tried it on a few PCs and get the same results.
Attachments:
main.vi ‏20 KB

Looking at my disks, version 6 appears to have been the first release to support digital graphs. I remember using as soon as it was available.
I tried several tests to see if I could further narrow down the problem for NI.
I am able to load the raw version 6.0 examples directly into 8.5.
1) I saved version 6.0 example "Simple Digital Waveform Graph" (SDWG) into a seperate VI. It loads in both 6.1 and 8.5 with no exception.
2) Loaded main.vi example and copied it into the SDWG using 6.1. Causes exception in 8.5
3) Connect the two graphs together in example so digital data is shown on both graphs, then saved the values as defaults. This version loads in 8.5 with no exception.
4) Start with main.vi, clear all the waveform data and save as defaults. Causes exception in 8.5
So, problem appears to have nothing to do with the cursors but does appear to be something with the data that had been stored into this graph when the defaults were saved. It is really strange that clearing the data does not solve the problem. Maybe this is a bigger problem than I originally thought.
Message Edited by lecroy on 10-09-2008 01:07 PM

LORD - ERP Error ERP_LORD_GET_HEAD caused exception EXC_LORD_NOT_LOADED

Hello,
We have an CRM 7.0 system linked to EHP4 ECC.
We have implemented LEAN Order Interface.
Now while saving an ERP Sales Order from CRM Screen, it gives an errror saying "ERP Interfaced stopped / failed unexpectedly".
We have implemented enhancement spot ENH_SPOT_LORD for the same in ECC.
No Detailed error description is appearing, no application log is being written, neither in ECC nor in CRM.
Required Switches are also made activated in SWF5. Mapping Structures are also mapped in LORD_MAPPING and LORD_MAPPING_RO.
error message that I get is : ERP_LORD_GET_HEAD caused exception EXC_LORD_NOT_LOADED
Can some1 please help the BADI's and the mandatory methods that needs to be over written in Enhancement.
Or can some1 please tell where I am going wrong?
Thanks & Regards,
Narendra.

Hi Narendra,
Did you get a solution to this please?
Thks,
William

Finally cause Exception be forgotten

In trying out that finally cause previous return value be forgotten, as described on page 206 of "The Java Programming Language, 3rd edition", I wrote the following code, and tested it with jdk1.3.1. To my supprise, not only the return value was forgotten, the exception was appeared forgotten as well:
class PException extends Exception {
class Final {
    void f1(int i) {
     int result;
     System.out.println("f1("+i+")");
     try {
         result = f2(i);
         System.out.println("result = " + result);
     } catch(Exception e) {
         System.out.println("caught an Exception: " + e);
     try {
         result = f3(i);
         System.out.println("result = " + result);
     } catch(Exception e) {
         System.out.println("caught an Exception: " + e);
    int f2(int i) throws PException {
     try {
         if (i == 1) {
          System.out.println("generate exception");
          throw new PException();
         return 1;
     } finally {
         return 2;
    int f3(int i) throws PException {
     if (i == 1) {
         System.out.println("generate exception");
         throw new PException();
     return 1;
    public static void main(String[] args) {
     Final f = new Final();
     f.f1(1);
     f.f1(2);
     f.f1(1);
}Here is the result:
f1(1)
generate exception
result = 2
generate exception
caught an Exception: PException
f1(2)
result = 2
result = 1
f1(1)
generate exception
result = 2
generate exception
caught an Exception: PException

The concern here is that when the
try {
finally {
}pattern is used, without the catch block, purelly for flow control purpose, a return statement in the finally block could be problematic. If a finally block ends with a return statement, any exception that might be thrown in the try block would be ignored. The unhandled exception will not propergate, it simply lost in the midst. Because any code could throw unchecked exception, if the exception cannot afford to be lost, then one should be careful not to use return in the finally block. See the following test code:
class Finally {
    void test() {
     int result;
     System.out.println("test()");
     try {
         result = f1();
         System.out.println("result = " + result);
     } catch(Exception e) {
         System.out.println("Caught an Exception: " + e);
     try {
         result = f2();
         System.out.println("result = " + result);
     } catch(Exception e) {
         System.out.println("Caught an Exception: " + e);
     try {
         f3();
     } catch(Exception e) {
         System.out.println("Caught an Exception: " + e);
     try {
         f4();
     } catch(Exception e) {
         System.out.println("Caught an Exception: " + e);
    int f1() {
     System.out.println("f1()");
     int a = 0;
     int b = 0;
     try {
         a = 1/0; // this generate an unchecked exception
         b = 1;
     } finally {
         return b; // this return clobber the unchecked exception
    int f2() {
     System.out.println("f2()");
     int a = 0;
     int b = 0;
     a = 1/0; // this generate an unchecked exception
     b = 1;
     return b;
    void f3() {
     System.out.println("f3()");
     int a = 0;
     int b = 0;
     try {
         a = 1/0; // this generate an unchecked exception
         b = 1;
     } finally {
         return;   // this return clobber the unchecked exception
    void f4() {
     System.out.println("f4()");
     int a = 0;
     int b = 0;
     try {
         a = 1/0; // this generate an unchecked exception
         b = 1;
     } finally {
    public static void main(String[] args) {
     Finally f = new Finally();
     f.test();
/code]
Here are the results:test()
f1()
result = 0
f2()
Caught an Exception: java.lang.ArithmeticException: / by zero
f3()
f4()
Caught an Exception: java.lang.ArithmeticException: / by zero
We see that the devide by zero exception throw by f1() simply vanished, the unintended result 0, instead of the intended result 1, is returned. The test() method did not detect any abnormality in f1(), which is scary. To drive the point home, we try f3() and f4(), which has void return type. A simple return statement in f3() causes exception be lost. The stack frame seems intact, for otherwise, the test() method would exit abruptly before f2() even get a chance to be called.

RemovingDisabling Portal Tool Area

We currently want to increase the portal body size, and do not have TREX running, so we are wanting to remove\disable the Portal Tool Area (removing Search Field Box, Search, and Advance Search from Portal Outer Frame. Instead of blanking out values within Theme Editor for Portal Tool Area, can we just disable Portal Tool Area globally to increase the portal body size?
Regards,
James

Hi,
You can open the default framework page from Portal Content -> Content Provided by SAP -> End User Content -> Standard Portal Users -> Default Framework Page. Inside that, Uncheck the visiblity check box of tool bar iView. That should do.
Regards,
Harini S

Code causing exceptions at its own sweet time and place

import java.lang.*;
class newthread implements Runnable
     Thread t;
     int click=0;
     public volatile boolean running=true;
     newthread(int p)
          t=new Thread(this);
          t.setPriority(p);
     void start()
          t.start();
     public void run()
          while(running)
               click++;
     void start1()
          running=true;
     void stop()
          running=false;
class threadpriority2
     public static void main(String argv[])
          newthread ob1=new newthread(Thread.NORM_PRIORITY+2);
          newthread ob2=new newthread(Thread.NORM_PRIORITY-2);
          ob1.start();
          ob2.start();
          try
               Thread.sleep(5000);
          catch(Exception e)
               System.out.println("error detected:"+e);
          System.out.println("first one:"+ob1.click);
          System.out.println("first one:"+ob2.click);
          System.out.println("the priority of ob1 is:"+ob1.t.getPriority());
          System.out.println("the priority of ob2 is:"+ob2.t.getPriority());
          ob1.stop();
          ob2.stop();
          ob2.t.setPriority(Thread.NORM_PRIORITY+3);
          ob1.t.setPriority(Thread.NORM_PRIORITY-3);
          ob1.start1();
          ob2.start1();
          ob1.start();
          ob2.start();
          System.out.println("the priority of ob1 is:"+ob1.t.getPriority());
          System.out.println("the priority of ob2 is:"+ob2.t.getPriority());
          try
               Thread.sleep(5000);
          catch(Exception e)
               System.out.println("error detected:"+e);
          ob1.stop();
          ob2.stop();
          System.out.println("first one:"+ob1.click);
          System.out.println("first one:"+ob2.click);
errors during runtime:
Exception in thread "main" java.lang.IllegalThreadStateException
at java.lang.Thread.start(Unknown Source)
at newthread.start(threadpriority2.java:17)
at threadpriority2.main(threadpriority2.java:77)
when i run this code it causes exceptions at its own sweet locations when i run it separately.if once it displays some valid input it would then be followed by the exception
next time if i run it it will throw exception as soon as i run it at the very start without displaying even an iota of valid data like the previous case
is ti because the os is placing restrictions on the threads growth or something else.incase there is an error in my code it should atleast pop up the exceptions at one particular loaction in the output and not give different outputs

1) When you post code, please use and tags as described in Formatting tips on the message entry page. It makes it much easier to read.
wasnt aware of it.will keep it in mind i post nexttime.sorry for the inconvenience[\b]
3) You have multiple threads, right? The scheduling of which thread gets how much CPU time when is not subject to your control or prediction, so of course you'll see different timings in subsequent runnings of the same code.[b]actually the problem is not with multiple threads showing different times.whats happening is that exceptions are being thrown randomly at runtime.once when i ran it the exception was displayed at the very beginning of the output and the program snapped.next when i ran it first some output which was slated to be displayed got displayed and then the exceptions appeared in the output.now if the exceptions are thrown at the very beginning its obvious theres some problem at the background coz in the second case that never happened[\b]
i guess the formatting tips have taken effect[:D]

Portal Tools Installation

i have been trying to install Portal Tools in my 9iAS rel.2 Portal but i always get an Internal Server error when testing the provider. My jpdk is working fine. I just need to install this. Hope you can help me with this. thanks

Hello,
Which version of portalTools are you installing in your Oracle Portal ? (I guess you have a 9.0.2.x Portal)
Also, since you have an error, you should take a look to the application log file of the portaltools application you have deployed. (using Enterprise Manager or file system)
Regards
Tugdual Grall

Setting camera target and using the pan tool moves everything except target

Hi,
I have a JavaScript which sets the camera target using the code below.
var setTarget = function(strNodeName) {
    for (var intCounter = 0; intCounter !== scene.nodes.count; intCounter++) {
        var node = scene.nodes.getByIndex(intCounter);
        if (node.name.indexOf(strNodeName) === 0) {
            var camera = scene.cameras.getByIndex(0);
            camera.target = node;
This works great for the rotate and spin tool. But hen I use the pan tool, everything moves except the node that was set as target.
Why is this happening and how can I prevent this?

James, thank you very much for the VI, now i understand what you meant by initialising the shift registers. You're right about my text-based programming background, and seeing how you've implemented the case selection really helped. The removal of the mathscript modules does reduce lag quite a lot, too, and now everytihng works exactly as it should. I set the initial servo positions and rawx/rawy values, extended the error line the way you suggested, and added a division by two after the array summation, in order to get an average, rather than a near-double result.
I agree with you and 22v10 that slicing the image up into quadrants might have been a better idea to begin with. The 'center band' that is set in the current vi works quite well and i'll stick with it for now, since i won't have much more time to work on this project.
I avoided adding tilt for now because i thought it would only complicate things. Now that panning works, i've duplicated the method and adjusted it for tilt.
I'm also considering removing the Vision Assistant nodes, since for calibration purposes i need to go into it and create new templates from scratch every time, and this will only get more tedious as i start experimenting with more complex 'targets'. A more viable solution is presented here, where everything is set once the application is launched.
Please find attached an updated copy of the VI. It's a bit laggy, i'll continue working on it and updating.
James, thank you again for providing a working solution. I'd love to give you credit when the project's finished.
Attachments:
image tracking camera centering-update 2, working.vi ‏916 KB

Ampersand in portal tools entitlements causing exception

Similar Messages

Maybe you are looking for