Architecture Question with WebLogic

          WE have started a new project using WebLogic (in fact we will do that very
          soon). Since we are new to WebLogic, we are questioning the following
          tradeoff:
          About the system:
          The end system will be a web-based application providing secure access to
          its web users. The business logics (combination of some session and entity
          beans) store data in Oracle. The system is very report intensive, meaning in
          most of the time, people using it to get some report. The system also have a
          specific web interface to specific user for administration purpose. The
          admin ultimately create, update, remove data stored in Oracle.
          Questions 1 -- Servlets, JSP, and use of RMI:
          To generate the report, we decide to use WebLogic Servlet with JSP. There
          are 40 different reports, and each is mapped to one servlets. There will be
          a servlet manager to start other servlets, the ones that actually using the
          JSP to dynamically generating the HTML pages (the report).
          The Servlets themselves have to interface with the business logic objects
          using RMI. They have to do that since we don't want to re-implement the
          business logic in the Servlet again. The Business logic (Java Beans)
          executes on separate NT computer. Is this is a good architecture?
          Question 2 -- Applet/application and RMI:
          The system needs to interact with some admin users. To do that, the business
          logic portion (the session and entity Beans) provide remote interfaces to
          the applets/application. With Applet, Of course we can embed them in the
          HTML pages.Note that the business logic Beans are the ones also used by the
          servlets.
          Anyone see any problem with this approach? Is there any other alternative?
          Remember this approach has to be worry about synchronization between the
          report pages IF data is changed through applet/application by some
          administrator? This is something that we like to avoid! Anyone has a better
          alternative architecture or any suggestion?
          Thanks,
          Mansour

Manish,
          See below...
          >
          >WE have started a new project using WebLogic (in fact we will do that very
          >soon). Since we are new to WebLogic, we are questioning the following
          >tradeoff:
          >
          >About the system:
          >The end system will be a web-based application providing secure access to
          >its web users. The business logics (combination of some session and entity
          >beans) store data in Oracle. The system is very report intensive, meaning in
          >most of the time, people using it to get some report. The system also have a
          >specific web interface to specific user for administration purpose. The
          >admin ultimately create, update, remove data stored in Oracle.
          >
          So currently, you're supporting two different clients - one typically
          generating reports using a browser-based interface (HTTP/HTML) and the
          other a little more complex which may need the functionality of an
          applet or application.
          Servlets/JSPs should definitely be used to bridge the gap between your
          browser-based clients and your application's components. How dynamic
          is the underlying data used to generate the reports? Are the majority
          of reports static or based on adhoc queries? Sounds like they may be
          fairly static. If so, consider caching the reports somehow to prevent
          database hits. Although, consider the fact that the database caches
          data a lot better than we can - typically. I would create a few test
          cases to validate an approach.
          >Questions 1 -- Servlets, JSP, and use of RMI:
          >To generate the report, we decide to use WebLogic Servlet with JSP. There
          >are 40 different reports, and each is mapped to one servlets. There will be
          >a servlet manager to start other servlets, the ones that actually using the
          >JSP to dynamically generating the HTML pages (the report).
          >The Servlets themselves have to interface with the business logic objects
          >using RMI. They have to do that since we don't want to re-implement the
          >business logic in the Servlet again. The Business logic (Java Beans)
          >executes on separate NT computer. Is this is a good architecture?
          >
          Sounds like you guys have decided on using the second access model for
          JSPs and this certainly provides the most flexibility. Good decision.
          I'm assuming you really mean your business components are EJBs and not
          straight-up RMI objects as your statement may be interpreted?!?!?!
          EJBs are the correct choice for a lot of reasons.
          >Question 2 -- Applet/application and RMI:
          >The system needs to interact with some admin users. To do that, the business
          >logic portion (the session and entity Beans) provide remote interfaces to
          >the applets/application. With Applet, Of course we can embed them in the
          >HTML pages.Note that the business logic Beans are the ones also used by the
          >servlets.
          >Anyone see any problem with this approach? Is there any other alternative?
          >
          Using servlets to provide an interface to clients who choose to speak
          HTTP to your application is a good approach. For browser-based clients
          its a must and you may easily use the same servlets in your
          applets/applications as well. However, do consider the fact that your
          applets/applications may speak T3 to WL. My only concern with the
          latter approach is duplication of logic in the client itself and you
          will certainly want to eliminate this. Leveraging the servlets will
          certainly be a benefit.
          >Remember this approach has to be worry about synchronization between the
          >report pages IF data is changed through applet/application by some
          >administrator? This is something that we like to avoid! Anyone has a better
          >alternative architecture or any suggestion?
          >
          Consider a report manager layer that will be responsible for ensuring
          the latest report is potentially cached and available or is
          responsible for generating the report (by calling the servlet or bean
          or whatever...).
          Again, if the underlying data is fairly dynamic, then I would tend to
          generate the reports each time and rely on the database to cache data,
          optimize queries, handle synchronization issues... rather than
          attempting to cache reports in WL. If the data is fairly static
          though, developing a report manager layer that can cache reports...
          may be worth while.
          Jason

