Weblogic talking to Websphere

Hi,
As anyone tried to call WebSphere EJB from weblogic? If so, how is it
achieved, and what to look out for?
Any pointers appreciated. Thanks!
ph
[email protected]

I have a servlet that is connecting using the
HttpsUrlConnection object to another servlet on
another domain. The idea is to use my servlet as a
proxy to this other application on the other domain
via a HttpsURLConnection object.
Okay. For clarity, let's refer to the Servlet that initiates the connection as Server A and the resource that it accesses as Server B.
For security reasons, I am not able to redirect or do
a form submission to this other application as that
will cause the user's browser to be "aware" of my
connection to this other application.
I do not follow. The user's browser is only able to connect to Server A (your Servlet) and can only receive a response from the same. It has no knowledge of what Server A does, including initiating a SSL connection to Server B.
The URLConnection works, however when the other
application's servlet either tries to redirect,
forward or do a form submission to a different
servlet, the content of the other servlet can't be
seen in the user's browser.
I thought you were proxying. Why would Server B issue a redirect to the browser? It could do so to Server A.
Is this a possible solution, or does
HttpsUrlConnection only allow HTTP header information
transfer on a webserver-to-webserver level?This is
what appears to be the case.
With HTTP, you will normally only 'see' the HTTP CONNECT command with the URL of the target server. Even the headers should be encrypted.
To complicate things, my application is on WebLogic
and is talking to another application on WebSphere.Makes no difference. HTTP is HTTP. SSL is SSL. That's all you are really using.
- Saish

Similar Messages

Mapping Weblogic 7 to Websphere

Hello,
I want to Weblogic 7 A/S to websphere .How to do it?I don't have much idea abt the websphere?
Plz help.
Thanks in advance.

If u don't know answer better don't answer and don't
try to act smart.Try to behave like a professionalBefore commenting on his reply, try to read that question again. It doesn't make any sense.
I want to Weblogic 7 A/S to websphere.
What does this mean?!? I want to "what"?!?
Your question sounds unpreofeesional enough. Try defining your problem clearly.

Weblogic server with Websphere Portal server

Hi,
I am having this peculiar problem.
I am using Websphere Portal Server and accessing an application which is running
on Weblogic
6.1. I am also using struts on both the portal server and weblogic server.
The first time I access a jsp which is on weblogic from websphere portal I get
it fine.
I have button on this jsp on submit of which another jsp on weblogic should come
up.
The problem is that on click of the button the URL which is being formed is
<ip of weblogic>/<path of portal server>.
I have no clue why this is happening and its driving me crazy.
Can anyone tell me whats happening?
Thanks
Siri

Siri-
This sounds like a URL rewriting issue with whatever proxy or tool you are using
to interface from WS to WLS. Basically, for the setup to work, any URL's that
are contained in the content served up by your WLS instance will have to be rewritten
such that your WS instance knows that the request is actually intended for the
WLS server.
-Brodi
"Siri" <[email protected]> wrote:
>
Hi,
I am having this peculiar problem.
I am using Websphere Portal Server and accessing an application which
is running
on Weblogic
6.1. I am also using struts on both the portal server and weblogic server.
The first time I access a jsp which is on weblogic from websphere portal
I get
it fine.
I have button on this jsp on submit of which another jsp on weblogic
should come
up.
The problem is that on click of the button the URL which is being formed
is
<ip of weblogic>/<path of portal server>.
I have no clue why this is happening and its driving me crazy.
Can anyone tell me whats happening?
Thanks
Siri

Servlet under Weblogic talking to external daemon via RMI

Hi,
We are trying to deploy our servlet-based application to Weblogic 8.1 and have
hit problems with RMI. This application has worked for years under Tomcat.
The servlet attempts to make some RMI calls to an external process which is running
it's own RMI registry. The RMI connection to that external process is being refused
though.
From the Weblogic doc, I've seen information about building RMI stubs using the
Weblogic rmic. But are application needs to support non-Weblogic servlet engines
too so we do not want to have to change our RMI classes around if at all possible.
Does anyone know if it is possible to use standard Java RMI classes inside of
Weblogic to talk to standard RMI classes outside of Weblogic?
Thank you,
Tom

