HELP with WebSphere MQ

How do i run the WebSphere MQ for java in Windows Xp..
thanks in advance

"WebSphere MQ for java" is just an API to let you access MQ queue managers, you need to ensure you have access to a server running the MQSeries server software (could be installed locally or on another platform).
Beyond that, you need to start the MQ service, in the same way you start any service, and create yourself a queue manager, and some queues. Then you are closer to being able to use the Java API.
But this is all too big a topic for this forum, you need to know how to use MQ series, and then come back here with any specific problems.

Similar Messages

Help with WebSphere Businessobjects sso integration package

Hi All,
We are using the SSO package from businessobjects and it works great.. However, we've noticed that in the inbox view, the "Sent Date" does not server our needs, we would like to show Instance Creation Date instead so that if we ever need to send copies of ran instances to a user's inbox, it will not show all of them having the sent date... we've noticed in CMS, when you go look at the history of a report, the report time shows "Report Name and Date Time".. wondering if we can get the Inbox view to show this info instead of the date sent ?
Kevin

Hello Kevin,
We spoke on the phone yesterday - I'm inferring this issue is also relevant to the BusinessObjects Enterprise WebSphere Portal Integration Kit (PIK).
If you confirm, I can transfer this thread to the correct forum for PIK questions.
Sincerely,
Ted Ueda

Error in JMS Adapter while communicating with WebSphere MQ 7.5

Guys,
I am trying to integrate JMS Adapter with WebSphere MQ.
JMS Adapter : 14.0.2.0
WebSphere MQ : 7.5
I am getting error like below. Please help me out. Thanks
17/04/14 16:25:49 java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsSession.createQueue(Ljava/lang/String;)Ljavax/jms/Queue;
at com.ibm.mq.jms.MQSession.createQueue(MQSession.java:708)
at com.acta.adapter.jms.MQConfigHandler.getQueue(MQConfigHandler.java:74)
at com.acta.adapter.jms.JMSAdapter.getQueue(JMSAdapter.java:547)
at com.acta.adapter.jms.JMSGetOperation.start(JMSGetOperation.java:398)
at com.acta.adapter.sdk.OperationWrapper.runOperation(OperationWrapper.java:171)
at com.acta.adapter.sdk.OperationWrapper.run(OperationWrapper.java:94)
at java.lang.Thread.run(Thread.java:662)
I have added following jars in class path of the adapter.

Problem solved after removing j2ee.jar file from classpath !

Error integrating OBIEE portlet with WebSphere Portal