Similar Messages

JSESSIONID question with weblogic

I am building a web application ( call it Tracker ) that will be launched from a weblogic web application ( call it Scheduler ). The Tracker application is a non-java application. The scheduler application is a Java weblogic application.
Once the user logs into the Scheduler web application with their login and password, they will be issued a JSESSIONID. This already is happening.
What I want to do is call the Tracker application from within the Scheduler application, and have the authentication be automatic. In other words, I don't want to have the user to have to enter their login credentials once the tracker application is called. The tracker application should lauch and the user should be logged in automatically.
The Tracker application exists on a seperate web server.
My only idea for a simple solution is to have the scheduler application build a the URL to the tracker application with the JSESSIONID and the USERNAME of the person logged in. Then, with the tracker appliation URL is clicked, the tracker application web server would need to do a server side web server call to the scheduler application, and verify that the JSESSIONID and the USERID is a valid session. If it is then authenticate the tracker application session and continue.
I don't know much about weblogic, so would my idea even be possible? Also, I am open to other ideas. I know single sign on solutions like CAS would work, but I am looking for something a bit less involved than that.
Edited by: 856632 on May 4, 2011 2:02 PM

I am building a web application ( call it Tracker ) that will be launched from a weblogic web application ( call it Scheduler ). The Tracker application is a non-java application. The scheduler application is a Java weblogic application.
Once the user logs into the Scheduler web application with their login and password, they will be issued a JSESSIONID. This already is happening.
What I want to do is call the Tracker application from within the Scheduler application, and have the authentication be automatic. In other words, I don't want to have the user to have to enter their login credentials once the tracker application is called. The tracker application should lauch and the user should be logged in automatically.
The Tracker application exists on a seperate web server.
My only idea for a simple solution is to have the scheduler application build a the URL to the tracker application with the JSESSIONID and the USERNAME of the person logged in. Then, with the tracker appliation URL is clicked, the tracker application web server would need to do a server side web server call to the scheduler application, and verify that the JSESSIONID and the USERID is a valid session. If it is then authenticate the tracker application session and continue.
I don't know much about weblogic, so would my idea even be possible? Also, I am open to other ideas. I know single sign on solutions like CAS would work, but I am looking for something a bit less involved than that.
Edited by: 856632 on May 4, 2011 2:02 PM

Architecture/Design Question with best practices ?

Architecture/Design Question with best practices ?
Should I have separate webserver, weblogic for application and for IAM ?
If yes than how this both will communicate, for example should I have webgate at both the server which will communicate each other?
Any reference which help in deciding how to design and if I have separate weblogic one for application and one for IAM than how session management will occur etc
How is general design happens in IAM Project ?
Help Appreciated.

The standard answer: it depends!
From a technical point of view, it sounds better to use the same "midleware infrastructure", BUT then the challenge is to find the lastest weblogic version that is certified by both the IAM applications and the enterprise applications. This will pull down the version of weblogic, since the IAM application stack is certified with older version of weblogic.
From a security point of view (access, availability): do you have the same security policy for the enterprise applications and the IAM applications (component of your security architecture)?
From a organisation point of view: who is the owner of weblogic, enterprise applications and IAM applications. In one of my customer, application and infrastructure/security are in to different departments. Having a common weblogic domain didn't feet in the organization.
My short answer would be: keep it separated, this will save you a lot of technical and political challenges.
Didier.

QUESTION Re. Integrating TIBCO EMS with Weblogic 8.1 using MDB