Hi, Tom
Yes, it is possible. I have an application that uses standard Java RMI classes
inside Weblogic. There is a Java Control doing lookup to a remote component.
I had to take care with the permissions in the policy file. If the connection
is being refused, probably you have to review permissions, specially socket permissions.
Bye,
Diana
"Tom H" <[email protected]> wrote:
>
Hi,
We are trying to deploy our servlet-based application to Weblogic 8.1
and have
hit problems with RMI. This application has worked for years under Tomcat.
The servlet attempts to make some RMI calls to an external process which
is running
it's own RMI registry. The RMI connection to that external process is
being refused
though.
From the Weblogic doc, I've seen information about building RMI stubs
using the
Weblogic rmic. But are application needs to support non-Weblogic servlet
engines
too so we do not want to have to change our RMI classes around if at
all possible.
Does anyone know if it is possible to use standard Java RMI classes inside
of
Weblogic to talk to standard RMI classes outside of Weblogic?
Thank you,
Tom

Supporting latest release of bea weblogic or ibm websphere

Post Author: slack
CA Forum: Migration to XI R2
hi,
Wondering when do you plan to plan to certified the latest release platform of BEA Weblogic 10.x or IBM WebSphere 6.1. End of this year?
thanks

You can find the same under Oracle Access Manager - 3rd Party Integration.
Linux CD2
for Oracle_Access_Manager10_1_4_0_2_linux_BEA_WL_
SSPI

WebLogic with WebSphere MQ as an XA resource

I have been using WebLogic MDBs with WebSphere MQ as an external JMS provider. We just bought MQ Extended Client that would let external transaction managers do XA management with MQ. I have looked at IBM's document @
          http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf. This document indicates that Weblogic cannot be used to do XA with MQ; only three txn managers are mentioned - CICS, Encina, and Tuxedo.
          I don't believe that to be true because it says that it can be used with any XA compliant transaction manager. Is anyone aware of documents showing how to configure a WebLogic server (expecially MDBs) to use MQ extended client to do XA?