Hi
I am trying to integrate OBIEE 10.1.3.4.1 with Websphere Portal.
I perform following steps :
1. Installed OBIEE and created a report at url "http://punitp63969d:9704/analytics/saw.dll?Dashboard"
2. Modified portlet.xml of sawjsr168portlets.war as follows
<preference>
<name>oracle.bi.presentation.sawserver.URL</name>
<value>http://punitp63969d:9704/analytics/saw.dll?Dashboard</value>
<read-only>false</read-only>
</preference>
<preference>
<name>oracle.bi.presentation.portlets.jsr168.reportui.AdminUserName</name>
<value>Administrator</value>
<read-only>false</read-only>
</preference>
<preference>
<name>oracle.bi.presentation.portlets.jsr168.reportui.AdminPwd</name>
<value>Administrator</value>
<read-only>false</read-only>
</preference>
<preference>
<name>oracle.bi.presentation.portlets.websphere.SuperuserSlotId</name>
<value>sawseveradmin</value>
<read-only>false</read-only>
</preference>
where Administrator/Administrator is user-id/password for OBIEE and
sawseveradmin is name of credential vault in WebSphere-Portal.
3. Deployed the war on WebSphere Portal and got portlet disable with following error in log :
WSVR0200I: Starting application: PA_SAWReport
9/4/09 18:42:52:067 IST 000001ff ApplicationMg A WSVR0204I: Application: PA_SAWReport Application build level: Unknown
9/4/09 18:42:52:708 IST 000001ff WebGroup A SRVE0169I: Loading Web Module: SAWReport.
9/4/09 18:42:52:973 IST 000001ff VirtualHost I SRVE0250I: Web Module SAWReport has been bound to default_host:10000,:80,:10002,:10015,:10016,:443,:10023,:10026,:10040,:10035.
9/4/09 18:42:53:130 IST 000001ff ApplicationMg A WSVR0221I: Application started: PA_SAWReport
9/4/09 18:42:59:692 IST 00000037 WebContainer E SRVE0255E: A WebGroup/Virtual Host to handle /searchfeed/myserver/scopes has not been defined.
9/4/09 18:43:26:458 IST 00000037 WebContainer E SRVE0255E: A WebGroup/Virtual Host to handle /searchfeed/myserver/scopes has not been defined.
9/4/09 18:43:50:318 IST 000000a5 ServletWrappe I SRVE0242I: PA_SAWReport [wps/PA_SAWReport] Oracle_Business_Intelligence_Report_View_Portlet: Initialization successful.
9/4/09 18:43:50:521 IST 000000a5 MimeResponseI E com.ibm.ws.portletcontainer.core.impl.MimeResponseImpl getWriter EJPPC0176W: Invalid content type
9/4/09 18:43:50:661 IST 000000a5 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Oracle_Business_Intelligence_Report_View_Portlet. Exception thrown : javax.servlet.ServletException: java.lang.IllegalStateException: No content type set.
at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:369)
Caused by: java.lang.IllegalStateException: No content type set.
at com.ibm.ws.portletcontainer.core.impl.MimeResponseImpl.getWriter(MimeResponseImpl.java:114)
at com.siebel.analytics.web.portlets.jsr168.ReportUI.checkUser(ReportUI.java:852)
at com.siebel.analytics.web.portlets.jsr168.ReportUI.doView(ReportUI.java:167)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
at com.siebel.analytics.web.portlets.jsr168.ReportUI.doDispatch(ReportUI.java:1058)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
at com.ibm.ws.portletcontainer.invoker.impl.PortletFilterChainImpl.doFilter(PortletFilterChainImpl.java:128)
at com.ibm.wps.propertybroker.standard.filter.C2APortletFilter.doFilter(C2APortletFilter.java:185)
at com.ibm.ws.portletcontainer.invoker.impl.PortletFilterChainImpl.doFilter(PortletFilterChainImpl.java:120)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:573)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:114)
at com.ibm.isclite.container.collaborator.PortletServletCollaborator.doRender(PortletServletCollaborator.java:68)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
at com.ibm.ws.portletcontainer.rrd.RRDServerPortletServletCollaborator.doRender(RRDServerPortletServletCollaborator.java:123)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
at com.ibm.ws.portletcontainer.cache.CacheCollaborator.doRender(CacheCollaborator.java:92)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
at com.ibm.wps.pe.pc.waspc.core.impl.PortletServletCollaboratorImpl.doRender(PortletServletCollaboratorImpl.java:156)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:273)
... 219 more
Please help me resolve this issue.Thanks in advance.

I'm getting the same error on WebSphere 6.1.5. Is there any solution for this?

Style Sheet Problem with Websphere

Hello. If anyone here has any experience with Websphere or iSeries, I would appreciate some help. I posted this topic in the Websphere forum , but it seems that forum isn't very active. Anyway, I can't get my style sheet to work with a java servlet application that I installed on an iSeries server. I put together the app and style sheet through WebSphere and exported everything to the server as an .ear file, installed the application and the program works; however, the app isn't accessing the style sheet. I'm new to both iSeries and Websphere. I've been trying this line:
writer.println("<LINK rel='stylesheet' type='text/css' href='Master.css'>");
and have tried putting the style sheet in the same folder as the class file, tried putting it in the Java Source folder, tried it all over the place really and have tried making the path absolute. I've also tried pasting the .java file into the classes folder with the .class file. None of my efforts have been successful. Is this even possible? Any help would be appreciated. Thank you.

