Integration of ALBPM 5.7 with WebLogic 9.2 ::: Error

Hi All,
We are trying to configure ALBPM5.7 Enterprise Edition(with Weblogic) and WebLogic 9.2 Server. We have followed one particular document which states the use of Oracle as a Server.i.e ALBPM_5-7_WebLogic_9-2_Installation.pdf
But we are using MS-SQL Server. We are also using Merlia.jar as a JDBC Driver.
Now the issue is, we reach @ the end of the document by installing the jar file named "fuegoj2ee-lib-all.jar" through WebConsole. But we are getting stuck while installing the EAR file through Webconsole. Actually this file is neccessary to start the ALBPM 5.7 Engine to run.
We get "Direcory Service could not be reached" on DOMAIN console.
We are need and seeking a solution for the same.
Thanks
Shail

Hi.
We have tested the configuration of the engine. Its says "Directory Service has been found". So there is no issue of the directory service being null as such.
This is the domain log ------->
weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Too many connections :3
     at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:241)
     at weblogic.jdbc.jts.Driver.newConnection(Driver.java:918)
     at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:340)
     at weblogic.jdbc.jts.Driver.connect(Driver.java:181)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:82)
     at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:59)
     at fuego.connector.impl.RemoteJDBCConnector.getResource(RemoteJDBCConnector.java:129)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:280)
     at fuego.connector.JDBCHelper.getConnection(JDBCHelper.java:43)
     at fuego.directory.provider.jdbc.j2ee.RemoteJDBCConnectionProvider.getEntry(RemoteJDBCConnectionProvider.java:60)
     at fuego.directory.provider.jdbc.JDBCPersistenceManager.getConnection(JDBCPersistenceManager.java:552)
     at fuego.directory.provider.jdbc.JDBCPersistenceManager.checkConnectivity(JDBCPersistenceManager.java:120)
     at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:163)
     at fuego.directory.provider.Factory.startSession(Factory.java:488)
     at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:167)
     at fuego.directory.Directory.startSession(Directory.java:674)
     at fuego.ejbengine.Engine.initDirectorySession(Engine.java:335)
     at fuego.ejbengine.Engine.start(Engine.java:120)
     at fuego.ejbengine.servlet.SchedulerServlet.init(SchedulerServlet.java:107)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:278)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1715)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1692)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1612)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2750)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
We have large of active connections available on the MS SQL Server.
Awaiting Reply.
Thanks
Shail.

Similar Messages

Integration of Commons Logging framework with Weblogic

Hi,
We are trying to use Apache commons logging framework and trying to publish log mesages in Weblogic so that messages can be seen through console and all the Logging configurations can be managed from Admin console. I tried using the below steps:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/logging/config_logs.html#using_commons
But these does not seems to be working for User defined handlers. I am able to see the logs in the default odl-handler file but not able to log the messages through the handlers defined by me.
Can anyone help me on this.
Regards,
Anuj

Hi,
We are able to see reports through Workspace. We are facing problem after
integrating Hyperion Interactive Reporting with Weblogic Portal. we are able to see the sections like Query,Report,Results but we are not able to see the content after selecting any one of the section mentioned above.
System Configuration:
Hyperion Interactive Reporting 9.3.1
App Server: Weblogic server 9.2
Web Server: Apache 2.0.52
Database: Oracle 9.0.1.
Operating System: Windows 2003 with SP1
Browser: I.E 6.0
With Workspace everything is working fine. After Integration we are facing problem.
Regards,
S.Suresh.

OAM (10.1.4.3) Integration with WebLogic App Server (10.3.0 or below)

Hi All,
Can I use OAM 10.1.4.3 (Authentication Provider & Identity Asserter) to implement SSO with weblogic App Server 10.3.0 or below?
OAM 10.1.4.3 Authentication Provider & Identity Asserter is the recommended way to configure SSO with Web Logic App server 10.3.1 ( Oracle Middleware 11g).
And
OAM 10.1.4.2 uses WebLogic SSPI to configure SSO between OAM 10g and WebLogic App Server 10.3.0 or below.

Hi,
This is how the integration goes with different versions of WLS and OAM.
There is oamAuthnProvider.jar available with OAM 10.1.4.3 downloads. So it provides the assertion functionality.
Can I use OAM 10.1.4.3 (Authentication Provider & Identity Asserter) to implement SSO with weblogic App Server 10.3.0 or below?
Mahendra: Yes
OAM 10.1.4.3 Authentication Provider & Identity Asserter is the recommended way to configure SSO with Web Logic App server 10.3.1 ( Oracle Middleware 11g).
Mahendra: Yes, this is the recommended and easy approach.
OAM 10.1.4.2 uses WebLogic SSPI to configure SSO between OAM 10g and WebLogic App Server 10.3.0 or below.
Mahendra: Yes, older version of OAM uses SSPI connector installation.
HTH.
Mahendra.