WL is an XA compliant TM, and many customers use it with MQ. For more information, you can start with this FAQ:
          http://e-docs.bea.com/wls/docs81/faq/interop.html#268632
          Also see the notes I've appended below.
          Finally, you can search this newsgroup - you will see that your question comes up quite a bit.
          Tom, BEA
          JMS Integration of Foreign Vendors with BEA WebLogic Server
          The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
          For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
          JMS Integration Overview
          - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
          - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
          - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
          - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
          - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
          - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
          - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
          Integration with 8.1 Details
          A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
          http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
          This document refers to helpful new 8.1 features, which simplify integration. These include:
          http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
          http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
          And are also summarized here (under interoperability):
          http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
          Also read the MDB documentation, which extensively covers integrating foreign vendors:
          http://edocs.bea.com/wls/docs81/ejb/message_beans.html
          The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
          Integration with 6.1 and 7.0 Details
          Read the "Using Foreign JMS Providers With WLS" white-paper:
          http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
          Note that this white-paper does not take into account 8.1 features.
          For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
          http://edocs.bea.com/wls/docs81/ejb/message_beans.html
          Non-Java Integration Options
          - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
          http://e-docs.bea.com/wls/docs61/jcom.html
          http://e-docs.bea.com/wls/docs70/jcom/
          http://e-docs.bea.com/wls/docs81/jcom/
          - Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
          http://e-docs.bea.com/wls/docs81/rmi_iiop/
          http://e-docs.bea.com/wls/docs70/rmi_iiop/
          http://e-docs.bea.com/wls/docs61/rmi_iiop/
          Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
          - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
          - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
          http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
          - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
          - Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
          Notes on MQ Remote Capable XA Clients
          Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
          http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
          The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
          - Required on WLS where MQ objects are bound into JNDI:
          com.ibm.mq.jar, com.ibm.mqjms.jar
          - Required only if MQ objects are bound into JNDI on a different server:
          com.ibm.mq.jar
          If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
          Notes on Oracle AQ Integration
          If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
          http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
          Caveats:
          The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
          Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
          The solution doesn't seem to support transactions, it may be possible to extend it to do so.
          MDB Thread Pool Notes
          WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
          http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
          (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
          MDB Concurrency Notes
          Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
          Design Guide-Lines and Performance Tuning Notes
          The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
          http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp

Advantages of Weblogic security framework over websphere security architecture

Hi,
Weblogic implement the security as a layer . And websphere, as far as I known
implements security as plug ins.
I'd like to known what are the advantages of weblogic security framework over
Websphere security archirtecture ? performance point of view, features, reliability,
robustness etc ...
Thanks a lot !

"walt" <[email protected]> wrote in message
news:3fca2d60$[email protected]..
>
Hi,
Weblogic implement the security as a layer . And websphere, as far as Iknown
implements security as plug ins.
I would consider the WLS security provider model to be a plugin model.
I'd like to known what are the advantages of weblogic securityframework over
Websphere security archirtecture ? performance point of view, features,reliability,
robustness etc ...
http://www.bea.com/content/news_events/white_papers/BEA_WLS_vs_Websphere_TCO_wp.pdf
http://e-docs.bea.com/wls/docs81/secintro/archtect.html
http://dev2dev.bea.com/products/wlserver/whitepapers/WLS_security_Framework.jsp
http://dev2dev.bea.com/products/wlserver81/index.jsp

OIM on Weblogic Vs WebSphere

Hi All
What could be the reasoning for promoting OIM/Weblogic over OIM/Websphere. I want to suggest my client to go with OIM/Weblogic combination rather than websphere. What should be my strong points to promote OIM-Weblogic.
Please help.
Thanks

WebSphere trials only last 30 or 60 days, so unless your client gives you a full version, your dev images/environments will need rebuilds fairly often. There are lot more integration pieces that tie OIM and WebSphere together which can cause lots of problems because it integrates the security of websphere with the database for OIM.
WebLogic is just the logical choice.
-Kevin

Does WebLogic 6.1 support client mode of MQ ?

I know WebLogic 6.1 is not supported yet. But we're still using it and plan to upgrade.
          AS-IS: WebLogic 6.1sp1 and IBM MQSeries 5.2 now. (using binding mode and XA)
          TO-BE: WebLogic 10 and WebSphere MQ 6.02 (using client mode and XA)
          We plan to upgrade MQ first, so, we need to know could WebLogic 6 supports to use client mode and XA with MQ 6.0. I only know WebLogic 8.1 is ok, but I cannot find document for WebLogic 6.
          btw, is there any suggestion for this upgrade ?

Hi,
          I can think of a few things worth noting:
          (A) I don't recall there being any specific support for MQ XA in 6.1SP1 - not even in MDBs. I think its likely that your current app just calls the MQ APIs directly and manually enlists MQ with the current transaction. This is all outside of WebLogic's control and will still work. (See the interop FAQ link below for an explanation of manual enlistment.)
          (B) Since 6.0, we've added a significant set of features to aid with foreign JMS vendor integration, particularly in the area of transparent XA integration, and we've also upgraded WebLogic JMS in general. These three links are probably a good place to get started if you care to review them:
          http://edocs.bea.com/wls/docs100/jms/interop.html
          http://edocs.bea.com/wls/docs100/jms_admin/intro.html#jms_features
          http://edocs.bea.com/wls/docs100/messaging.html
          (C) Very recently, I've heard that there have been some problems integrating WebLogic with MQ 6.0's "JMS 1.1 specification only" jars. These problems are being addressed or already have been addressed in newer releases but I doubt they've been looked at for version 6.0. Since its likely you're not planning to use the JMS 1.1 APIs in the very near term, I think this should not be a problem for you - you can just make sure to use MQ 6.0's JMS 1.0.2 jars.
          Hope this helps,
          Tom

Weblogic10.3(11g) Foreign Server With WebSphere MQ7.0.1.1 binding

Hi All ,
I have configured the WLS10.3 with MQ7.0.1.1 both are running in same physical box (same machine) successfully , and it work fine ...
but if the both are in different machine.. its not working.. please help if any doucment please share with me will be gr8 help full to me...
I have followed steps WebLogic MDB on WebSphere MQ for remote MQ server ...but still i am not abe to connect ..
Please share an screen shots /document /pdf .. how to generate the.binding file in remote ..

You may get some idea...after refering to the following links...
Please refer to the Below Link to achieve this....With Screenshots as well
Suitable for WLS8.x
http://www.ibm.com/developerworks/websphere/library/techarticles/0604_kesavan/0604_kesavan.html
<font color=maroon>
For later versions of WLS8.x you can even refer to :</font><BR>
http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

Weblogic Security framework

Hi,
I am trying to implement the above mentioned on my jsp pages to achieve Authentication, Authorisation and Role Mapping.
Please help me answer some doubts:
1) Where are the usernames, passwords stored for Authetication. How shall i configure it ?
2) If I were to implement the security framework directy from the jsp pages, instead of doing in the conventional way through portlets, which classes would i need from the bea api ?
Please help me get started on this. Thanks a lot!

