Bea Portal 7.x and Siteminder integration

Hi All,
Does anyone know if the integration kit supplied by BEA for the above
product versions which uses delegate realm solution, works with RDBMS Realm
Any extra configuration to be done for it to work ?
By default the examples are in LDAP v2 realms
Thanks.
Regards,
Leonard.

Yes, it saves a lot of grief, providing all servers are equally secure of
course...
On Mon, 8 Dec 2003 18:43:29 -0800, "Carl" <[email protected]> wrote:
Very cool. How does it work under the covers? The two WLS domain talk with
each other? So, the following would work:
o We have a WLS 7 domain
o The domain uses RDBMSRealm
o We created a new WLS 8 domain
o We set-up the trust
o Now, we login in to app on 8 domain, and it checks the 7's realm?Not quite - 8 still needs its own realm. The subjects (users and groups)
have to exist in both realms - 8 will just be taking 7's word for it that
"fred" has been authenticated but will still need to check fred's group
and/or role mappings.
The same realm data needs to exist for both systems. In LDAP it would be
easy enough to point them both at the same directory but.for a database
there is less control over the mappings - any differences between RDBMSRealm
and 8's RDBMSAuthenticator (unless you want to run compatibility security)
schemas might cause problems. I believe running the latter on both should
work but in principle the schema could change in a later version of the
product.
>
"Alex Thomas" <[email protected]> wrote in message
news:[email protected]..
See "Enabling Trust Between WebLogic Server Domains" section in
http://e-docs.bea.com/wls/docs81/secmanage/domain.html#1140940
This works between 7 and 8 (and, using the system account, on 6.1).
cheers
Alex
On Fri, 5 Dec 2003 10:22:29 -0800, "Carl" <[email protected]> wrote:
You can make the 7 domain trust the 8 domain so users don't have to log
in
twice, but you can't run the two versions in the same domain (not agreat
deal of benefit in doing so, once trust is sorted).How we do make 7 domain trust the 8 domain?

Similar Messages

[ANN] Databases, Portals, Web Services, and XML Integration Magic (Boston, July 29)

Recently added to DCI's Corporate and e-Business Portals
Conference:
Databases, Portals, Web Services, and XML Integration Magic
When: July 29, 2001, 9:00 AM - 5:00 PM
Where: Hynes Convention Center, Boston
http://www.dci.com/brochure/porbos/seminars.asp

Recently added to DCI's Corporate and e-Business Portals
Conference:
Databases, Portals, Web Services, and XML Integration Magic
When: July 29, 2001, 9:00 AM - 5:00 PM
Where: Hynes Convention Center, Boston
http://www.dci.com/brochure/porbos/seminars.asp

BEA 8.1 and Siteminder Integration

Does anybody have code sample and/or implementation for BEA 8.1 and Siteminder 6.0 integration?

Does anybody have code sample and/or implementation for BEA 8.1 and Siteminder 6.0 integration?

OIA and Siteminder integration

Has anyone integrated OIA(11g BP6) with Siteminder for authentication purposes? Can you please helo me with the configurations to be done in OIA and in Siteminder for this integration.
Inputs from integration done in any version of OIA will be helpful.
Let me know if you need more information.
Thanks,
JK

The files are located in the deployment path used by Weblogic. In my case that is $RBACX_HOME/rbacx/WEB-INF/lib where $RBACX_HOME = C:\OIA_11gR1.
Have I set it right?
I tried changing the variable to $RBACX_HOME to C:\OIA_11gR1\rbacx but the Application won't start when I change the variable RBACX_HOME.
Thanks!!!

BEA Portal 8.1 and Stellent Content Management

Does anyone have experience using Portal (any 8.1 version) with Stellent, using the IDCServerBean API. We are having serious performance issues with Stellent and its bundled Verity indexer - and trying to isolate whether it is a stellent issue, communication between stellent and portal, or a portal issue?
Thanks
Regards,
Kunal
Kunal Mittal