Issue while integrating external LDAP with weblogic

Hi,
i am trying integrating external LDAP (OpenLdap) with weblogic 10.3. I created a provider and provided required credentials and able to see users and group of the LDAP into the weblogic console. I am also able to login in the weblogic console with the users available in the LDAP after assigning the admin role to the ldap group. But i when i see the user's property (by clicking on the user in the admin console) it only shows the tabs for General, Password and Group only. on the other hand if i see the users from DefaultAuthenticator, it shows the Attribute tab apart from the General, Password and Group.
Can anyone let me knwo how can we get the Attribute tab for the Ldap users.
thx,
Ajay

Hi Ajay
By default Weblogic has READ ONLY adapters for any External Security Providers that are configured like any AD Providers. READ ONLY means, you can only read the data from the ldap but not modify it, hence may be its not showing the Attributes tag. For Default Authenticator, see the first paragraph note in Attributes tab, that says the same thing. NOW, may be WLS can atleast show Attributes in READ only format, but it needs some sort of mappings to be defined. Say on Weblogic side, we have like firstName, lastName which on any typical AD will be like sn (surname = lastname), givenname (firstname) etc etc. This mapping is tough to generalize.
One thing for sure is, from Weblogic you cannot modify or edit any attributes for any user in external AD. If you really want to get those attributes, you may need to use some javax.ldap apis or some 3rd party ready to use tools/apis. I remember Weblogic Portal has a facility to configure a xml file that defines attributes mapping and get all attributes for any user. But again thats in Weblogic Portal product and not part of weblogic server.
If you have any SOA Software, they have some utilities for the same.
Thanks
Ravi Jegga

QUESTION Re. Integrating TIBCO EMS with Weblogic 8.1 using MDB

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

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

Any kind of integration experience with Weblogic JMS and Oracle AQ?

Hi,
In my company I work with java developers who believe in some kind of "holly" database independence I don't understand and as a result my life as a database developer is hell on earth.. Yesterday we again started to discuss, this time where to log, they believe database is slow and prefer logging to filesystem, after some hours finally I could convince them for some operational and reporting needs to use the database and will do this in an asyncronous way whiich they won't get slow. After all I believe the reason for a database is data, this is the place where data lives, and with the correct desing and implementation logging to database would perform better.
I love Oracle features, and know that we paid a lot for this software, so today I started investigating this promised solution. And quickly I found AQ and JMS topics in the documentation :)
After this introduction here is my problem; my company use BEA Weblogic as application server and the java guys want AQ to automatically (but of course with some delay) take their JMS log requests into database tables. Does any one have similar application experience, or any kind of integration experience with Weblogic JMS and Oracle AQ?
Any comments, references, documentation, sample code, url will be most welcomed :)
Thank you very much!
Tonguc
[email protected]
References I found upto now;
Oracle® Streams Advanced Queuing Java API Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14291/toc.htm
(Packages; javax.jms & oracle.jms)
Oracle® Streams Advanced Queuing User's Guide and Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14257/toc.htm
Part IV
Using Oracle JMS and Oracle Streams AQPart V describes how to use Oracle JMS and Oracle Streams Advanced Queuing (AQ).
Chapter 11, "Introducing Oracle JMS"
Chapter 12, "Oracle JMS Basic Operations"
Chapter 13, "Oracle JMS Point-to-Point"
Chapter 14, "Oracle JMS Publish/Subscribe"
Chapter 15, "Oracle JMS Shared Interfaces"
Chapter 16, "Oracle JMS Types Examples"
A Sample Code from Otn
http://www.oracle.com/technology/sample_code/tech/java/web_services/jmsws/NewsQueueEJB.java.html