Hi All,
 I am trying to integrate TIBCO EMS 4.3.0 with Weblogic 8.1 SP6.
 I have created a topic "SIMPLE.TOPIC" on the EMS. I have configured the Foreign JMS Server as follows:
 Name: TIBCO JMSServer
 JNDI Initial Context Factory:com.tibco.tibjms.naming.TibjmsInitialContextFactory
 JNDI Connection URL:tibjmsnaming://emshost:emsport
 I have configured the connection factory as follows:
 Name: TIBCO JMSTopicConnectionFactory
 Local JNDI Name: TopicConnectionFactory.Local
 Remote JNDI Name:TopicConnectionFactory
 User Name:username to connect to EMS server
 Password::pssword to connect to EMS server
 My JMS destination is configured as follows:
 Name: Tibco JMS Destination
 Local JNDI Name:SIMPLE.TOPIC.LOCAL
 Remote JNDI Name:SIMPLE.TOPIC
 My weblogic-ejb-jar.xml consists of the following code:
 <weblogic-ejb-jar>
 <weblogic-enterprise-bean>
 <ejb-name>SimpleTopicListener</ejb-name>
 <message-driven-descriptor>
 <pool>
 <max-beans-in-free-pool>200</max-beans-in-free-pool>
 <initial-beans-in-free-pool>20</initial-beans-in-free-pool>
 </pool>
 <destination-jndi-name>SIMPLE.TOPIC</destination-jndi-name>
 <connection-factory-jndi-name>TopicConnectionFactory</connection-factory-jndi-name>
 </message-driven-descriptor>
 <enable-call-by-reference>True</enable-call-by-reference>
 </weblogic-enterprise-bean>
 </weblogic-ejb-jar>
 The problem is, when I try to deploy this mdb, I get the following error:
 The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: SIMPLE.TOPIC. However, the object with the JNDI name: SIMPLE.TOPIC is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).
 I have checked and double checked to make sure that the topic SIMPLE.TOPIC does exist on the EMS server.
 Does anyone know what is the issue here and how to resolve it?
 Many thanks!
 -Kinshuk
 Edited by kinshukk at 05/14/2007 8:35 AM

(1) Check the standard ejb jar and make sure you've specified a topic destination type (the default is queue). For details, you can reference the WebLogic 9.0 MDB developer guide (the MDB dev guide was revised in 9.0 to include more detail than the 8.1 guide). Also, you might want to take a look at our integration/interop FAQ (again for 9.0 or later).
 (2) Change the weblogic-ejb-jar to reference the foreign local JNDI names - not the remote JNDI names.
 (3) Be careful about using the "." and "/" characters in local JNDI names - these have side-effects in JNDI (they force creation of subcontexts).
 Tom

Architecture question, global VDI deployment

I have an architecture question regarding the use of VDI in a global organization.
We have a pilot VDI Core w/remote mysql setup with 2 hypervisor hosts. We want to bring up 2 more Hypervisor hosts (and VDI Secondaries) in another geographic location, where the local employees would need to connect desktops hosted from their physical location. What we don't want is to need to manage multiple VDI Cores. Ideally we would manage the entire VDI implementation from one pane of glass, having multiple Desktop Provider groups to represent the geographical locations.
Is it possible to just setup VDI Additional Secondaries in the remote locations? What are the pros and cons of that?
Thanks

Yes, simply bind individual interfaces for each domain on your web server,
one for each.
Ensure the appropriate web servers are listening on the appropriate
interfaces and it will work fine.
"Paul S." <[email protected]> wrote in message
news:407c68a1$[email protected]..
>
Hi,
We want to host several applications which will be accessed as:
www.oursite.com/app1 www.oursite.com/app2 (all using port 80 or 443)
Is it possible to have a separate Weblogic domain for each application,all listening
to ports 80 and 443?
Thanks,
Paul

Has anyone used JAAS with WebLogic?