"walt" <[email protected]> wrote in message
news:3fca2d60$[email protected]..
>
Hi,
Weblogic implement the security as a layer . And websphere, as far as Iknown
implements security as plug ins.
I would consider the WLS security provider model to be a plugin model.
I'd like to known what are the advantages of weblogic securityframework over
Websphere security archirtecture ? performance point of view, features,reliability,
robustness etc ...
http://www.bea.com/content/news_events/white_papers/BEA_WLS_vs_Websphere_TCO_wp.pdf
http://e-docs.bea.com/wls/docs81/secintro/archtect.html
http://dev2dev.bea.com/products/wlserver/whitepapers/WLS_security_Framework.jsp
http://dev2dev.bea.com/products/wlserver81/index.jsp

Need help to integrate weblogic and mq on separate machine

Hi,
is there any step by step instruction to help me integrating weblogic server and websphere mq on separate machines?
thanks.

You can use the message bridge to move messages between two destinations:
- http://download.oracle.com/docs/cd/E21764_01/web.1111/e13741/basics.htm#BRDGE116
For this you have to create a foreign server: http://download.oracle.com/docs/cd/E21764_01/web.1111/e13738/advance_config.htm#JMSAD194
and create a message bridge: http://download.oracle.com/docs/cd/E21764_01/apirefs.1111/e13952/taskhelp/bridge/bridge_instance/CreateJMSBridgeInstance.html
Here an example is provided for the JBoss variant: http://middlewaremagic.com/weblogic/?p=6066 and WebSphere MQ: http://www.coderanch.com/t/440070/EJB-JEE/java/Configure-Bridge-between-Websphere-MQ
To just use WebSphere MQ as the JMS provider: http://www.ibm.com/developerworks/websphere/library/techarticles/0604_kesavan/0604_kesavan.html (shows an example for WebLogic8)
- Configure a foreign JMS server, foreign connection factory, and foreign destination.
- Reference the local JNDI names of the foreign destination and foreign connection factory in, for example, an message-driven bean.

Websphere Vs WLS

hi,
I am trying to find some documenttation about product comparison of
Websphere Vs Weblogic.
thankx
suresh reddy

