8.1 equivalent of portlet:form event=bea.portal.framework.internal.refresh

I've got a portlet with an edit JSP that allows the user to set some portlet settings. The edit JSP uses a form defined with the tag <portlet:form event="bea.portal.framework.internal.refresh" >. This in essence allowed the edit JSP to submit the form to itself, so it could then process (store) the settings.
This tag is no longer supported in 8.1. I haven't been able to find what the equivalent is. Am I going to be able to do the same thing, or am I going to have to rewrite the Edit piece as a page flow?

I've already tried that and it's not working in my current portal.
The other things I've tried are <render:postBackUrl/> and <render:windowUrl> for the form action, and they weren't working, either. But since then I've discovered that in a new vanilla portal installation, the <render:postBackUrl/> action works fine (I assume the controller would, too, but I didn't try it).
It seems I now have a different problem to work through to figure out why <render:postBackUrl/> works in a new installation, but not in my current one. The same goes for the controller.

Similar Messages

Inter portlet Communication - Events and Parameters

Hi,
I just tried a sample inter portlet communication using events and parameters.
I used the below code to enable inter portlet communication between two struts portlet.
UrlUtils.constructLink etc
The above works fine. Instead of link, I would like to use a form button to fire the event.
Is there any way of using button to fire the event.
Another thing I noticed is that when the event is fired the page gets refreshed.
How to enable inter portlet communication without the portal page refreshing.
Many Thanks in advance!!!!!!!!
-Chid