Has anyone used JAAS with Weblogic? I was looking at their example, and I have a bunch of questions about it. Here goes:
Basically the problem is this: the plug-in LoginModule model of JAAS used in WebLogic (with EJB Servers) seems to allow clients to falsely authenticate.
Let me give you a little background on what brought me to this. You can find the WebLogic JAAS example (to which I refer below) in the pdf: http://e-docs.bea.com/wls/docs61/pdf/security.pdf . (I believe you want pages 64-74) WebLogic, I believe goes about this all wrong. They allow the client to use their own LoginModules, as well as CallBackHandlers. This is dangerous, as it allows them to get a reference (in the module) to the LoginContext's Subject and authenticate themselves (i.e. associate a Principal with the subject). As we know from JAAS, the way AccessController checks permissions is by looking at the Principal in the Subject and seeing if that Principal is granted the permission in the "policy" file (or by checking with the Policy class). What it does NOT do, is see if that Subject
has the right to hold that Principal. Rather, it assumes the Subject is authenticated.
So a user who is allowed to use their own Module (as WebLogic's example shows) could do something like:
//THEIR LOGIN MODULE (SOME CODE CUT-OUT FOR BREVITY)
public class BasicModule implements LoginModule
private NameCallback strName;
private PasswordCallback strPass;
private CallbackHandler myCB;
private Subject subj;
         //INITIALIZE THIS MODULE
           public void initialize(Subject subject, CallbackHandler callbackHandler, Map sharedState, Map options)
                  try
                       //SET SUBJECT
                         subj = subject; //NOTE: THIS GIVES YOU REFERENCE
TO LOGIN CONTEXT'S SUBJECT
                                                 // AND ALLOWS YOU TO PASS
IT BACK TO THE LOGIN CONTEXT
                       //SET CALLBACKHANDLERS
                         strName = new NameCallback("Your Name: ");
                         strPass = new PasswordCallback("Password:", false);
                         Callback[] cb = { strName, strPass };
                       //HANDLE THE CALLBACKS
                         callbackHandler.handle(cb);
                  } catch (Exception e) { System.out.println(e); }
     //LOG THE USER IN
       public boolean login() throws LoginException
          //TEST TO SEE IF SUBJECT HOLDS ANYTHING YET
          System.out.println( "PRIOR TO AUTHENTICATION, SUBJECT HOLDS: " +
subj.getPrincipals().size() + " Principals");
          //SUBJECT AUTHENTICATED - BECAUSE SUBJECT NOW HOLDS THE PRINCIPAL
           MyPrincipal m = new MyPrincipal("Admin");
           subj.getPrincipals().add(m);
           return true;
         public boolean commit() throws LoginException
               return true;
    }(Sorry for all that code)
I tested the above code, and it fully associates the Subject (and its principal) with the LoginContext. So my question is, where in the process (and code) can we put the LoginContext and Modules so that a client cannot
do this? With the above example, there is no Security. (a call to: myLoginContext.getSubject().doAs(...) will work)
I think the key here is to understand JAAS's plug-in security model to mean:
(Below are my words)
The point of JAAS is to allow an application to use different ways of authenticating without changing the application's code, but NOT to allow the user to authenticate however they want.
In WebLogic's example, they unfortunately seem to have used the latter understanding, i.e. "allow the user to authenticate however they want."
That, as I think I've shown, is not security. So how do we solve this? We need to put JAAS on the server side (with no direct JAAS client-side), and that includes the LoginModules as well as LoginContext. So for an EJB Server this means that the same internal permission
checking code can be used regardless of whether a client connects through
RMI/RMI-IIOP/JEREMIE (etc). It does NOT mean that the client gets to choose
how they authenticate (except by choosing YOUR set ways).
Before we even deal with a serialized subject, we need to see how JAAS can
even be used on the back-end of an RMI (RMI-IIOP/JEREMIE) application.
I think what needs to be done, is the client needs to have the stubs for our
LoginModule, LoginContext, CallBackHandler, CallBacks. Then they can put
their info into those, and everything is handled server-side. So they may
not even need to send a Subject across anyways (but they may want to as
well).
Please let me know if anyone sees this problem too, or if I am just completely
off track with this one. I think figuring out how to do JAAS as though
everything were local, and then putting RMI (or whatever) on top is the
first thing to tackle.

Send this to:
newsgroups.bea.com / security-group.

Oracle 8.1.5 database connection problem with WebLogic 5.1

Hello,
the NSAPI integration works, also the JSP files.
But I have still problems with the Jdriver for my Oracle 8.1.5.
I get the message :
Failed to invoke startup class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.JdbcStartup
when the WebLogic Server is started.
Any ideas or hints about that?
Thanks in advance
Armin