1) ClassLoader issues -- too weird to even figure out what WL is tryingto
accomplish ;-) ... but with a week of almost non-stop debugging we managed
to find a way to work around the issue until you guys get the next release
out with some class loader improvements (as mentioned by you or RobW)Our next major release, version 6.0 -- out in the fall, will be having a
complete rework of class loading. They should make your life a lot easier.
Our focus here is to make it completely simple.
We are making some small fixes into version 5.1. I have been told that the
next service pack (No. 6) will include some fixes for the dreaded class cast
exceptions. They should help matters somewhat.
>
2) Regressions -- every service pack fixes 9 bugs and introduces 1, and I
need about 7 of the nine fixes and the one regression usually hits a key
piece of functionality that I use (like authentication in SP4)
Unfortunately, form based authentication has been a problem in version 5.1.
We're working to fix that.
As for the quality of the service packs, we are dedicating more resources
immediately to make sure that the service packs come out with better
quality. Of course, please let us know if there are problems -- we want to
fix them as soon as possible.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Cameron Purdy" <[email protected]> wrote in message
news:[email protected]...
Michael,
There have only been two major area of frustration for me using WebLogic:
1) ClassLoader issues -- too weird to even figure out what WL is tryingto
accomplish ;-) ... but with a week of almost non-stop debugging we managed
to find a way to work around the issue until you guys get the next release
out with some class loader improvements (as mentioned by you or RobW)
2) Regressions -- every service pack fixes 9 bugs and introduces 1, and I
need about 7 of the nine fixes and the one regression usually hits a key
piece of functionality that I use (like authentication in SP4)
Then there is the frustration of trying to develop portable applications,
but that's its own story.
Cameron Purdy
http://www.tangosol.com
"Michael Girdley" <[email protected]> wrote in message
news:[email protected]...
3) BEA and IBM lead the market for a reason -- they have been able to
deliver working solutions. I must admit that both implementations
have
very
frustrating problems, but the value that they provide far out-weighs
the
frustrations.We would like to know what these frustrating problems are. If you have
specifics, please do take advantage of our developer center and let usknow.
Check out the "wish" area. The feedback you put there goes directly toall
of the folks defining the product.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Cameron Purdy" <[email protected]> wrote in message
news:[email protected]...
Start here:
http://www.flashline.com/components/appservermatrix.jsp
BEA WebLogic and IBM WebSphere are the market leaders (#1 and #2
respectively). IBM has not yet released a J2EE version (EJB 1.1 etc.)
of
WebSphere, but plans to do so this summer (although I guess the summeris
now almost over).
It boils down to this:
1) If you need EJB 1.1, stick with WebLogic for now.
2) Try to keep your work portable (and your non-portable workencapsulated)
in case you have to switch or support multiple platforms.
3) BEA and IBM lead the market for a reason -- they have been able to
deliver working solutions. I must admit that both implementations
have
very
frustrating problems, but the value that they provide far out-weighs
the
frustrations.
Cameron Purdy
http://www.tangosol.com
"indham inc" <[email protected]> wrote in message
news:[email protected]...
hi,
I am trying to find some documenttation about product comparison of
Websphere Vs Weblogic.
thankx
suresh reddy

JSF with Weblogic 8.1 SP2

Hello,
I am trying to deploy a JSF application in weblogic 8.1 SP2. But I am getting some servlet initialization exception. Have anyone of u faced such problem? Then please let me know the solution.
Also, is there any way to know what versions of different J2EE component does a particular version of weblogic supports? Websphere has got a batch file which when executed gives the supported versions of JDBC etc. in an html file. Does weblogic has something similar?
Regards,
Saurav

I think it is that answer. However, Weblogic Enterprise Security does
support SAML.
"Joe Newcomer" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
I would like to play around with SAML-based authentication with WebLogicPlatform
8.1 sp2.
I searched thru dev2dev, google and e-docs, but could not come up with anyhow-to
or example.
Can somebody please tell me how can we do this?! (I hope the answer is not'WebLogic
does not support SAML at this at this time!').
Thanks
Joe

Separation of tiers

Hi...,
In one of our application, we are thinking to separate the Web Layer(Jsp/JSF) & deploy it on the Web Server , EJB's on the App Server. My question is ,
-what benefits does it provide having such separation?
-When should we decide to separate the web tier from the application server?
- Which web server is stable enough to handle up to 10 thousand hits a day?
Regards,
P

But what are the benefits of separating the 2 in terms of :
- Having static pages on web server & EJB's on App server does make any difference to performance?
- Security?
- Industry Standard?These are architectural design decisions and should be based upon the business/domain requirements of the application. If the architectural design is crappy, then the performance will be crappy. If the design is good, then the performance will be good. The benefits would be discoverd/identified/revealed in the architectural design. And you can't get an architectural design without the application's business/domain requirements.
Some factors to consider are: the content of the web pages, the type of EJB used and the technical design of how the EJB communicate with the web application.
Whether there are benefits to having the web server on a different machine than the application server or not, depends upon how the application is designed, a multitude of possible constraints, and the application's quality-of-service requirements. What are the security requirements? What are the perfomance requirements? What are the maintainability requirements? Scalability requirements? What application server are we talking about? JBoss is nice, Weblogic is better, Websphere is worst, etc.

Weblogic talking to Websphere

Similar Messages

Maybe you are looking for