I wouldn't go as far to say Oracle AQ is out-dated today. However, it is indeed a proprietary technology that did not found much main-stream adoption in the earlier years after its introduction. The advent of JMS made it somewhat more useful (or should I say intriguing, because more people are trying to tie it together with other J2EE technologies), but the Oracle's JMS wrapper classes in aqapi.jar were not feature complete for a long while, so using it outside Oracle's application server was painful, if not impossible. I do agree that the info at the dev2dev's JMS newsgroup or in this forum is highly fragmented, as neither Oracle nor BEA provides an official solution to integrate AQ with WebLogic, so people like us have to learn the technology through experimentation and in a piecemeal fashion.
3 years ago I was literally "playing around" - we had a polling mechanism set up to use triggers to write Oracle data changes into an event table, and had a Java-based daemon to scan that table and publish events as JMS messages to the WebLogic JMS server. This continues to work reliably till today, but I was looking for a solution that has few parts - I wanted to hook up my WebLogic MDB directly to AQ as a foreign JMS provider. Although I was able to get it to work (including XA), there were a few hoops I had to jump through, such as decompiling the Oracle AQjms classes to make them bind to the WebLogic JNDI tree.
One year after that Diptanshu Parui took what I did a giant step further - he extended the Oracle AQjms classes to allow them to be bound to the WebLogic JNDI tree naturally, and he figured out how to use WebLogic JMS messging bridge to re-send single-threaded AQ JMS messages to clustered JMS queues, which allow concurrent message assumption by multiple instances of MDB's. My impression is that he is using that setup in a production environment.
I am sure you are aware of it but I would like to make it clear - in order to use AQ as a foreign JMS provider to WebLogic-hosted MDB's, you don't need to update your database to Oracle 10g - Oracle 8i is good enough (although I recommend at least 9i Release 2). It is not the database engine, but rather the aqapi.jar JMS wrapper on top of AQ that matters. I do recommend that you use aqapi.jar from Oracle Application Server 10.0.3 or up for better XA support, among other things. Again, you don't have to replace WebLogic with Oracle AS - you only need a single jar file from it and put it in your WebLogic's classpath. However, I don't know what this means from a licensing point of view if you ever go to production - do you have to pay the full price of OracleAS or OC4J just to use the aqapi.jar?
In the coming days I will test the latest aqapi.jar to see how much progress Oracle has made in terms of making their J2EE products more spec-compliant :-).
Hope the above gives you a different perspective.
Eric

Problem integrating JProbe 4.0 with Weblogic 4.5.1

I'm trying to integrate JProbe 4.0 with Weblogic 4.5.1. JProbe
doesn't provide an integration for this version of Weblogic so I have
to do the set up by hand. We are running Weblogic with a 1.3 JVM on
Solaris.
First problem is that the JVM we were using wasn't supported by
JProbe. So I swapped to a different version. The application,
consisting of about 150 EJBs plus JSPs and Servlets works fine with
this JVM. When I run with JProbe, JProbe waits for the console
connection then Weblogic starts. About half way through deploying all
the EJBs the application stops. I've done a thread dump and it
doesn't seem to be a deadlock. Looking at the JProbe console I can
see that objects are getting allocated and GC'd in the typical saw
tooth fashion indicating that things are still running. I've waited
15 minutes but the application does not progress beyond this point.
Any got any ideas about this or tips as to how I can debug things
further?
tia
David

Hi David,
You could try to turn off memory debugging along with
putting the debug environment into a big fat box. With
memory debugging on JProbe is slooooow...
Regards,
Slava Imeshev
"David Off" <[email protected]> wrote in message
news:[email protected]..
I'm trying to integrate JProbe 4.0 with Weblogic 4.5.1. JProbe
doesn't provide an integration for this version of Weblogic so I have
to do the set up by hand. We are running Weblogic with a 1.3 JVM on
Solaris.
First problem is that the JVM we were using wasn't supported by
JProbe. So I swapped to a different version. The application,
consisting of about 150 EJBs plus JSPs and Servlets works fine with
this JVM. When I run with JProbe, JProbe waits for the console
connection then Weblogic starts. About half way through deploying all
the EJBs the application stops. I've done a thread dump and it
doesn't seem to be a deadlock. Looking at the JProbe console I can
see that objects are getting allocated and GC'd in the typical saw
tooth fashion indicating that things are still running. I've waited
15 minutes but the application does not progress beyond this point.
Any got any ideas about this or tips as to how I can debug things
further?
tia
David

Iplanet Integration with weblogic

Dear All,
We want to integrate IPlanet with weblogic application server.
Please suggest the procedure for the same i.e docs , URLs.
Thanks
Prashant

kindly take a look at our reverse proxy plugin
http://docs.sun.com/app/docs/doc/819-0902
also, please note that if you need to serve only servlet / jsp , then sun java system web server 6.1 has integrated container that can do the job very well.
for any further business process logic , you can use the app servers with 'reverse proxy enabled' so that these requested can be forwards to either Sun Java System Application Server or Web Logic
thanks
sriram.

Has anyone integrated Netegrity with WebLogic ?

Hello:
Has anyone integrated Netegrity's SiteMinder with WebLogic ? I am curious to
see how well it integrates and if there are any 'real world' experiences.
Thanks.
-Sunil .K

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

IBM Cognos 8 BI Integration with Weblogic portal