Post the full stacktrace here
Also you might want to post jdbc related questions to weblogic.developer.
interest.jdbc
Kumar
DreamNEON wrote:
Hello,
the NSAPI integration works, also the JSP files.
But I have still problems with the Jdriver for my Oracle 8.1.5.
I get the message :
Failed to invoke startup class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.JdbcStartup
when the WebLogic Server is started.
Any ideas or hints about that?
Thanks in advance
Armin

Problem in Using Log4J with Weblogic 9.2

I am using Weblogic 9.2 and Log4j.
By using Admin console I set the Severity Level to WARNING and inside my java code is given below:
Logger logger = Log4jLoggingHelper.getLog4jServerLogger();
if (logger.isEnabledFor(Priority.DEBUG)){
logger.debug("DEBUG - Test Debug message");
logger.info("DEBUG - Test Info Message");
logger.warn("DEBUG - Test Warning Message");
logger.error("DEBUG - Test Error Message");
logger.fatal("DEBUG - Test Fatal Message");
Somehow the logger.isEnabledFor(Priority.DEBUG) returning 'TRUE' and the follwoing message is displayed.
<Nov 29, 2006 2:44:04 PM EST> <Warning> org.apache.log4j.Category> <000000> <DEBUG - Test Warning Message>
<Nov 29, 2006 2:44:04 PM EST> <Error> <org.apache.log4j.Category> <000000> <DEBUG - Test Error Message>
<Nov 29, 2006 2:44:04 PM EST> <Info> <org.apache.log4j.Category> <000000> <DEBUG - Test Fatal Message>
NOTE - The logger.debug() and logger.info() methods are not invoked because of the severity level to 'WARNING' in the console.
I would like to know why the Somehow the logger.isEnabledFor(Priority.DEBUG) is having a value of 'TRUE'.
I expected only the Somehow the logger.isEnabledFor(Priority.ERROR) will have the value of 'TRUE'.

Did you get an answer to your question? I have the same problem with WebLogic 10.0.

Enabling SSO with Weblogic Server

Hi,
Can someone please forward some documention on enabling SSO with Weblogic server for different applications using the admin console.
Is enabling SSO only possible programmatically??
Is there an external server amongst the Weblogic Platform that maintains this SSO information??
Regards,
Mukta

Pradeep,
Here are some questions for you.
1. what version of Weblogic App Server you are using?
2. Is it a weblogic Portal or a Java application deployed
on a Weblogic App Server?
3. You have mentioned that the users are stored in a table. Is it a database table ?
Anyway see the following link as a starting point?
http://e-docs.bea.com/wls/docs81/jconnector/security.html#1216783
If the customer has lot of other web applications that they want to integrate you can look at third party authentication solutions (Ex: Siteminder). But if it is a few or limited applications then custom solution would be more appropriate from the cost perspective.
Hope this can be a starting point.
-Regards
-Venkat Malempati

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

O/R mapping tool with WebLogic

Hi
What is the most popular O/R mapping tool used with WebLogic - TopLink? CocoBase?
Anything else?
Also, does anyone have market share numbers for this tool, e.g. out of the total
number of O/R tools used with WebLogic, XYZ's share is 75%.
Thanks in advance!
Ashish Ray

(from toplink support)
Andrew,
Hi there. I've performed some research regarding
your question, and it appears that having an
"automatic" 1:1 indirect relationship between an EJB
2.0 Entity Bean and a dependent Java object is not
currently supported by TopLink. Examining the
documentation, this non-support unfortunately isn't
documented. I have entered a feature request on your
behalf so that we might be able to support it in a
future major version of TopLink.
However, there are a couple of alternatives which
you can use:
1) We do support non-indirect 1:1 relationships
between an EJB 2.0 Entity Bean and a dependent Java
object. You could disable indirection, and maybe
make the relationship a batch read relationship so
that your performance will not be degraded.
2) You can write a concrete getter and setter, and
provide an instance variable on the entity bean for
your dependent object of type ValueHolderInterface.
Provide the private getters and setters for set and
get -Holder. Map this normally using TopLink, and
make sure Indirection is specified in the Mapping
Workbench.
IMPORTANT: TopLink will handle the normal
persistence management for this relationship,
however you will need to handle the merging back of
this object yourself (you had to do this in EJB 1.1
in TopLink as well). Luckily there are good docs on
this, and it's covered in detail - look at the
TopLink for WebLogic documentation : Runtime
Considerations > Managing dependent objects.
Personally, I would implement solution 1) with batch
reading on the attribute, because the dependent
object shouldn't be that "big" (otherwise it would
be an entity bean). This is an easier solution,
however you should investigate 2) fully yourself.