Kunal Mittal a ?crit :
Does anyone have experience using Portal (any 8.1 version) with Stellent, using the IDCServerBean API. We are having serious performance issues with Stellent and its bundled Verity indexer - and trying to isolate whether it is a stellent issue, communication between stellent and portal, or a portal issue?
Thanks
Regards,
Kunal
Kunal MittalWe are using Portal 8.1 SP4 with Stellent but using the CIS. I don't
know if it's the same thing than IDCServerBean API.
We didn't notice real performance issues. We are using Verity indexer too.
Can you give more details about your architecture ?
Thomas

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]

SiteMinder integration with the internal and external facing portals

Hi ,
We are in development phase for SiteMinder integration with the internal and external facing portals.The proposed dual authentication scheme which requires both SiteMinder for External facing portal (EFP) and LDAP for Internal portal .is it possible?
and is it possible to main to diff LDAP directories one is external users and one is for internal users.?
If you maintain 2 diff(external & internal) LDAP Directories in Siteminder Policy Server what about external users which are not exit in portal data source .
I appreciate if anyone can help me for my above query .
Regards
Tag

Hey Tag,
We do have a physical external Portal and a physical internal portal. The both the external and internal are connected to 2 LDAP directories.
For example the External Portal is connected to the Employee LDAP Direcotry and the Customer LDAP Directory. The Internal Portal is connected to the US Employee LDAP Direcotry and the EMEA LDAP Directory.
So each one of them is connected to 2 different LDAP Directories.
I believe that the Siteminder Policy is setup such that the Internal portal has a policy and the External portal has a seperate policy on the same Siteminder Server. Then each of the Policies is configured to connect to the approiate LDAP Directories.
You have to maintain the LDAP Directory information in both the portal and Siteminder Policy Server. It is required in the policy server so that it can authenticate the user and it is required in the Portal server so that it can authorize the user and display content based on thier assigned roles.
Hope that helps.
Regards,
Keith

Oracle Portal and Discoverer Integration