Hi,
In our project we need to integrate IBM Cognos 8 BI portlets with Weblogic portal 10.3.
1. How to integrate Cognos ?
2. How to enable SSO between Portals & Cognos? Cognos should use the portal users credentials for authentication
Please share me some useful links and sample code to proceed.
Thanks & regards,
Rajesh

Basically I am saying that your options are
1. Screenscraping the apps into portlets
2. Using SSO to login to the apps, but keepin them separate
3. Using Web Services to consume parts of the apps and exposing those as portlets
For our application we do 2 and 3. In many cases we just create portlets that represents views into other j2ee apps. When the users click on something, we launch the j2ee app in a popup browser. The users are already signed on, and taken to a specific detail page, add page or something within the app directly.
Hope this helps.
Kunal

How to Integrating Microsoft MapPoint Webservice with Weblogic Workshop 9.2

I have to integrate the MapPoint Webservice with Weblogic Workshop 9.2. But while analyzing the WSDL i m getting the error.
The error which I m getting is :
An error was encountered while analyzing the WSDL:null jName
Detail:
com.bea.wlw.controls.service.ui.except.TypesAnalysisFailedException: java.lang.IllegalArgumentException: null jName at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.<init>(SelectSCInfoPage.java:127)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.getPageList(GenerateSCWizard.java:150)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.addPages(GenerateSCWizard.java:136)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:499)
at org.eclipse.jface.window.Window.create(Window.java:418)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:996)
at org.eclipse.jface.window.Window.open(Window.java:776)
at com.bea.wlw.controls.service.ui.actions.NewSCGenAction.run(NewSCGenAction.java:101)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.IllegalArgumentException: null jName at com.bea.staxb.buildtime.internal.bts.BindingTypeName.<init>(BindingTypeName.java:51)
at com.bea.staxb.buildtime.internal.bts.BindingTypeName.forPair(BindingTypeName.java:40)
at com.bea.staxb.buildtime.Schema2Java.createBindingType(Schema2Java.java:766)
at com.bea.staxb.buildtime.Schema2Java.bind(Schema2Java.java:363)
at com.bea.staxb.buildtime.Schema2Java.internalBind(Schema2Java.java:301)
at com.bea.staxb.buildtime.BindingCompiler.bind(BindingCompiler.java:125)
at weblogic.wsee.bind.buildtime.internal.XmlBeansBaseBindingsBuilderImpl.createBuildtimeBindings(XmlBeansBaseBindingsBuilderImpl.java:159)
at weblogic.wsee.tools.source.EndpointBuilder.setupBindingProviderWithServices(EndpointBuilder.java:836)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBindingProvider(ClientGenUtil.java:458)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBuildtimeBindings(ClientGenUtil.java:211)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBuildtimeBindings(ClientGenUtil.java:174)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadBuildtimeBindings(BindingsClassNameReference.java:228)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getBindings(BindingsClassNameReference.java:161)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadJsService(BindingsClassNameReference.java:307)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getJsService(BindingsClassNameReference.java:362)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadTypeNamesForService(BindingsClassNameReference.java:398)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getTypeNamesForService(BindingsClassNameReference.java:383)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeNamesForService(BindingsCheckUtility.java:210)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingTypeInfoForService(BindingsCheckUtility.java:131)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingInfoForServiceByBindingsDataSourceType(BindingsCheckUtility.java:104)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.initializeTypesForTheService(BindingsCheckUtility.java:253)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.findMatchingBindingsDataSources(BindingsCheckUtility.java:434)
at com.bea.wlw.controls.service.ui.util.BindingsChecker.<init>(BindingsChecker.java:55)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.checkForCompatibleBindings(SelectSCInfoPage.java:304)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.<init>(SelectSCInfoPage.java:98)
... 31 more