Using StoneBeat WebCluster load balancing with WebLogic

          Hi,
          I have done some testing of WebLogic Server with my company's StoneBeat WebCluster
          distributed load balancing software. This might be one more option to consider
          as a load balancing solution for WLS. It is advanced in the sense that load balancing
          is really dynamic, there are no single-points of failure (distributed architecture)
          and there is a very good, configurable test subsystem that runs on each cluster
          node to check for overload situations, HW/OS failures, ...
          In the initial testing, the WebCluster load balancing works with WebLogic replication,
          although there are some cases that need mroe consideration (please see below).
          I had to get a patch to WLS6SP1 on NT to make WLS' multicast work when there are
          several NICs on the cluster nodes.
          However, there is one case which causes problems:
          - I have 3 cluster nodes
          - P: 2, S: 3 (SessionServlet = 1)
          - 2: offline - P: 3, S: 1 (SessionServlet = 2; WebCluster randomly selected a
          new node to handle the connection)
          - 2: online - P: 2, S: ? (SessionServlet = 3, WebCluster redistributes the load
          when a node goes online)
          - 2: offline
          - P: 3, S: 1 (__SessionServlet = 1__) NB!
          The log messages show that when node 2 comes back online it retrieves the replica
          from the secondary (node 1) and not from the primary (node 3). After a while (5-6
          minutes), node 3 tries to update the replica on node 1. Node 1 considers this
          a stale update request and removes the Primary 16... (node name) and then the
          secondary for 16... (the replicated object). Then there's a message (still on
          node 1) that it is unable to find object 16... Back on node 3 the primary for
          16... is removed.
          From the WLS6 documentation (under the discussion of using replication with external
          HW load balancing solutions) I thought that this case would have been handled:
          - it is stated that after the failure of a node, if the HWLB box sends the next
          request to a node where there is no replica, WLS is able to retrieve the replica
          - to be fair, this is what happens: when node 2 came back online, it retrieved
          the replica from node 1 (the secondary) - I suppose that there is an assumption
          that if a request arrives to a node without a replica, the primary __must have
          failed__
          Is there any way to get around this problem?
          Admittedly, WebCluster has a problem in that the stickyness of connections is
          not perfect: - when a node goes online, a connection that was correctly persisted
          (based on either source-ip or source-network address) may be moved to a new node
          since the load is redistributed. Our load balancing is very dynamic, but doesn't
          maintain a list of who is connected to which node when resistribution takes place
          Regards,
          Frank Olsen
          Stonesoft


Rick,
You may want to look at the Alteon and F5 configuration we have on edocs.
Take a look at the following URLs for a possible solution
http://edocs.bea.com/wls/docs61/cluster/alteon.html#591902
http://edocs.bea.com/wls/docs61/cluster/bigip.html#591902
Chuck Nelson
DRE
BEA Technical Support

SOA Suite 11g and its compatibility with Weblogic

Hi ,
I have two questions:
1. From where do I download the SOA Suite 11g --Link to the download?
2.If SOA suite 11g can be installed on weblogic. I understand that SOA suite 10.1.3.4 is compatible with weblogic 9.2 but need some inputs on the SOA Suite11g!
Cheers
Prabal

Prabal,
Did you get an answer or we have to wait for the official release till July-1-2009.
Thanks,
Rahul

Oracle VM Server for SPARC - network multipathing architecture question