Portal Version: 9.0.2.0.1
RDBMS Versjion: 9.0.1.3
OS/Vers. Where Portal is Installed:: Suse 7 SLES
Error Number(s)::
Oracle Portal and Discoverer Integration
We're trying to integrate Discoverer with Portal unsuccessfully.
We made many things in accordance with oracle's documentation until add discoverer portlets (worksheet and list of workbooks) in a test page.
In view mode, the worksheet portlet shows the error:
"The portlet has not been defined. The publisher must define the portlet by clicking on Edit Defaults for the portlet on the edit mode of this page. Please contact the publisher of this page."
We think we have to edit properties before. Is this? Anyway edit worksheet portlet crashes between step 1 and 2. The error is: "The listener returned the following Message: 500 Internal Server Error".
We have a public conection created in EM and a discoverer application which can be viewed using plus or viewer.
Furthermore, it's not possible delete the added portlets neither the page that contain it. The error at delete is:
Error: An unexpected error occurred: User-Defined Exception (WWC-44082)
(WWC-00000)
An unexpected error has occurred in portlet instances: User-Defined Exception (WWC-
44846)
An unexpected error occurred: User-Defined Exception (WWC-43000)
The following error occurred during the call to Web provider:
oracle.portal.provider.v2.PortletNotFoundException
at oracle.portal.utils.v2.ContainerException.fillInStackTrace(Unknown Source)
at java.lang.Throwable.<init>(Throwable.java:78)
at java.lang.Exception.<init>(Exception.java:29)
at oracle.portal.utils.v2.ContainerException.<init>(Unknown Source)
at oracle.portal.provider.v2.PortletException.<init>(Unknown Source)
at oracle.portal.provider.v2.PortletNotFoundException.<init>(Unknown Source)
at oracle.disco.portlet.provider.DiscoPortletPersonalizationMgr.destroy
(DiscoPortletPersonalizationMgr.java:65)
at oracle.portal.provider.v2.DefaultPortletInstance.deregister(Unknown Source)
at oracle.webdb.provider.v2.adapter.soapV1.ProviderAdapter.deregisterPortlet
(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.doMethodCall(Unknown Source)
at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.processInternal(Unknown Source)
at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.process(Unknown Source)
at oracle.webdb.provider.v2.adapter.SOAPServlet.doSOAPCall(Unknown Source)
at oracle.webdb.provider.v2.adapter.SOAPServlet.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at com.evermind.server.http.ResourceFilterChain.doFilter
(ResourceFilterChain.java:59)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at com.evermind.server.http.ServletRequestDispatcher.invoke
(ServletRequestDispatcher.java:523)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal
(ServletRequestDispatcher.java:269)
at com.evermind.server.http.HttpRequestHandler.processRequest
(HttpRequestHandler.java:735)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
(WWC-43147)
Edit properties for portlet List of Workbook works but in view mode we have the error in the portlet area:
"Failed to refresh portlet. Please verify that the information used to create the
portlet instance or customization is still valid. Otherwise, please contact your
iAS administrator. oracle.discoiv.controller.FatalControllerException:
DiscoNetworkException - Nested exception: org.omg.CORBA.OBJECT_NOT_EXIST: minor
code: 0 completed: No null"
Any ideas?
Thanks

Hi there,
Have you applied any patches to 9ias since it was first installed? We had the same problem and had to apply a couple of patches to get the portlets working.
1. Apply the 9.0.2.53.16 one-off patch for Oracle 9iAS Discoverer which takes Discoverer up to 9.0.2.53.16. This patch appears to be password protected and you need to get someone at Oracle support to give you a password.
2. Apply the Discoverer Portlet Provider: 9.0.2.53.00c patch (patch no. 2595444) which gives you a new discportal.xsl file that actually works. It's this second step that solves your problem but you need to do step 1 before this. This is password protected as well.
3. As you've upgraded Disco on the server to 9.0.2.53, you'll need to upgrade Disco Admin & Desktop within your 9iDS installation using patch no. 2555265. This is because Disco 9.0.2.53 uses an upgraded EUL that Disco Admin & Desktop need to be patched to use.
This was the course of action Oracle support advised us about nine months ago. Of course they may have released a further patch to Disco that does 1 & 2 in one go, but we regularly carry out steps 1 and 2 on servers we use and we can use the Disco portlets successfully.
Hope this helps
Mark Rittman
[email protected]

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

How to implement multlingual on bea portal books and pages

Hi
We are are using BEA weblogic portal.
Now we want to use multilingual on bea portal.
Ho we can change the portal book's name and pages according to languages.
Regards
Paramdeep Singh

In your browser, you maintain your list of desired languages. This is an ordered list with the first language/locale in the list being the primary. This list of languages is passed to the server in as header. The portal server uses this header as the default mechanism to determine the language to serve back to the browser, although this behavior can be changed for your implementation if you wish. The server will look for a matching resource bundle based on the order of preference in your list of accepted languages.
So, if you want to receive fr_FR responses, ensure the fr_FR is listed first in your browsers list of languages and that you have created fr resources in your portal.
Brad

Can you access applications through BEA Portal Server and run applications on different BEA Application Server?

Is it possible to use common Corporate BEA Portal server and able to run different Business Unit applications on different BEA Application Servers?

Hi Akula,
You may want to read this article:
http://dev2dev.bea.com/products/wlportal81/articles/wsrp.jsp
It maybe related to what you want.
Regards,
--alex
Akula Venkata <[email protected]> wrote:
Is it possible to use common Corporate BEA Portal server and able to
run different Business Unit applications on different BEA Application
Servers?

BEA Custom Data Transfer and non-BEA Producer Portals?

Hello,
I recently had a problem where my BEA 10 Consumer was not sending my BEA 10 Producer the user's x509 digital certifcate used in authentication. In a non-WSRP environment, the certs come over in the HttpServletRequest object. I was told that for WSRP, BEA strips things out of the request object and the cert was one of those things. The solution was to implement BEA's Custom Data Transfer. I was able to create a solution for our problem using this approach. All is well.
Now I have run into a problem where one of our other projects is using a non-BEA portal and wants to also be a Producer. Since the Custom Data Transfer is a BEA solution (the Producer portlet class imports BEA classes), how can a non-BEA Producer receive the user's digital certificate since they presumedly can't implement the BEA Custom Data Transfer (unless, I guess, they bring in some BEA library file with those particualr classes).
Any insight? Thanks - Peter Len

Peter,
What producer are you using, some other vendors have implemented BEA's
custom data transfer. Also, the WSRP committee is looking into
standardizing this.
Additionally, you may use an interceptor (9.2 and later) to set HTTP
headers that the producer may be able to use.
Nate
Peter Len wrote:
Hello,
I recently had a problem where my BEA 10 Consumer was not sending my BEA 10 Producer the user's x509 digital certifcate used in authentication. In a non-WSRP environment, the certs come over in the HttpServletRequest object. I was told that for WSRP, BEA strips things out of the request object and the cert was one of those things. The solution was to implement BEA's Custom Data Transfer. I was able to create a solution for our problem using this approach. All is well.
Now I have run into a problem where one of our other projects is using a non-BEA portal and wants to also be a Producer. Since the Custom Data Transfer is a BEA solution (the Producer portlet class imports BEA classes), how can a non-BEA Producer receive the user's digital certificate since they presumedly can't implement the BEA Custom Data Transfer (unless, I guess, they bring in some BEA library file with those particualr classes).
Any insight? Thanks - Peter Len

Weblogic Portal Console Administration and SSO

Hello!
I have integrated Oracle Weblogic Server(10.3.2) with Oracle Identity Manager to achive Single Sign On. In IDM is set form login.
My base_domain configuration is : AdminServer and a Cluster_0 with two managed servers : Server_1 and Server_0.
I have as proxy server : Oracle HTTP Server (OHS) for each server : Admin-Server, Server-0, Server-1.
I targeted my portal app to cluster. My portal application contains Portal Administration Console, avaibled at /myAppAdmin.
Security Providers are (in this order):
1. OAMIDAsserter - Oracle Access Manager Identity Asserter( Control Flag : REQUIRED, Active Types : ObSSOCookie)
2. OIDAuthentificator - Provider that performs LDAP authentication (Control Flag: SUFFICIENT )
3. DefaultAuthenticator - Weblogic Authentication Provider ( Control Flag : SUFFICIENT
4. DefaultIdentityAsserter - Weblogic Identity Assertion provider.
When I access Portal Administration Console from /myAppAdmin (admin-tools.war)
1. I login first in IDM with the user from LDAP : weblogic_ldap. The login is ok and the ObSSOCookie is set.
2. I am redirected to login from Portal Administration Console (this thing is wrong and I want to jump this step. I want to go directly in Portal Administration Console after the first login).
3. I login in the second login page from Portal Administration Console with the same user : weblogic_ldap. The login has succeed.
4. I am logged in Portal Administration Console and I can add content ( for exemple)
What I have to do to have only the login form from IDM. To have the only two steps:
1. Login in Portal Administration Console using login form from IDM and a LDAP user
2. Access the Portal Administration Console
I have tried :
I have changed domain security Default Model : "Advanced" , set Combined Role Mapping Enabled to "FALSE", set Check Roles and Policies to
"ALL Web applications and EJBs" and selected for When Deploying Web Applications or EJBs: "Ignore roles and policies to DD".
After this changes I deployed myApp which contains /myAppAdmin Console with Security policies set to Advanced.
I have only the IDM login, the correct one, and after that I am able to see first page of the Portal Administration Console and whatever I click I receive the error:
####<Mar 29, 2011 11:20:55 AM EEST> <Error> <netuix> <server0-dns> <Server-0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <1301386855474> <BEA-423142> <The control com.bea.netuix.servlets.controls.page.SingleLevelMenu could not be rendered properly due to the following error:
com.bea.p13n.entitlements.common.PolicyMgmtAccessException: Attempt to access Entitlement Policy Mgmt API by user in invalid role. Entitlement Policy operation attempted by disallowed user ["principals=[]"].
at com.bea.p13n.entitlements.management.internal.SecurityHelper.isWLPAdminRole(SecurityHelper.java:937)
at com.bea.p13n.entitlements.management.internal.RolePolicyDelegate.roleExists(RolePolicyDelegate.java:346)
at com.bea.p13n.delegation.DelegationService.getParentInheritanceFlag(DelegationService.java:189)
at com.bea.p13n.delegation.DelegationService.getAdminPolicies(DelegationService.java:753)
at com.bea.p13n.delegation.DelegationService.isAdminPolicyOnResourceRoot(DelegationService.java:450)
at com.bea.p13n.delegation.DelegationService.isAdminPolicyOnResourceRoot(DelegationService.java:430)
at com.bea.jsptools.common.ToolsMenuTag.hasMenuAccess(ToolsMenuTag.java:354)
at com.bea.jsptools.common.ToolsMenuTag.doStartTag(ToolsMenuTag.java:130)
I have to modified admin-tools.war or something in domain's security or myApp's descriptors to be able to login in Portal Administration Console
using only SSO and not both SSO and default login?
Thank you for helping me.

Thank you user11089180, this bit me too. The new password of Passw0rd for the system account is really buried in the documentation.

WLPS and SiteMinder

Hi,
I had a small request w.r.t the Personalization Server.We are currently
using Netegrity SiteMinder4.51 as our third-party authentication tool and
WLPS as our personalization Server.Now the issue is that we would like to
have a common login process (one for the Application through SiteMinder)
and the other for WLPS.So how do I integrate WLPS with my application using
SiteMinder.
Any help would be appreciated.
Thanks,
Madhu

Hi,
I just started looking into integrating Cocoon's XSP with WLPS. I am
new to both technologies, but I am noticing that WLPS heavily uses JSP
tag libraries. I am in the process of trying to determine if XSP can
simply call JSP taglibs? If not does anyone who is more familiar with
WLPS have any feedback as to whether or not it would be possible to
create home grown XSP taglibs to get XSP and WLPS integrated? Are the
WLPS JSP taglibs just a separation layer between JSP and EJB, or do they
contain a lot of logic? A personalized XSP portal using WLS and WLPS
would be a very powerful platform!
Thanks,
Ian
"Marc A. Jones" wrote:
>
We are in the process of converting our code base from a "home grown" portal
app to WLPS. We used XML for our presentation layer, and would like to
continue using it. However, it doesn't appear as though it will be easy to
use XML in conjunction with WLPS.
Has anyone done this?--
Ian R. Brandt
Senior Software Engineer
Genomics Collaborative, Inc.
99 Erie Street
Cambridge, MA 02139
(617)661-2400 Ext.2244
(617)661-8899 FAX
[email protected]

Spring 2.5 and WLP integration

Hello,
I'm trying to integrate Spring 2.5 with a Bea Portal 9.2 application.
Given a simple three layers architecture (web/service/dao), I would like to be able to inject the service pojos into the action classes. The web layer is based on Struts and I'm using the Struts/Portal plugin.
I have tried different approaches but the bottom line is that the Portal framework (Beehive) doesn't like that the Action is instantiated by Spring. There are Lifecycle related exceptions.
I was wondering if any of you guys ever tried to do something like that and got any luck.
Of course, I can get the service bean via getBean(...) but I would like to avoid having Spring classes imported into my Struts controllers.
Any idea?
Thanks
Luciano

Is that so? No one ever tried integrating Spring and Portal?
That's quite scary, which company would ever decide to use a product that does have no history of integration with the leading J2ee framework (Spring).

Bea Portal 7.x and Siteminder integration

Similar Messages

Maybe you are looking for