Hi Natu,
To start: read the documentation: http://download.oracle.com/docs/cd/B32110_01/webcenter.1013/b31074/jpsdg_java_adv.htm#CHDHDCGI
Then, you need to make sure the portlets can operate independently. That means: the locations portlet should be able to run without the incidents portlet.
What you should try to achieve is create a locations jspx that uses a page parameter with the incident number as input. The page can then be populated based on that id.
The key thing here is: input portlet variables are available as page parameters.
Then, you need to add some functionality to the incidents portlet to submit the selected incident number to the outside world. You can do this using some backing bean code. Example:
    public void transmitEvent(ActionEvent actionEvent) {
        FacesContext facesContext = FacesContext.getCurrentInstance();
        ExternalContext externalContext = facesContext.getExternalContext();
        Object response = externalContext.getResponse();
        if (response instanceof javax.portlet.ActionResponse) {
            ActionResponse actionResponse = (ActionResponse)response;
            // setting the portlet OUT parameter
            String outResult = "my output";
            actionResponse.setRenderParameter("outParam", outResult);
       } else {
            // not in portlet environment
    }Hope this brings you further.
Jeroen van Veldhuizen

Form Events in Acrobat 9 Standard

I'm trying to programatically have my form fields highlighted when opened by a user in Reader. I've seen some other posts recommending setting the app.runtimehighlight event to true but I can't find the form events. Any help would be appreciated.

Acrobat 9 Standard does not have direct access to the document level scripts. So with a one page form you could add the code to the open page action. You will need to open the 'Page' or 'Thumbnail' navigation page, select the page, right mouse click and select the 'Page Properties" and add the script using the 'Actions' tab.

HCM Form events

Hi,
We are developing the HCM forms. Our requirement is populating the Country values in one dropdown list and based on the country we need to populate the city's in other dropdown list. The city values will come from the backed (BADI logic). The event is triggering and the city values also getting but the complete form getting refreshing when ever event is triggering, i don't want to refresh all the form, only related fields need to refresh.
The below events are added to my Country dropdown exit event
$record.CONTROL_PARAM.ISR_EVENT = "USER_EVENT_INITIALIZE"
app.eval("event.target.SAPSubmit();");
Please can any one help me on this.
Thanks
Nag

Hey Nag,
Are you using the ZCI format for the forms, because if you are, you are using the wrong dropdown list box. The list box you are using is for the ACF style of form.
I'd first suggest downloading the ISR ZCI library from the Service Marketplace
[Note 1104060 - Adobe LiveCycle Designer - ZCI template update|https://service.sap.com/sap/support/notes/1104060]
[Note 947675 - ISR/Adobe: Layout category ZCI (composite SAP note)|https://service.sap.com/sap/support/notes/947675]
[Note 947633 - Current ISR Control libraries|https://service.sap.com/sap/support/notes/947633]
[Note 973170 - New library for "SAP Interactive Forms by Adobe"|https://service.sap.com/sap/support/notes/973170]
The last one has the dropdown that has the correct code for use within the ZCI form template usage.
This is what the code is to look like, and can only be executed when the event language is Javascript:
xfa.record.CONTROL_PARAM.ISR_EVENT.value = "CHECK";
ContainerFoundation_JS.SendMessageToContainer(event.target, "submit", "", "", "", "");
You have to replace CHECK with the name of the operation in the backend that you want to call. Also, another thing that you have to do is Insert Web Dynpro Script when using ZCI form template. This can be done by selecting the Utilities option from the SAP GUI menu bar, not the form designer menu bar, and it should be right above the Versioning option. After selecting this, you will notice that you have an addition to your Hierarchy tab in the Form Designer that says
(variables)
|-----ContainerFoundation_JS
This contains the code needed to make reference to your operation in the DO_OPERATION method of your BAdI.
Hope this helps...
Cheers,
Kevin

How to tell apart ready:form-event and ready:layout-event

Hi,
I would like to call the same function in a script object from different events.
As I cannot make layout changes in the ready:layout event I would like to find out in the function: Which event called me?
event.name gives me the event name nicely for most events. (Although the returned strings are somewhat peculiar....)
But: The ready:layout-event as well as the ready:form-event both give me "Open".
Therefore I would like to know:
How can a function tell whether it was called from ready:layout or from ready:form?
I suppose there is a much simpler solution, than trying "event.name".
Ulrich

Hi Ulrich,
Check out event.activity in LC Designer help. This gives a closer description of the event fired, eg 'docReady' instead of 'open'.
Good luck,
Niall

Passing parameters from portlet reports to portlet forms

Hi,
I'm tring to pass parameters between a Report displayed as a portlet in a page ( page 1) and a form displayed in other page ( page 2).
The problem is i can't do this.
I only can pass parameters from a report ( running as normal or in a portlet displayed in a page) to a form running "normal" by using application links. Can i do this between a report that show's me every employees of scott.emp table. Then when i click on each employee, it open's me another page with the portlet form of the specified employee.
I'm not sure i made myself clear. Please send me some feedback.
Pedro

I have the same problem. Please let me know if this could be done.
In particular my form is a type of "Form on Table/View."
Thanks
Henry

Modal Form between the Form Events

I create a modal form which is like the message box but with a textbox in it. What i mean here is, the modal needs to hold the form event while it's adding an Sales Order record.
I have tried the Modal Form method as shown in SDK Sample 12.ModalForm. However, i found the Sales Order is added before i click any button in the Modal Form.
So, can anyone give me any advise how to work with it.......
Thanks a lot~~

Hi,
Solution I would try is to catch FormItemEvent, EventType = et_ITEM_PRESSED, ItemUID = "1".
With this you can catch the OK/Save button. If you use the BeforeAction you can even Cancel (bubbleEvent) adding the record if the user cancels your modal form.

Bea Portal: Installing 3rd Party Portlets / cms portlets

Hi there,
I hope this question is not too silly, but I am new to Bea Portal
Server. How do I properly install 3rd party portlets, e.g. the
cmsportlets available for download on the developer page ?
I extracted the zip files and then there is an Ant-Script where one's
supposed to change some parameters according to ones installation. I did
this and then I ran Ant, which actually copied the files to the portlets
directory. This is already strange to me: can the EBCC just create new
portlets or can it do something like "import" resources that someone
else has developed?
Well, so even after running ant, the portlets can be seen in EBCC, but I
an not add them to my page.
Any idea how to move on ?
Thanks
Hinrich

Hi,
Did you have a chance to look into WebLogic Portal 8.1 SP3? Check out the new Library Services features, which includes versioning and simple approval:
http://e-docs.bea.com/wlp/docs81/adminportal/help/CM_MAN_LifecycleOV.html
We also provide a few ootb portlets that allow users to interact with the CM system. Let us know if you have additional questions.
Best Regards,
--alex

Oracle Forms events coming to city near you in 2008....

Details on my blog.
http://groundside.com/blog/GrantRonald?title=some_events_you_might_be_interested_in&more=1&c=1&tb=1&pb=1
I've also added a new link to the Forms home page on OTN which points to the new Oracle Forms events page.
Any feedback please let me know
Thanks
Grant

Hi Grant,
Can I put a summary here which will help users not to navigate to many URLs.
Dates Country
===================
21st February 2008 Ireland
13th February 2008 Finland
12th February 2008 Norway
29th January 2008 Denmark
18th January 2008 Sweden
13th December 2007 Portugal
3rd July 2007 UK
19th June 2007 UK
30th May 2007 Faroe Islands
Rajesh ALex

Content Presenter Portlet (CPP) on weblogic portal 10.3 giving error

Hi,
We are using WLP 10gR3 & UCM 10gR3 in our environment.
We've done a new installation on portal following the checklist which is working fine on a working env.
On portal application CPP giving error
Content Presenter Portlet giving err-An appropriate display template for this item could'nt be found
WLP is able to connect to UCM & all required patches for CPP (patch APD4, patch AVW6, patch ZKHC) are also poperly applied.
On console, error logs show - Error - <May 5, 2011 1:02:49 PM IST> <Warning> <Events> <BEA-401903> <Duplicate EventListener com.bea.content.repo.internal.server.logic.search.ContentExporterListener not added to Handler com.bea.p13n.events.internal.EventHandler on Type {3}.>.
Not able to understand what is going wrong?
Same set of libraries are also applied in this env.

Hi,
Could someone pls explain which cache is used to cache portlet content and in which form the content is cached?

BEA portal and other frameworks

This is a very general question. Is it possible to have an
enterprise application written using BEA Portal 4.0 and having
parts of the application (aome portlets) written using a
different framework. In other words how is it difficult to
merge BEA Portal with applications written using different set
of frameworks.
Thank you

I don't know whether you're still at this address.
We own a package software company in the consumer lending space. Our application is a large pure J2EE application, running in BEA Webserver/Oracle, precisely and carefully engineered (it is probably the largest Java based lending application anywhere). The application has been built by a leading team of software engineers, from 2001 to 2004. The members of the design
and programming team has multiple advanced degrees, PHDs, includes academics and academic chairs with extensive experience, including in Mathematics, and
have been working with Java/J2EE since its original inception.
IB is looking for additional resource in the form of a company deeply experienced in Java design, architecture and implementation to assist to manage parts of the product, and to assist tocreate enhancements to the product on an ongoing basis.
Do you know such companies based in India with these sorts of extensive skills?
[email protected]

Problem with LDAP in BEA Portal

Problem with LDAP in BEA Portal
I have a list of 50 user which should be cerated in portal staging(devlopment) machine and should be transfered to
production machine using LDAP
Steps which i followed to create Users
1.Create User Profile with 2 parameters branch and Role
2.I have list user in the Xls file with Username,password ,branch and Role
3.Write a java File which will read the Xls File
4.The users are created in the staging machine for the portal
Steps which i followed in LDAP to tranfer the created User form Devlopment to Production
1.Export the created user from Devlopment (which was moved as .DAT in my local directory)
2.import the user from local direcory to production machine
The Users are imported in the production machine with username and password but the role and branch values are empty
We need a solution for importing the user with role and branch corresponding to each user.
Thanks in Adv
Suresh

In Portal 8.1, user name and password in stored in LDAP where as user profile values are stored in database. That is the reason you are not able to see the user profile values.
Check once again whether you can see these values through admin tool. In case,it is not(after confirmation again),you might have to use APIs to do this for you incase you dont want to manage through Admin Tool.
Thanks,
Prashanth Bhat.

How to show or hide portlets dynamically on a Portal Page

Dear All
1. I have a Portal Page with One Portlet in the top having like 5 Buttons. Each button click should display a separate portlet in the bottom on this same page.
2. I have Top Portlet. For bottom I have 5 Portlets P1, P2, P3, P4 and P5. On my .portal file, I dragged and dropped top portlet and all these 5 Portlets one below each other.
3. Now, I am trying to use BackingFile approach at PageLevel/Portlet level, to get the details of button clicked in top portlet (like name etc), and then show only one portlet at a time in the bottom section (using portlet backingcontext show/hide APIs). I do need to compare the bottom portlets defintion_label etc. which is fine for now.
Is this the right approach...?
Or do I have to use Portlet Custom Event approach. So top portlet will trigger event everytime button is clicked with some payload. And bottom 5 portlets listen to that event and show/hide accordingly. But in this approach, I have to attach backingfile to all the bottom portlets to listen to them.
All the portlets are Pageflow based Portlets. Any ideas or any other simpler approaches, are highly appreciated.
Thanks
Ravi Jegga

Hi Kevin
1. Thanks a lot for the pointers. I will go with Events. So for bottom Portlets, I will use the same BackingFile. But still it is going to be custom Event. Because only one portlet will be shown. So its like my payload will be portlet def label. In Backing File, I will compare this payload with actual dynamic value and if same, show or hide that portlet. Please let me know if this is correct approach.
2. Now each one of the Bottom Portlets is a complex pageflow portlet with many buttons of their own. So everytime a button is clicked or action is invoked, the Backing File gets called. And I had to somehow know that the same portlet has to be shown or the show/hide logic should not be called. Is there any way, where backing file gets called or just listen for Events triggered only from main top portlet.
Thanks for the other message, where looks like you already gave lots of pointers. I will go through them.
I will design and test this out and will keep you posted with my results.
Thanks a lot again
Ravi Jegga

Out of the box porlets for Content Management with BEA Portal

I am looking at BEA Portal for a simple Intranet site with some basic content management system capabilities. I would like to implement this without the use of a third party tool and wanted to know if there are any open source or out of the box BEA portlets/web-apps with basic CMS capabilities beyond what has been shown in the Portal tutorials around CMS. From doing the tutorials, I have learned how to manage content, and how to build a site from scratch to access the content using the <cm:> tags. However, without additional third party products such as Documentum or Interwoven, is there any free BEA/open source portlets to:
- Configure exposure of this content in a runtime framework? (ie content manager can expose new content from the repository by a configurable admin GUI, place where this content is on the page)
- Allow for a simple approval workflow where content that gets added to the repository by user A has to be approved by user B before automatically exposing?
Interested to know if custom portal type development is the only way to do these kind of simple functions, or third party product.

Hi,
Did you have a chance to look into WebLogic Portal 8.1 SP3? Check out the new Library Services features, which includes versioning and simple approval:
http://e-docs.bea.com/wlp/docs81/adminportal/help/CM_MAN_LifecycleOV.html
We also provide a few ootb portlets that allow users to interact with the CM system. Let us know if you have additional questions.
Best Regards,
--alex

Integrate with BEA Portal and Lotus Domino R5.0.12

Deal all:
I got a problem when I integrate with BEA Portal and Lotus Domino R5.0.12.
my environment is below:
- Domain Server :
Lotus Domino Server R5.0.12
BEA Personal Messaging API 4.3
(test successful on local host)
- Application Server:
BEA Weblogic 8.15
BEA Groupware portlets 2.5
I got connection successful message when I using "Domino Service Connection"
but I got "CZ: VERSION CONFLICT" error message when I add a new account by
Compoze_Groupware-Edit Account user interface.
Have anybody met the error message before... and know how to sovle the problem..
I appreciated any suggest or comment~~~
detail error message is below:
portlets.compoze.groupware.exception.ConnectionException: CZ: VERSION CONFLICT at portlets.compoze.groupware.controls.provider.SessionControlImpl.createSession(SessionControlImpl.jcs:142) 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.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:381) at $Proxy19.createSession(Unknown Source) at portlets.compoze.groupware.controls.provider.GroupwareProviderControlImpl.updateAccount(GroupwareProviderControlImpl.jcs:4825) 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.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:249) at com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:85) at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224) at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:109) at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:207) at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54) at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:168) at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:46) at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161) at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315) at $Proxy11.updateAccount(Unknown Source) at portlets.compoze.content.options.accounts.editAccount.editAccountController.saveChangesAccountAction(editAccountController.jpf:534) 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.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1512) at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1447) at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:778) at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211) at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:608) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:1504) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:674) at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527) at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1734) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1754) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:561) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:121) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:98) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:150) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:109) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:224) at com.bea.netuix.nf.ControlLifecycle$3.visit(ControlLifecycle.java:171) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:355) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:126) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:105) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:173) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:333) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:196) at com.bea.netuix.servlets.manager.PortalServlet.doPost(PortalServlet.java:772) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:150) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Hi,
The reason why you are seeing this exception is because there is a mismatch between the version of the WLPM API used by the portlets, with the version of the service that you have installed on you Domino server.
To explain a little, there are two sides to the API that is used to communicate with Lotus Domino:
1) the Java API side (used by the portlets that you have installed in the portal)
2) the Domino Service side (installed as a DSAPI filter in the HTTP task of a Domino Server)
Each Java API jar and Domino Service Executable are branded with a version number, which in your case does not match because the portlets came with one version of the Java API, and you have installed a non-matching version of the service on the Domino Service side (you probably extracted the executable for the service installation from the "BEA Personal Messaging API 4.3" bundle or installer).
The solution for this is to:
1) uninstall the Domino Service that you have plugged into the domino service
2) extract the Domino Service installer which was included with the portlet bundle. This is located in the "Program Files\compoze\groupware_portlets_bea-2.5\8.1\service\domino" directory if you ran the portlet installer, or in the "groupware_portlets_bea81-noinstall-25\groupware_portlets_bea-2.5\8.1\service\domino" directory if you used the "no-install" zip file.
As a tip, to quickly check whether the versions of the service and Java APIâ€™s that you are using are matching, perform the following steps:
1) hit the domino server with the following URL and notice the "service version": http://domino_service_url:http_port/compoze.czdo. This should be something like "Service Version: 3.6.102"
2)in your portal application (or in the portlet install bundle), open the harmony_portlets.jar file with winzip, then find the "compoze_products_information.properties" file. In this file, notice the "product.domino" version (e.g. product.domino = 3.6.102)
3) the two versions you have inspected must match in order for the connection between the portlet and service to succeed.
If you have verified that the "service" version and "java API" version (located in %portal_app_dir%/APP-INF/lib/harmony_portlets.jar, and you are still getting the exception, it is likely that there is a "harmony_portlets.jar" that included an old version of the Java API located somewhere in the portal server classpath. In this case, make sure that the only harmony_portlets.jar in the classpath is the one that was included with the portlet bundle that you have installed.
Regards,
Lev

8.1 equivalent of portlet:form event=bea.portal.framework.internal.refresh

Similar Messages

Maybe you are looking for