This is a general architecture question about how to best setup network multipathing
I am reading the "Oracle VM Server for SPARC 2.2 Administration Guide" but I can't find what I am looking for.
From reading the document is appears it is possible to:
(a) Configure IPMP in the Service Domain (pg. 155)
- This protects against link level failure but won't protect against the failure of an entire Service LDOM?
(b) Configure IPMP in the Guest Domain (pg. 154)
- This will protect against Service LDOM failure but moves the complexity to the Guest Domain
- This means the there are two (2) VNICs in the guest though?
In AIX, "Shared Ethernet Adapter (SEA) Failover" it presents a single NIC to the guest but can tolerate failure of a single VIOS (~Service LDOM) as well as link level failure in each VIO Server.
https://www.ibm.com/developerworks/mydeveloperworks/blogs/aixpert/entry/shared_ethernet_adapter_sea_failover_with_load_balancing198?lang=en
Is there not a way to do something similar in Oracle VM Server for SPARC that provides the following:
(1) Two (2) Service Domains
(2) Network Redundancy within the Service Domain
(3) Service Domain Redundancy
(4) Simplify the Guest Domain (ie single virtual NIC) with no IPMP in the Guest
Virtual Disk Multipathing appears to work as one would expect (at least according the the documentation, pg. 120). I don't need to setup mpxio in the guest. So I'm not sure why I would need to setup IPMP in the guest.
Edited by: 905243 on Aug 23, 2012 1:27 PM

Hi,
there's link-based and probe-based IPMP. We use link-based IPMP (in the primary domain and in the guest LDOMs).
For the guest LDOMs you have to set the phys-state linkprop on the vnets if you want to use link-based IPMP:
ldm set-vnet linkprop=phys-state vnetX ldom-name
If you want to use IPMP with vsw interfaces in the primary domain, you have to set the phys-state linkprop in the vswitch:
ldm set-vswitch linkprop=phys-state net-dev=<phys_iface_e.g._igb0> <vswitch-name>
Bye,
Alexander.

Dynamic XML with Weblogic ?

hello all !!
May be this question is already answered, and sorry for that, but here again !
I am trying to use Weblogic server, in order to process XML files, this files
make a query to my Oracle Data Base, Before this I was using Cocoon (apache) to
generate the dynamic XML with the query's result, is there a way to make the same
thing with Weblogic ? anybody know how to do it ? do yu have a simple example
? here is a sample code that I use with cocoon.
<?xml version="1.0" ?>
<?cocoon-process type="xsp"?>
<xsp:page language="java" xmlns:sql="http://www.apache.org/1999/SQL"
xmlns:xsp="http://www.apache.org/1999/XSP/Core"
xmlns:request="http://www.apache.org/1999/XSP/Request">
<page title="SQL Search Results">
<sql:execute-query>
<sql:driver>oracle.jdbc.driver.OracleDriver</sql:driver>
<sql:dburl>jdbc:oracle:thin:@IP_Address:1521:cta</sql:dburl>
<sql:username>User</sql:username>
<sql:password>Password</sql:password>
<sql:doc-element>My_table</sql:doc-element>
<sql:row-element>record</sql:row-element>
<sql:query>select * from My_table</sql:query>
</sql:execute-query>
</page>
</xsp:page>
Thanks a lot for your help !
Gustavo Mejia
INFOTEC

Since Cocoon is a servlet, just install it in Weblogic.
"Gustavo Mejia" <[email protected]> wrote in message
news:3b5ca3fa$[email protected]..
>
hello all !!
May be this question is already answered, and sorry for that, but hereagain !
>
I am trying to use Weblogic server, in order to process XML files, thisfiles
make a query to my Oracle Data Base, Before this I was using Cocoon(apache) to
generate the dynamic XML with the query's result, is there a way to makethe same
thing with Weblogic ? anybody know how to do it ? do yu have a simpleexample
? here is a sample code that I use with cocoon.
<?xml version="1.0" ?>
<?cocoon-process type="xsp"?>
<xsp:page language="java" xmlns:sql="http://www.apache.org/1999/SQL"
xmlns:xsp="http://www.apache.org/1999/XSP/Core"
xmlns:request="http://www.apache.org/1999/XSP/Request">
<page title="SQL Search Results">
<sql:execute-query>
<sql:driver>oracle.jdbc.driver.OracleDriver</sql:driver>
<sql:dburl>jdbc:oracle:thin:@IP_Address:1521:cta</sql:dburl>
<sql:username>User</sql:username>
<sql:password>Password</sql:password>
<sql:doc-element>My_table</sql:doc-element>
<sql:row-element>record</sql:row-element>
<sql:query>select * from My_table</sql:query>
</sql:execute-query>
</page>
</xsp:page>
Thanks a lot for your help !
Gustavo Mejia
INFOTEC

Architecture Question with WebLogic

Similar Messages

Maybe you are looking for