Plz find the WSDL file's text below :
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://s.mappoint.net/mappoint-30/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://s.mappoint.net/mappoint-30/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://s.mappoint.net/mappoint-30/">
<s:element name="GetVersionInfo">
<s:complexType />
</s:element>
<s:element name="GetVersionInfoResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetVersionInfoResult" type="tns:ArrayOfVersionInfo" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="ArrayOfVersionInfo">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="VersionInfo" nillable="true" type="tns:VersionInfo" />
</s:sequence>
</s:complexType>
<s:complexType name="VersionInfo">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Component" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Version" type="s:string" />
</s:sequence>
</s:complexType>
<s:element name="CustomerInfoHeader" type="tns:CustomerInfoHeader" />
<s:complexType name="CustomerInfoHeader">
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="CustomLogEntry" type="s:short" />
</s:sequence>
</s:complexType>
<s:element name="UserInfoHeader" type="tns:UserInfoHeader" />
<s:complexType name="UserInfoHeader">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Culture" type="tns:CultureInfo" />
<s:element minOccurs="1" maxOccurs="1" name="DefaultDistanceUnit" type="tns:DistanceUnit" />
<s:element minOccurs="0" maxOccurs="1" name="Context" type="tns:CountryRegionContext" />
</s:sequence>
</s:complexType>
<s:complexType name="CultureInfo">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
<s:element minOccurs="1" maxOccurs="1" name="Lcid" type="s:int" />
</s:sequence>
</s:complexType>
<s:simpleType name="DistanceUnit">
<s:restriction base="s:string">
<s:enumeration value="Kilometer" />
<s:enumeration value="Mile" />
</s:restriction>
</s:simpleType>
<s:complexType name="CountryRegionContext">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" default="0" name="EntityID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="Iso2" type="s:string" />
</s:sequence>
</s:complexType>
<s:element name="GetCountryRegionInfo">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="entityIDs" type="tns:ArrayOfInt" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="ArrayOfInt">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="int" type="s:int" />
</s:sequence>
</s:complexType>
<s:element name="GetCountryRegionInfoResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetCountryRegionInfoResult" type="tns:ArrayOfCountryRegionInfo" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="ArrayOfCountryRegionInfo">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="CountryRegionInfo" nillable="true" type="tns:CountryRegionInfo" />
</s:sequence>
</s:complexType>
<s:complexType name="CountryRegionInfo">
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="EntityID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="LatLong" type="tns:LatLong" />
<s:element minOccurs="0" maxOccurs="1" name="Iso2" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Iso3" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="FriendlyName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="OfficialName" type="s:string" />
</s:sequence>
</s:complexType>
<s:complexType name="LatLong">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" default="0" name="Latitude" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="0" name="Longitude" type="s:double" />
</s:sequence>
</s:complexType>
<s:element name="GetEntityTypes">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="dataSourceName" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="GetEntityTypesResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetEntityTypesResult" type="tns:ArrayOfEntityType" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="ArrayOfEntityType">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="EntityType" nillable="true" type="tns:EntityType" />
</s:sequence>
</s:complexType>
<s:complexType name="EntityType">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="DisplayName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="ParentName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Definition" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Properties" type="tns:ArrayOfEntityProperty" />
</s:sequence>
</s:complexType>
<s:complexType name="ArrayOfEntityProperty">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="Property" nillable="true" type="tns:EntityProperty" />
</s:sequence>
</s:complexType>
<s:complexType name="EntityProperty">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="DisplayName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="DataType" type="s:string" />
</s:sequence>
</s:complexType>
<s:element name="GetDataSourceInfo">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="dataSourceNames" type="tns:ArrayOfString" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="ArrayOfString">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="string" nillable="true" type="s:string" />
</s:sequence>
</s:complexType>
<s:element name="GetDataSourceInfoResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetDataSourceInfoResult" type="tns:ArrayOfDataSource" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="ArrayOfDataSource">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="DataSource" nillable="true" type="tns:DataSource" />
</s:sequence>
</s:complexType>
<s:complexType name="DataSource">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Version" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Description" type="s:string" />
<s:element minOccurs="1" maxOccurs="1" name="Capability" type="tns:DataSourceCapability" />
<s:element minOccurs="0" maxOccurs="1" name="EntityExtent" type="tns:ArrayOfInt" />
</s:sequence>
</s:complexType>
<s:simpleType name="DataSourceCapability">
<s:list>
<s:simpleType>
<s:restriction base="s:string">
<s:enumeration value="CanDrawMaps" />
<s:enumeration value="CanFindPlaces" />
<s:enumeration value="CanFindNearby" />
<s:enumeration value="CanRoute" />
<s:enumeration value="CanFindAddress" />
<s:enumeration value="HasIcons" />
<s:enumeration value="DataServiceQuery" />
</s:restriction>
</s:simpleType>
</s:list>
</s:simpleType>
<s:element name="GetGreatCircleDistances">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="latLongs" type="tns:ArrayOfLatLong" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="ArrayOfLatLong">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="LatLong" nillable="true" type="tns:LatLong" />
</s:sequence>
</s:complexType>
<s:element name="GetGreatCircleDistancesResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetGreatCircleDistancesResult" type="tns:ArrayOfDouble" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="ArrayOfDouble">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="double" type="s:double" />
</s:sequence>
</s:complexType>
<s:element name="Find">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="specification" type="tns:FindSpecification" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="FindSpecification">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DataSourceName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="InputPlace" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="EntityTypeNames" type="tns:ArrayOfString" />
<s:element minOccurs="0" maxOccurs="1" name="Options" type="tns:FindOptions" />
</s:sequence>
</s:complexType>
<s:complexType name="FindOptions">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Range" type="tns:FindRange" />
<s:element minOccurs="1" maxOccurs="1" name="SearchContext" type="s:int" />
<s:element minOccurs="1" maxOccurs="1" name="ResultMask" type="tns:FindResultMask" />
<s:element minOccurs="0" maxOccurs="1" default="0.85" name="ThresholdScore" type="s:double" />
</s:sequence>
</s:complexType>
<s:complexType name="FindRange">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" default="0" name="StartIndex" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" default="25" name="Count" type="s:int" />
</s:sequence>
</s:complexType>
<s:simpleType name="FindResultMask">
<s:list>
<s:simpleType>
<s:restriction base="s:string">
<s:enumeration value="LatLongFlag" />
<s:enumeration value="EntityFlag" />
<s:enumeration value="AddressFlag" />
<s:enumeration value="BestMapViewFlag" />
<s:enumeration value="MatchDetailsFlag" />
</s:restriction>
</s:simpleType>
</s:list>
</s:simpleType>
<s:element name="FindResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="FindResult" type="tns:FindResults" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="FindResults">
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="NumberFound" type="s:int" />
<s:element minOccurs="1" maxOccurs="1" name="StartIndex" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="Results" type="tns:ArrayOfFindResult" />
<s:element minOccurs="1" maxOccurs="1" name="TopScore" type="s:double" />
</s:sequence>
</s:complexType>
<s:complexType name="ArrayOfFindResult">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="FindResult" nillable="true" type="tns:FindResult" />
</s:sequence>
</s:complexType>
<s:complexType name="FindResult">
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="Score" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" name="FoundLocation" type="tns:Location" />
</s:sequence>
</s:complexType>
<s:complexType name="Location">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="LatLong" type="tns:LatLong" />
<s:element minOccurs="0" maxOccurs="1" name="Entity" type="tns:Entity" />
<s:element minOccurs="0" maxOccurs="1" name="Address" type="tns:Address" />
<s:element minOccurs="0" maxOccurs="1" name="BestMapView" type="tns:MapViewRepresentations" />
<s:element minOccurs="0" maxOccurs="1" name="DataSourceName" type="s:string" />
</s:sequence>
</s:complexType>
<s:complexType name="Entity">
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="ID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="DisplayName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="TypeName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Properties" type="tns:ArrayOfEntityPropertyValue" />
</s:sequence>
</s:complexType>
<s:complexType name="ArrayOfEntityPropertyValue">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="Property" nillable="true" type="tns:EntityPropertyValue" />
</s:sequence>
</s:complexType>
<s:complexType name="EntityPropertyValue">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Value" />
</s:sequence>
</s:complexType>
<s:complexType name="Address">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddressLine" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="PrimaryCity" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="SecondaryCity" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Subdivision" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="PostalCode" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="CountryRegion" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="FormattedAddress" type="s:string" />
</s:sequence>
</s:complexType>
<s:complexType name="MapViewRepresentations">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ByScale" type="tns:ViewByScale" />
<s:element minOccurs="0" maxOccurs="1" name="ByHeightWidth" type="tns:ViewByHeightWidth" />
<s:element minOccurs="0" maxOccurs="1" name="ByBoundingRectangle" type="tns:ViewByBoundingRectangle" />
</s:sequence>
</s:complexType>
<s:complexType name="ViewByScale">
<s:complexContent mixed="false">
<s:extension base="tns:MapView">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" default="0" name="MapScale" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" name="CenterPoint" type="tns:LatLong" />
</s:sequence>
</s:extension>
</s:complexContent>
</s:complexType>
<s:complexType name="MapView" abstract="true" />
<s:complexType name="ViewByBoundingLocations">
<s:complexContent mixed="false">
<s:extension base="tns:MapView">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Locations" type="tns:ArrayOfLocation" />
</s:sequence>
</s:extension>
</s:complexContent>
</s:complexType>
<s:complexType name="ArrayOfLocation">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="Location" nillable="true" type="tns:Location" />
</s:sequence>
</s:complexType>
<s:complexType name="ViewByHeightWidth">
<s:complexContent mixed="false">
<s:extension base="tns:MapView">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" default="0" name="Height" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="0" name="Width" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" name="CenterPoint" type="tns:LatLong" />
</s:sequence>
</s:extension>
</s:complexContent>
</s:complexType>
<s:complexType name="ViewByBoundingRectangle">
<s:complexContent mixed="false">
<s:extension base="tns:MapView">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="BoundingRectangle" type="tns:LatLongRectangle" />
</s:sequence>
</s:extension>
</s:complexContent>
</s:complexType>
<s:complexType name="LatLongRectangle">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Southwest" type="tns:LatLong" />
<s:element minOccurs="0" maxOccurs="1" name="Northeast" type="tns:LatLong" />
</s:sequence>
</s:complexType>
<s:complexType name="MapPointConstants">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" default="6378.2" name="EarthRadiusInKilometers" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="3.1415926535897931" name="Pi" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="0.017453292519943295" name="RadiansPerDegree" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="57.295779513082323" name="DegreesPerRadian" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="0.621371192237334" name="MilesPerKilometer" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="1.609344" name="KilometersPerMile" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="0.0003048" name="KilometersPerFoot" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="3280.8398950131232" name="FeetPerKilometer" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="0.85" name="FindScoreThreshold" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="96" name="AssumedDpi" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" default="3.280839895013123" name="FeetPerMeter" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" default="0.3048" name="MetersPerFoot" type="s:double" />
</s:sequence>
</s:complexType>
<s:complexType name="SpatialFilter" abstract="true" />
<s:complexType name="LatLongSpatialFilter">
<s:complexContent mixed="false">
<s:extension base="tns:SpatialFilter">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="LatLong" type="tns:LatLong" />
</s:sequence>
</s:extension>
</s:complexContent>
</s:complexType>
<s:complexType name="LatLongRectangleSpatialFilter">
<s:complexContent mixed="false">
<s:extension base="tns:SpatialFilter">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="BoundingRectangle" type="tns:LatLongRectangle" />
<s:element minOccurs="1" maxOccurs="1" name="PolygonRectangleRelation" type="tns:SpatialRelation" />
</s:sequence>
</s:extension>
</s:complexContent>
</s:complexType>
<s:simpleType name="SpatialRelation">
<s:restriction base="s:string">
<s:enumeration value="WithinArea" />
<s:enumeration value="TouchesArea" />
</s:restriction>
</s:simpleType>
<s:element name="CustomerInfoFindHeader" type="tns:CustomerInfoFindHeader" />
<s:complexType name="CustomerInfoFindHeader">
<s:complexContent mixed="false">
<s:extension base="tns:CustomerInfoHeader" />
</s:complexContent>
</s:complexType>
<s:element name="UserInfoFindHeader" type="tns:UserInfoFindHeader" />
<s:complexType name="UserInfoFindHeader">
<s:complexContent mixed="false">
<s:extension base="tns:UserInfoHeader" />
</s:complexContent>
</s:complexType>
<s:element name="FindAddress">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="specification" type="tns:FindAddressSpecification" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="FindAddressSpecification">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DataSourceName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="InputAddress" type="tns:Address" />
<s:element minOccurs="0" maxOccurs="1" name="Options" type="tns:FindOptions" />
</s:sequence>
</s:complexType>
<s:element name="FindAddressResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="FindAddressResult" type="tns:FindResults" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ParseAddress">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="inputAddress" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="countryRegion" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ParseAddressResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ParseAddressResult" type="tns:Address" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="GetLocationInfo">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="location" type="tns:LatLong" />
<s:element minOccurs="0" maxOccurs="1" name="dataSourceName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="options" type="tns:GetInfoOptions" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="GetInfoOptions">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" default="true" name="IncludeAddresses" type="s:boolean" />
<s:element minOccurs="0" maxOccurs="1" default="true" name="IncludeAllEntityTypes" type="s:boolean" />
<s:element minOccurs="0" maxOccurs="1" name="EntityTypesToReturn" type="tns:ArrayOfString" />
</s:sequence>
</s:complexType>
<s:element name="GetLocationInfoResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetLocationInfoResult" type="tns:ArrayOfLocation" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="FindNearby">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="specification" type="tns:FindNearbySpecification" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="FindNearbySpecification">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DataSourceName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="LatLong" type="tns:LatLong" />
<s:element minOccurs="1" maxOccurs="1" name="Distance" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" name="Filter" type="tns:FindFilter" />
<s:element minOccurs="0" maxOccurs="1" name="Options" type="tns:FindOptions" />
</s:sequence>
</s:complexType>
<s:complexType name="FindFilter">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="EntityTypeName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="PropertyNames" type="tns:ArrayOfString" />
<s:element minOccurs="0" maxOccurs="1" name="WhereClause" type="tns:WhereClause" />
<s:element minOccurs="0" maxOccurs="1" name="SortProperties" type="tns:ArrayOfSortProperty" />
<s:element minOccurs="0" maxOccurs="1" name="Expression" type="tns:FilterExpression" />
</s:sequence>
</s:complexType>
<s:complexType name="WhereClause">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="SearchProperties" type="tns:ArrayOfEntityPropertyValue" />
<s:element minOccurs="1" maxOccurs="1" name="SearchOperator" type="tns:SearchOperatorFlag" />
</s:sequence>
</s:complexType>
<s:simpleType name="SearchOperatorFlag">
<s:restriction base="s:string">
<s:enumeration value="And" />
<s:enumeration value="Or" />
</s:restriction>
</s:simpleType>
<s:complexType name="ArrayOfSortProperty">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="SortProperty" nillable="true" type="tns:SortProperty" />
</s:sequence>
</s:complexType>
<s:complexType name="SortProperty">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="PropertyName" type="s:string" />
<s:element minOccurs="1" maxOccurs="1" name="Direction" type="tns:SortDirection" />
</s:sequence>
</s:complexType>
<s:simpleType name="SortDirection">
<s:restriction base="s:string">
<s:enumeration value="Ascending" />
<s:enumeration value="Descending" />
</s:restriction>
</s:simpleType>
<s:complexType name="FilterExpression">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Text" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Parameters" type="tns:ArrayOfAnyType" />
</s:sequence>
</s:complexType>
<s:complexType name="ArrayOfAnyType">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="anyType" nillable="true" />
</s:sequence>
</s:complexType>
<s:element name="FindNearbyResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="FindNearbyResult" type="tns:FindResults" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="FindByProperty">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="specification" type="tns:FindByPropertySpecification" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="FindByPropertySpecification">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DataSourceName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Filter" type="tns:FindFilter" />
<s:element minOccurs="0" maxOccurs="1" name="Options" type="tns:FindOptions" />
</s:sequence>
</s:complexType>
<s:element name="FindByPropertyResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="FindByPropertyResult" type="tns:FindResults" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="FindByID">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="specification" type="tns:FindByIDSpecification" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="FindByIDSpecification">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DataSourceName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Filter" type="tns:FindFilter" />
<s:element minOccurs="0" maxOccurs="1" name="Options" type="tns:FindOptions" />
<s:element minOccurs="0" maxOccurs="1" name="EntityIDs" type="tns:ArrayOfInt" />
</s:sequence>
</s:complexType>
<s:element name="FindByIDResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="FindByIDResult" type="tns:FindResults" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="FindNearRoute">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="specification" type="tns:FindNearRouteSpecification" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="FindNearRouteSpecification">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DataSourceName" type="s:string" />
<s:element minOccurs="1" maxOccurs="1" name="Distance" type="s:double" />
<s:element minOccurs="0" maxOccurs="1" name="Filter" type="tns:FindFilter" />
<s:element minOcc