have tried putting the style sheet in the same folder as the class file, tried
putting it in the Java Source folder, tried it all over the place really...In your web application, it should go in the same directory where you would put an HTML file or a JSP file. All those places you tried are places that the web server keeps hidden from clients. You should be able to request the CSS file from your browser in exactly the same way you would request an HTML or JSP file.

Integration with Websphere 5.0 (EJB 2.0) problems

Hello all,
Although a bit new to JDO, I have been trying to integrate Kodo 2.4 with
Websphere 5.0 (using EJB 2.0).
I have been basically binding a PersistenceManagerFactory into JNDI via
start-up servlet, however got the exception bellow when I tried to create
PersistenceManagerFactory (in setSessionContext of the EJB).
<i>JDOFatalInternalException: Could not perform automatic lookup of EJB
container's javax.transaction.TransactionManager implementation. Please ensure
that you are running the application from within an <b>EJB 1.1</b> compliant
EJB container, and then set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties property to the appropriate
value to obtain the TransactionManager.</i>
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with WSAD
5.0?
Thank you,
Petr

Petr-
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?Yes, we do have reports of people using Kodo successfully from within
Websphere. However, it should be noted that it is not as rigorously
tested internally at SolarMetric as some other application servers (E.g.,
JBoss and WebLogic). In short, integration is known to work, but it
might be a little more rough around the edges than for other application
servers (as shown in our misspelling of Websphere's TransactionManager
implementation name).
How do I tell Kodo to use existing Datasource managed by app server?You can have Kodo use a named DataSource by specifying the
javax.jdo.option.ConnectionFactoryName property (see
http://www.solarmetric.com/docs/2.4.0/docs/manual.html#javax.jdo.option.ConnectionFactoryName).
This is often more appropriate for applications server usage, since it
allows you to configure pooling and other information from within the
application server's centralized configuration.
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snetWhat kind of driver is COM.ibm.db2.jdbc.app.DB2Driver? The DB2
configuration we use for testing with IBM's drivers is:
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.net.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2://SERVER_NAME/DATABASE_NAME
They shouldn't behave differently (I am guessing that the app driver is
a type 2 driver or something), but it might be worth a shot to try using
the net driver. If this fixes the problem, please let us know, because
it will indicate that Kodo has a deficiency with one of IBM's drivers
that we should look into resolving.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.The binding code looks fine, and you are obviously able to retrive the
PM and start persistence operations. Note that you should also be able
to deploy Kodo as a Resource Adapter (which allows Kodo configuration
through the centralized Websphere configuration interface). However, I
doubt this is part of the issue.
So, in short, I recommend trying the following things:
1. Using the ConnectionFactoryName to use the DataSource defined for the
appserver, on the off chance this will fix it.
2. Using the net driver instead of the app driver.
3. Seeing if it will work with javax.jdo.option.Optimistic set to false
If none of these work, please let us know, and we will continue to
investigate other possible solutions.
In article <[email protected]>, Petr Bulanek wrote:
Hello Marc,
Very good guess. Pretty much the same code worked well without App server.
In that case, there obviously was no magic related to
TransactionManagerFactory initialization (see bellow).
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?
How do I tell Kodo to use existing Datasource managed by app server?
Here is the basic configuration (URL, class, etc):
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snet
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
We use DB2 Version 7.2/Version 7.1 FixPak 3 for Windows, in case it helps.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.
The new EESimpleConfiguration(true) construct seems to (by default) read
the kodo.properties file that is part of the project.
EEConfiguration conf = new EESimpleConfiguration(true);
conf.setManagedRuntimeProperties(\"TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\");
conf.setManagedRuntimeClass(\"com.solarmetric.kodo.ee.InvocationManagedRuntime\");
EEPersistenceManagerFactory pmf =
                    new EEPersistenceManagerFactory(conf);
InitialContext ic = new InitialContext();
ic.rebind(\"KodoPMF\", pmf);
Thank you,
Petr
Marc Prud\'hommeaux wrote:
Petr-
It looks like DB2 doesn\'t like our attempt to close the connection
without a rollback or commit. This is odd, since we have never
seen this happen in our stand-alone DB2 tests. Can you let us know
the connection details (driver, connectionURL, etc)?
In the meantime, one possible workaround may be to turn off
optimistic transactions (since this will cause the PM to
only use a single Connection); can you try to specify:
javax.jdo.option.Optimistic=false
Also, have you tried to run this code in a non-managed environment
(e.g., outside the application server)? I would be interested
to know if it is related to running within an appserver.
In article <[email protected]>, Petr Bulanek wrote:
Hi Abe,
Thank you for a speedo reply. You guys really are on the ball!!!
As you suggested, the
\\\'com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\\\'
did the job (for others, please note that the proper package name should
contain \\\'jts.jta\\\', not \\\'jts.jts\\\').
Unfortunately, I got another problem. When running a method containing
query (code bellow),
I get SQLException complaining about \\\'Invalid transaction state\\\'.
The method that executes the query is a stateless transactional Session
bean.
Thank you for your help,
Petr
--------------------------- DB2 - transaction state description
CLI0116E Invalid transaction state.
Explanation: There was a transaction in progress when SQLDisconnect was
called.
User Response: Call SQLTransact before calling SQLDisconnect.
--------------------------- Exception ------------------------------------
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] preparing statement <369367952>: SELECT DISTINCT
PARENTX.JDOCLASSX FROM PARENTX
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] executing statement <369367952>: [reused=1;params={}]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close:
com.solarmetric.datasource.PoolConnection@14079b90[[requests=6;size=6;max=70;hits=0;created=6;redundant=0;overflow=0;new=6;leaked=0;unavailable=0]]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close connection
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC [ C:null; T:1446894474; D:118283149 ]
exception when closing connection
[2/01/03 16:34:19:541 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC TRAS0014I: The following exception
was logged COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0116E
Invalid transaction state. SQLSTATE=25000
atcom.solarmetric.datasource.ConnectionWrapper.close(ConnectionWrapper.java:243)
atcom.solarmetric.datasource.DataSourceImpl$AbstractPool.close(DataSourceImpl.java:690)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:373)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:347)
at com.solarmetric.datasource.PoolConnection.close(PoolConnection.java:70)
atcom.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:885)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java:654)
atcom.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:274)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.addSubclassConditions(ClassMapping.java:1239)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1218)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:717)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:92)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:792)
atcom.solarmetric.kodo.query.QueryImpl.executeWithArray(QueryImpl.java:668)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:609)
at com.testkodo.ejb.ControllerBean.observeHumans(ControllerBean.java:66)
--------------------------- Failing code sample
try {
               PersistenceManager pm = factory.getPersistenceManager();
               Extent ex = pm.getExtent(Parent.class, false);
               Query q = pm.newQuery(ex, \\\"name==parName\\\");
               q.declareParameters(\\\"String parName\\\");
               Collection col = (Collection) q.execute(\\\"James\\\");
               Iterator iter = col.iterator();
               Parent pp;
               Collection ch;
               while (iter.hasNext()) {
                    pp = (Parent) iter.next();
                    System.out.println(pp);
                    ch = pp.getChildren();
                    Iterator it= ch.iterator();
                    while (it.hasNext()) {
                         System.out.println(it.next());
               q.closeAll();
               pm.close();
          } catch (Exception e) {
               System.out.println(e);
               throw new EJBException(e);
Abe White wrote:
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
EJB 2.0 is also supported. Sorry for the confusing error message.
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with
WSAD
5.0?
Try these settings:
com.solarmetric.kodo.ee.ManagedRuntimeClass=\\\\
     com.solarmetric.kodo.ee.InvocationManagedRuntime
com.solarmetric.kodo.ee.ManagedRuntimeProperties=\\\\
     TransactionManagerMethod=\\\\
     com.ibm.ejs.jts.jts.TransactionManagerFactory.getTransactionManager
Marc Prud\'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

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

Will Flex 2 integrate with WebSphere Portal Server

I have a few questions in trying to argue the case for Flex 2
to a very large client:
Will Flex 2 integrate with IBM WebSphere Portal Server ?
Will Flex 2 integrate with WebSphere if not with Portal
Server ?
Does Flex comply to the JSR168 Portlet specification ?

http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=wsrp_1 .html
http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=wsrp_2 .html
http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=wsrp_3 .html

Apache SOAP with websphere 6.1

I want to use Apache SOAP in websphere 6.1 since we will be reusing the framework developed already using Apache SOAP.This has been implemented only with weblogic previously.
Now we are trying to use this in combination with websphere 6.1,Is this supported?How to proceed?

Hi Thierry,
When we wrote the web services layer for BEA we purposefully left out
stateful session beans and entity beans because they did not match the
"services" model and there is no standard way to keep the state between
calls to the service. I believe the Apache implementation uses the HTTP
session for this behaviour. I don't know what the problem is with the
Apache SOAP implementation but I can try and help you either 1) use a
stateless session bean to call your sfsb, or 2) convince me that stateful
beans implemented outside the web services standard is something BEA should
support.
Sam
"Thierry Janaudy" <[email protected]> wrote in message
news:[email protected]..
Hello,
I wanted to use BEA's implementation of SOAP, but the problem is that you
cannot call SFSB.
Therefore I tried to install and run Apache SOAP (Which provides a service
for SLSB, SFSB, EB).
However, you I try to remotely list the services through:
java -cp %CP% org.apache.soap.server.ServiceManagerClient
http://localhost:7001/soap/servlet/rpcrouter list
I always get
Exception in thread "main" java.lang.NoSuchMethodError
at org.apache.soap.util.xml.QName.<init>(QName.java:80)
at org.apache.soap.util.xml.QName.matches(QName.java:146)
at org.apache.soap.Envelope.unmarshall(Envelope.java:237)
at org.apache.soap.rpc.Call.invoke(Call.java:230)
at
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClien
t.java:129)
at
org.apache.soap.server.ServiceManagerClient.list(ServiceManagerClient.java:1
51)
at
org.apache.soap.server.ServiceManagerClient.main(ServiceManagerClient.java:2
37)
Do you have any idea why?
Thx

Configuring blazeds with websphere

Hello,
I need some help deploying blazeds on websphere. Can anyone please give me steps to do this. My blazeds application is not able to access web services configured in the proxy-setting.config and also not able to get to the configured java remote object.
Thanks

Hi Alex,
Thanks a lot for the response. My swf file is in the web application. I think I am missing some configuration. Do I have to configure a servlet in websphere for flex to work. I also have a java remote object which is also not working. I am attaching my config files. Could you please have a look and tell me if I need to add something else.
Thanks a lot for your help
Roopa
--- On
Tue, 6/24/08, Alex Glosband
<[email protected]> wrote:
From: Alex Glosband <[email protected]>
Subject: Re: configuring blazeds with websphere
To: [email protected]
Date: Tuesday, June 24, 2008, 5:48 AM
A new message was posted by Alex Glosband in
General Discussion --
configuring blazeds with websphere
Hi. The steps for deploying BlazeDS on WebSphere should be the same as deploying any war file/web application. You could try deploying the samples webapp on your WebSphere server and run some of the samples. If that works then you know there is a problem with how you have your application configured. I would also try turning on client side and server side debugging for BlazeDS and seeing if the debug output tells you anything useful.
Can you give me any more information on how you have deployed BlazeDS and how you are running/loading your application? Is your application/swf being loaded from your BlazeDS web application or do you have it deployed locally or on another server?
If the swf isn't deployed on the BlazeDS web application, it's possible you are running into security
restrictions imposed by the flash player and need to add a cross domain policy file to your web server but without more information about how you have things configured I can't tell if that's your problem.
-Alex
View/reply at
configuring blazeds with websphere
Replies by email are OK.
Use the
unsubscribe form to cancel your email subscription.

OIM installation with WebSphere

I am trying to install OIM 9.1.0.1 on WebShpere 6.1.0.19
This Webshpere comes as bundle pack with Websphere portal server .
I tried many time but never worked out.
Dashboard shows every thing fine but OIM console cannot let xelsysadm user login .
I can login into websphere with xelsysadm user.
Please help me on this.

I did a websphere based project back in 2006 and I remember that some bundlings of Websphere (i.e. Websphere express) did not have all the components that OIM needs to work.
Have you tried installing OIM on the websphere version that is supported according to the release notes?
Best regards
/Martin

Need help startng websphere server in eclipse for debugging porpose

I am using Eclipse Sdk Version: 3.1.2
IBM websphere 6.0
JDK 1.4
I set debug value to "true" in my application.xml
I have a .ear file of my application deployed on the websphere appserver. Currently I can test my application in nobebug mode.
values of environment variables are -
JAVA_HOME - C:\DEV\IBMJDK142; C:\Program Files\Java\jre1.6.0_03
PATH - C:\DEV\IBMJDK142\bin; C:\Program Files\IBM\WebSphere MQ\Java\lib;C:\DEV\IBMJDK142\bin;%SystemRoot%\system32;%SystemRoot%;
I want to test the application in debug mode.
I am using default server on websphere, which is server1.
In Admin-console of webshere I went to
server-->Application server-->choose server1-->Debugging Service ---->checked the checkbox "Enable service at server startup"
Here value of my JVM debug port is 7777.
next In Eclipse env I chose Run---->Debug....--->Remote Java Application ----> created a new application with the name of my application and set the connection properties to -
Host - localhost
port-7777
Eclipse----> Windows----->Preferences---->Server----->Installed Runtime---->Add---->selected values such as -
JRE - default JRE(JDK 1.4)
IBM Websphere Installation Directory - C:/DEV/WebSphere/AppServer
saved it.
Now in debug perspective, I created a new server with selection/values such as -
IBM--->IBM Websphere v6---->
port - 9081
server profile directory - C:/DEV/WebSphere/AppServer/profiles/default
cell - GCWSNTRANode01Cell
node - GCWSNTRANode01
server - server1
Next---->Added the project to configured project ----->FINISH
Closed Eclipse to save env settings.
Started the default server (server1)
opened eclipse - desired project--->debug perspective ---->choose server--->Right Click----Start/Debug
mesg "Starting ServerI BM Websphere 6 - IBM Websphere 6 failed to start"
can some one please tell me what I am missing here.

Need help startng websphere server in eclipse for debugging porpose
can some one please tell me what I am missing here. Well for one, you're trying to debug a dolphin
Edited by: redfalconf35 on Jun 19, 2008 4:50 PM

J2ee agent 2.2 configuration problem with Websphere Portal 5.1

Hi,
I am trying to configure j2ee agent 2.2 with Websphere Portal server.
I have followed the document "Sun Java SystemAccess Manager
PolicyAgent 2.2 Guide for IBM WebSphere Portal Server 5.1.0.2"
Please see the thread "Problem with Sun's SSO system and Websphere Portal Server integration" for environment related information.
Also the security on app server has been enabled and is talking to LDAP.
My aim here is to enable application server (portal server) to autheticate requests.
I am getting following error when I log into the portal application.
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmFilter: now processing: SSO Task Handler
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
SSOTaskHandler: SSO Validation failed for null
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
javax.net.ssl.SSLHandshakeException: unknown certificate
     at com.ibm.jsse.bs.a(Unknown Source)
     at com.ibm.jsse.bs.startHandshake(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
     at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
     at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
URLFailoverHelper: disconnected the connection for availability check
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
ERROR: URLFailoverHelper: No URL is available at this time
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: No URL is available at this time
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmFilter: result =>
FilterResult:
     Status      : FORBIDDEN
     RedirectURL     : null
     RequestHelper:
          null
     Data:
          null
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmIdentityAsserter: result => TAIResult: status: 403, principal: null, subject: null
From whatever analysis I have done so far, I believe this issue is related to the personal certificate for sun one webserver (on which access manager & LDAP are installed) not registered with the application server (portal server).
I am not sure about the way I go by solving the issue.
Please can anybody help me out.
Thanks,
Yaseer
Message was edited by:
yazee
Message was edited by:
yazee

Ankush,
I am getting error as follows in the webserver error log:-
Error receiving request from 172.23.213.75 (SSL_ERROR_CERTIFICATE_UNKNOWN_ALERT: SSL peer had some unspecified issue with the certificate it received)
Although I can get into am console but with https://apollo.maxnewyorklife.com/amconsole
Tried the same thing, but couldnt resolve it. I will give it another go.
Generally I am getting same error again and again.
In my amWebsphere log file of j2ee agent (under root\am_wps_agent\agent_001\logs\debug) error I get.....
07/15/2007 04:19:11:656 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
AmFilter: now processing: SSO Task Handler
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
SSOTokenValidator.validate(): Exception caught
com.iplanet.sso.SSOException: Invalid sessionid formatjava.lang.IllegalArgumentException: Invalid server id in session id com.iplanet.services.naming.ServerEntryNotFoundException: Naming Service is not available.
     at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:205)
     at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:325)
     at com.sun.identity.agents.common.SSOTokenValidator.validateInternal(SSOTokenValidator.java:252)
     at com.sun.identity.agents.common.SSOTokenValidator.validate(SSOTokenValidator.java:157)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:88)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
SSOTaskHandler: SSO Validation failed for AQIC5wM2LY4SfcwoaNKFd01DvjYeNPbR3wXaa9sMVjcKtwo=@AAJTSQACMDE=#
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: No trusted certificate found
     at com.ibm.jsse2.bw.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.v.a(Unknown Source)
     at com.ibm.jsse2.v.a(Unknown Source)
     at com.ibm.jsse2.u.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.bx.l(Unknown Source)
     at com.ibm.jsse2.bx.startHandshake(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
     at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
     at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
Caused by: com.ibm.jsse2.util.g: No trusted certificate found
     at com.ibm.jsse2.util.f.b(Unknown Source)
     at com.ibm.jsse2.util.f.b(Unknown Source)
     at com.ibm.jsse2.util.d.a(Unknown Source)
     at com.ibm.jsse2.bn.checkServerTrusted(Unknown Source)
     at com.ibm.jsse2.z.checkServerTrusted(Unknown Source)
     ... 39 more
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
URLFailoverHelper: disconnected the connection for availability check
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
ERROR: URLFailoverHelper: No URL is available at this time
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: No URL is available at this time
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
Thanks,
Yaseer

How to config AM agent with websphere app server which binded http server??

Hi, thanks for your concern.
I am configuing AM policy agent with websphere 6.0 application server , the difference to the normal situation is : the IBM application server is binding with IBM http server so the server can deal with request from the port 80. It puzzled me much what shall I do when I installing the agent, the following are the questions:
1. Enter the Instance Config Directory: -- shall i use the config folder for "server1" or "webserver1"?
2. Enter the Server Instance name. -- shall i use the "server1" or "webserver1"?
3. Enter the preferred port number on which the application server provides its services: -- shall i use "80"(web server) or "9080"(app server) ,
4. Enter the preferred port number on which the application server provides its services: -- yes i should fill "/agentapp" here, but when i deploy this application, the web module should be "webserver1" or "server1"?
And yet I only need SSO here , what is the easiest way to configue them well? I do not want to obey the contents from DOC, at fact it makes my websphere crashed ... I think maybe I can use "filter" for application only after I installed the agent, is that right? but it make me crazy that, websphere told me it can not find the class javax.servlet.Filter ... I copied one for it ,but it still can not work. I think maybe I make wrong configuration before .
Is the document "Sun Java SystemAccess Manager PolicyAgent 2.2 Guide for IBM WebSphereApplication Server 6.0" only for stand alone application server?
Any help will be most appriciated! thank you!

If you are trying to install j2ee Agent 2.2 then the below answers may be helpful. i am not sure what webserver1 is ?
Remeber all config for j2ee agent is for the app server.
1. Enter the Instance Config Directory: -- shall i use the config folder for "server1" or "webserver1"? You should be using the 1 which your app server is using. The server.xml will be modified for the corresponding server instance.
2. Enter the Server Instance name. -- shall i use the "server1" or "webserver1"? depends on above config
3. Enter the preferred port number on which the application server provides its services: -- shall i use "80"(web server) or "9080"(app server) , for j2ee agent ot should be 9080
4. Enter the preferred port number on which the application server provides its services: -- yes i should fill "/agentapp" here, but when i deploy this application, the web module should be "webserver1" or "server1"?it should be ur app server port.
And yet I only need SSO here , what is the easiest way to configue them well? try sso_only mode
I do not want to obey the contents from DOC, at fact it makes my websphere crashed ... I think maybe I can use "filter" for application only after I installed the agent, is that right? without the agent filter in the web.xml the agent wont intercept any traffic.
but it make me crazy that, websphere told me it can not find the class javax.servlet.Filter ... I copied one for it ,but it still can not work. I think maybe I make wrong configuration before .
Is the document "Sun Java SystemAccess Manager PolicyAgent 2.2 Guide for IBM WebSphereApplication Server 6.0" only for stand alone application server?
Follow the SUN Docs strictly and it should work fine.

Urgent Requirement : Java Web Developer with Websphere Portal : CA

The Strategic Technologies Software Engineer - Advanced
Job Title Software Engineer - Advanced
Location : CA
Description:
     This Advanced Web Developer position will be a development team that is enhancing the feature set on the corporate intranet, IBM portal based system.
     Responsible for designing, developing and unit test components in a highly iterative and agile manner.
     Responsible for Design and Development of JSR168 portlets, servlets, JSPs and deploying the same to IBM WebSphere Environment. Ability to understand Themes, Personalization, SSO and integrate portlets.
     Responsible for writing Data access components using plain Java/JDBC and as well as using technologies like Spring and Hibernate
     Ability to quickly learn and come up to speed in a new environment and follow standards.
     Aside from solid web development skills, the candidate filling this position must have experience with test driven develop (TDD) techniques and have the demeanor and communication skills required for pair programming.
     Responsible for coordinating with team members to achieve desired results and possible mentoring of Junior programmers whenever there is a need.
     Proactively identifying issues in the development and bring up the same to the attention of tech lead or management attention at the very early stages. Ability to learn from team mates and solving issues quickly with the help of more knowledgeable team mates in that technology
     Strong experience in JSR 168 compliant, portlet design and development, preferably in a IBM portal environment 2 to 4 years
     Strong experience with Java, J2EE web application design, development of servlets, jsps, JSTL and good understanding of MVC framework minimum 4 years
     Strong experience in coding unit tests with JUNIT
     Experience with Javascript , html, XML and CSS in support of web application development
     Experience with design and development of data access component in Java with SQL knowledge
     Experience using IDEs like Eclipse , RAD and application servers like IBM Websphere Application Server
     Must have good communication skills both verbally and in written form and the ability to work independently with minimal guidance and as a member of a team. Education: A computer science college degree or equivalent experience.
Must have:
     8 years Java web development skills and excellent understanding of object-oriented analysis / design / programming.
5 years:
     Deep understanding of web application design / web security
     Good understanding of Model-View controller distributed architectures.
     Experience with Websphere Studio Application Developer (Eclipse)
     Experience with Service Oriented Architecture (SOA)
     OO Analysis and Design experience.
     Experience with the scrum agile development methodology, including TDD and JUNIT.
Hands-on experience with IBM's Websphere Portal is required.
If it interest you, please send your updated resume with your contact details ASAP at [email protected].
Regards,
Ejaz
Symphony Enterprises LLC
412-250-7227 (Tel) | 412-774-9230 (Fax)
IT Staffing | Training |
VERTICALS | Banking, Finance, Insurance | Healthcare | Manufacturing | Retail & Distribution
[email protected] | www.symphonyenterprises.com
WMBE & NWBE Certified Company
A Member of Women's Business Enterprise National Council (WBENC)
and National Association of Women Business Owners (NAWBO)

I'm getting the same error on WebSphere 6.1.5. Is there any solution for this?

HELP with WebSphere MQ

Similar Messages

Maybe you are looking for