Integrating Oracle BPM with WebLogic Portal

Can I integrate Oracle BPM standalone 10g with Weblogic Protal?
Must I use the BPM for Weblogic to integrate with Weblogic Protal or OSB.
According to the Configuration Guide, I cannot find the <ORABPM_standalone_HOME>/j2ee/weblogic/deployer

Hi All,
I am able to configure Oracle with Weblogic.
Thx.

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

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

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

AQ Adapter in 11g with weblogic

Hi all
I m looking to work on some sample AQ adapter in 11g with weblogic. is it possible?
if any one provide some light on this? some examples please?
thanks
Srikanth

Does the example from the guide doesnt work for you ?
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10231/adptr_aq.htm
Oracle AQ Adapter Use Cases

Data dependent routing with WebLogic

How do you do data dependent routing with WebLogic Platform? Does it require additional
products or can it be done just using WebLogic Platform components?
Thanks

WLI, or "WebLogic Integrator" may be what you are looking for, this is a
          full fledged message-flow/routing product built on top of JMS.
          If your needs are simple, you can roll-your-own data dependent routing
          using the WebLogic server built-ins of JMS, which provides reliable
          messaging, in combination with MDBs and/or Messaging Bridges - both of
          which allow the specification JMS selectors (filters). Furthermore,
          your MDB application can enqueue to a specific local destination (or a
          remote one, which is harder) based on the contents of the message it
          receives. Voila.
          For example, WorkQ (local or remote) --> MDB --> JobQ1 or JobQ2 or
          JobQ3. To simplify the MDB logic, JobQs could be on the same server,
          and therefore always available. (This is one of the advantages of
          having a JMS that can run in the same JVM as the app server, the other
          is very fast performance.)
          Tom
          David B wrote:
          > How do you do data dependent routing with WebLogic Platform? Does it require additional
          > products or can it be done just using WebLogic Platform components?
          >
          > Thanks

Integration of ALBPM 5.7 with WebLogic 9.2 ::: Error

Similar Messages

Maybe you are looking for