Does weblogic suppports nested Schema ComplexType and BTP.

hi,
in unsupported features they have mentioned "XML Schema complex data type inheritance
by restriction ", what inheritance means here(is it nested complex types.)
and in latest white paper "Web Services and the BEA Weblogic E-Business Platform"
in the heading "The BEA Difference" have mentioned for transaction support.does
any one has tried this feature or have some sample example.
regards,
Jainendra

Hi,
I'm assuming the paper you are speaking about is:
http://www.bea.com/products/weblogic/server/paper_webservices.shtml
It speaks specifically about: "BEA WebLogic Integration™ - This open and extensible
product integrates trading partners across the Web and enables complex Web Services to be
deployed with transactional integrity, security, and reliability while supporting the
emerging ebXML and BTP standards. BEA WebLogic Integration builds on simple Web Services
to offer the more sophisticated services required for complex B2B commerce and
integration."
Check out the documentation for this product:
http://e-docs.bea.com/wlintegration/v2_1/index.html
Hope this helps,
Bruce
Jainendra wrote:
hi,
in unsupported features they have mentioned "XML Schema complex data type inheritance
by restriction ", what inheritance means here(is it nested complex types.)
and in latest white paper "Web Services and the BEA Weblogic E-Business Platform"
in the heading "The BEA Difference" have mentioned for transaction support.does
any one has tried this feature or have some sample example.
regards,
Jainendra

Similar Messages

Does Weblogic server 8.1 support "LIMIT and OFFSET" in EJB QL?

hi,
Can any one tell me does 8.1 server support "limit" and "offset" keywords in EJB-QL?
I tried to define a finder method in the workshop with the following syntax:
@ejbgen:finder ejb-ql="SELECT OBJECT(o) from EmpBean OFFSET ?1 LIMIT ?2" generate-on="Local" signature="Collection findEmp(java.lang.Integer st,java.lang.Integer en)"
I get the following error
ERROR: ERROR: Error from ejbc: [EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was:
ERROR: Query:
 EJB Name: EmpBean
 Method Name: findEmp
 Parameter Types: (java.lang.Integer, java.lang.Integer)
SELECT OBJECT(o) from EmpBean OFFSET =>> 1 <<= LIMIT 2
EJB QL Parser Error.
39: unexpected token: 1
What am I doing wrong?
thanks

I could not find any documentation that suggested LIMIT or OFFSET where supported. Some of our developers needed to use limit, in the end all I could suggest was using a dynamic query and setting the maximum number of results see here
.

Hussein Badakhchani

WebLogic 11g EAR EJB Classpath and class loaders

All,
I have been having issues migrating Spring based EJB applications from OC4J to WebLogic 11g (10.3.1). I have been in communication with Oracle who has suggested a work around however I am keen to see if anyone else can suggest a solution.
The application is dependant on stateless session EJB beans that communicate with a Spring managed service tier to perform the business logic and database access. PitchFork is used to inject the Spring managers into the EJB’s using the spring-ejb-jar.xml configuration file. Note originally I was using the SpringBeanAutowiringInterceptor however I could not get this to work. See WebLogic 11g and Spring beens injected into EJB for details.
When the application is deployed packaging all the dependant jars within the APP-INF\lib folder I get a verity of errors from the following InvalidClassException, NoSuchMethodError, AbstractMethodError and IllegalArgumentException. I am using Spring 2.5.3 to match the supported WebLogic version. Note within the EAR application.xml the library-directory is set to APP-INF/lib. The issue appears to be Spring, PitchFork, commons-logging and aspectj libraries are being loaded form WebLogic and do not have visibility on jars within the application or have been modified when bundled for WebLogic. An example of this is the PitchFork jar within WebLogic has been changed excluding the spi package resulting in java.lang.ClassNotFoundException: org.springframework.jee.spi.PitchforkUtilsImpl errors.
Moving the jars to the domain library path does not resolve any of the issues. I have been unable to successfully deploy the application picking up the application jars using the prefer-application-packages configuration.
Oracle has advised me to deploy the libraries into the WebLogic system classpath by modifying the startWebLogic command to load the libraries into the classpath. I am concerned that modifying the system classpath will result in an unstable WebLogic server as I will be replacing modified jar files packages with WebLogic (such as PitchFork). This will also limit the applications that can be deployed within the server as each application must use the same libraries and versions (as the application ibraries are leing ignored).
Has anyone else hit this issue and corrected it? Can anyone think of an alternative solution?
Regards
Neil

Hi,
I am in the process of updating the tracking bug# 331569 with copies of the eclipse EAR/WAR projects and the EAR for these scenarios. Here are some details on how I got past the 2nd CCE on the org.eclipse.persistence.jpa.PersistenceProvider class (not the javax one)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=331569
Essentially an SE persistence unit running both JPA 2.0 api and the 2.0 XSD schema work fine. I will next retest the EE case with variations of the 3 types of injection on the SSB or Servlet.
Update: There are 3 (possibly 4) issues here (all of these may become obsolete when the next WLS version ships)Initially I got the same 2.0 schema error and the ClassCastException on org.eclipse.persistence.jpa.PersistenceProvider
It turns out that my import of the 2 eclipse projects from my bug # 296271 for WebLogic 10.3.2.0 lost their facets(specifically the dynamic web facet) because I associated them with a different WebLogic 10.3.3.0. - this caused the CCE I was experiencing like Sri.
Anyways, after creating an EAR/Web project combination from scratch in eclipse associated with the 10.3.3.0 instance - I predeployed/deployed/ran fine - even with the 2.0 schema - in SE bootstrap mode (no EE yet).
Reproduction Procedure:
redoing project from scratch as I noticed that the war was not at the root of the ear - it was a jar in the app-inf/lib dir - my imported eclipse project was not referenced correctly as a web module facet- create empty EAR and WAR project with references
- download and open my EAR and WAR project code from bug # 296271
https://bugs.eclipse.org/bugs/show_bug.cgi?id=296271
- do essentially all the steps in the page below (I paraphrase for re-verification)
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#DI_1.1:_Alternative_3:_Application_Level_Shared_Library_-InUse
- copy applicationService, entity and FrontController servlet code into new projects
- create persistence.xml and MANIFEST.MF manifest in src\META-INF
- update manifest
Class-Path: APP-INF/lib/eclipselink.jar
APP-INF/lib/javax.persistence_2.0.0.v200911041116.jar
- copy both javax.persistence 2.0 and eclipselink 2.x jars to APP-INF/lib
- change ordering of WebLogic library modules classpath reference (javax.persistence 1.0) to ear reference (2.0 version)
- update web.xml with servlet tags
- update weblogic.xml with new context root
- make the persistence unit name the same in persistence.xml and ApplicationManagedService
- update weblogic-application.xml with prefer-application-packages overrides
<wls:prefer-application-packages>
<wls:package-name>javax.persistence.*</wls:package-name>
<wls:package-name>org.eclipse.persistence.*</wls:package-name>
</wls:prefer-application-packages>
- enable server redirect logging

<property name="eclipselink.logging.logger" value="DefaultLogger"/>
- start WebLogic 10.3.3.0
- deploy (run on) server from eclipse or export ear to auto deploy directory
1) JPA 2.0 XSD usage on 10.3.3.0
- I reproduced this issue with a bad EAR
- was able to use the 2.0 schema within the WAR-only application managed EAR
persistence.xml<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">

<persistence-unit name="example2" transaction-type="JTA">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>localJTA</jta-data-source>
<class>org.eclipse.persistence.example.business.Cell</class>
<shared-cache-mode>NONE</shared-cache-mode>
<properties>
<property name="eclipselink.target-server" value="WebLogic_10"/>
<property name="eclipselink.logging.level" value="FINEST"/>
<property name="eclipselink.target-database" value="Derby"/>

<property name="eclipselink.logging.logger" value="DefaultLogger"/>



</properties>
</persistence-unit>
</persistence>
2) CCE on JPA provider implementation class
Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit example2: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider
- I reproduced and fixed this one (was Eclipse project facet issue) - EAR was wrong
- was able to run JPA 2.0 code fine on an SE PU (predeploy/deploy together)
- EE injection should not work but I will post an example EAR anyway
log[EL Example]: enterprise: JPA 2.0 Metamodel: MetamodelImpl@56287508 [ 3 Types: , 1 ManagedTypes: , 1 EntityTypes: , 0 MappedSuperclassTypes: , 0 EmbeddableTypes: ]
3) CCE on JPA spec interface class
- I could not reproduce this one
Re: WebLogic 11g EAR EJB Classpath and class loaders
Error processing persistence unit PT of module pt: Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit PT: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider cannot be cast to javax.persistence.spi.PersistenceProvider
4) CCE on fallback Kodo JPA provider (if an invalid say 2.1 JPA XSD schema is referenced)
java.lang.ClassCastException: kodo.persistence.PersistenceProviderImpl
at javax.persistence.Persistence.findAllProviders(Persistence.java:186)
java.lang.NoSuchMethodError: javax/persistence/EntityManager.getMetamodel()Ljavax/persistence/metamodel/Metamodel;
- reproduced by using the 1.0 javax.persistence jar (but named as the 2.0 one in APP-INF/lib)
- fixed by using either the 1.0 or 2.0 JPA XSD schema and using the correct 2.0 spec jar
thank you
/michael

"Source File does not match XML Schema"

Using MDM 5.5 SP4 Patch 2 (Build 5.5.34.26) on a 32-bit system (WinServer 2003, Enterprise Edition SP1.
This source file and schema have been verified by SAP Tech Support and again using Altova XML Spy. The schema was loaded into MDM through the console and the source file was successfully mapped against it and the data manually imported into MDM. The customer record was then cleansed using the Data Manager and the import map was used to create an inbound port. However, when the Import Server goes to import the file using the map, the following error is dropped into the log: "Source File does not match XML Schema". Has anyone else seen this error?
Thanks, Don
IMPORT LOG ENTRY:
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="MDM_Log.xsl"?>
<MDM_Log version="1.0" path="H:PROGRA~1SAPMDM~1.5IMPORT~1TempMDIS_TASK@@U@[email protected]"
>
 <Open ts-long="18:24:35 GMT, Saturday, February 03, 2007" ts="2007/02/03 18:24:35.108 GMT" pid="8640" host="bp1tulap452" compile-type="RELEASE_32">
 <Trace ts="2007/02/03 18:24:35.249 GMT" tid="7216" entry-no="3">[BP US FUELS CUSTOMER MASTER] Import Task Started. Chunk size[50000], No. parallel chunks[1]</Trace>
 <Trace ts="2007/02/03 18:24:43.890 GMT" tid="5980" entry-no="11">xSaxParser: Starting.</Trace>
 <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="19">xSaxParser: Ending.</Trace>
 <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="20">Source file does not conform to XML Schema!<LINE-FEED/></Trace>
 <Trace ts="2007/02/03 18:24:45.312 GMT" tid="7216" entry-no="29">[RESPOSITORY]Import Task Finished. Chunk size[50000], No. parallel chunks[1]</Trace>
 </Open>
</MDM_Log>
SOURCE FILE:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:CustomerCreateResp xmlns:ns1="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100">
- <CUSTOMER>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<MDMCUSTOMER>2463</MDMCUSTOMER>
<CREATE_DATE>22/01/2007,11:43:49</CREATE_DATE>
- <RETURN>
<TYPE />
<MESSAGE />
</RETURN>
- <PT_CONTPART_RETURN>
- <item>
<MDM_CONTACT>0000000001</MDM_CONTACT>
<CONTACT>0001111119</CONTACT>
</item>
- <item>
<MDM_CONTACT>0000000004</MDM_CONTACT>
<CONTACT>0002222229</CONTACT>
</item>
</PT_CONTPART_RETURN>
- <PARTNERS>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<PARTNER_FUNCTION>RE</PARTNER_FUNCTION>
<PARTNER_NUMBER>0001333329</PARTNER_NUMBER>
<DEFAULT_PARTNER>X</DEFAULT_PARTNER>
</item>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<PARTNER_FUNCTION>WE</PARTNER_FUNCTION>
<PARTNER_NUMBER>0001555559</PARTNER_NUMBER>
<DEFAULT_PARTNER />
</item>
</PARTNERS>
</item>
</CUSTOMER>
</ns1:CustomerCreateResp>
SCHEMA:
 <?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" targetNamespace="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" elementFormDefault="unqualified">
<xsd:element name="CustomerCreateResp" type="CustomerCreateResp" />
- <xsd:complexType name="CustomerCreateResp">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">682cc2d0aa6e11db9b800015c5888624</xsd:appinfo>
</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="CUSTOMER">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f68988f0a02e11db94bb00166f98336c</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b20a75811dba9d400166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b21a75811db9c4800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="MDMCUSTOMER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b22a75811dbcbac00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="CREATE_DATE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b23a75811dbcc0300166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="RETURN" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b24a75811db8d5500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="TYPE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b25a75811db876d00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="MESSAGE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b26a75811db85c400166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="PT_CONTPART_RETURN" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b27a75811db8ca900166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b28a75811dbaae100166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="MDM_CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b29a75811dbaade00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2aa75811dbc24c00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="PARTNERS" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ba75811dbb74500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ca75811db9f6500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2da75811db9bd800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="PARTNER_FUNCTION" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ea75811dbb84100166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="PARTNER_NUMBER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2fa75811db852800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="DEFAULT_PARTNER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b30a75811db968400166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

You have to define the namespace in the URI field of XML Schmea in Console.
In MDM Console,
Admin -> XML Schemas -> Create XML Schema
You have to specify the namespace urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100 in the URI property.
Please update this post if fixed your problem.

Not able to download Weblogic Server 10.3.5 and ATG 10.3.2 for 64 bit window

Hi
For past two days I am trying to download Weblogic Server 10.3.5 and ATG 10.3.2 for 64 bit window but the download stops after downloading 30 or 40 MB and once I got network error. I dont know whats the issue. I even disabled my antivirus and firewall, still no luck. Any help is appreciated.
Thanks.

I hope you are using following link to download the Oracle WebLogic Server 10.3.5
http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html
Oracle recommends to use Download manager. Download Managers can help if you are having trouble connecting, completing a download, or wish to queue up several files for unattended downloading. While Oracle does not provide or certify the use of any Download Managers, we recommend choosing one that is rated for the file size you are downloading and ensuring that it allows cookies to be passed to the download server.
Or you can also request Oracle to ship DVDs, please use following MOS notes to follow the process.
My Oracle Support Doc ID 1071023.1 ‘Requesting Physical Shipment or Download URL for Software Media'.

Weblogic 8.1 App Server and IBM MQ Series 5.2 Issue

Hi All,
 I am trying to create a bridge between Weblogic 8.1 App Server and IBM MQ Series 5.2 and i am facing issues.
 Bridge works fine if i use QualityOfService="Atmost-once" and i am getting following error when i use
 QualityOfService="Duplicate-okay".
 Error:
 <Oct 16, 2003 6:03:35 PM PDT> <Error> <MessagingBridge> <BEA-200015> <An error occurred in bridge "MQSeries WebLogic Bridge" during the transfer of messages (java.lang.Exception: weblogic.jms.adapter.JMSConnectionHandle.acknowledge(Ljavax/jms/MessageV).>
 <Oct 16, 2003 6:03:35 PM PDT> <Warning> <MessagingBridge> <BEA-200026> <Bridge "MQSeries WebLogic Bridge" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.bridge.internal.MessagingBridgeException.)>
 Any suggestions or comments will be really appreciated.
 Thanks
 Suresh


It is weird that nothing shows up in the log after you turned on the debug.
 Actually I knew somebody has run into the same problem once.
 The problem disappeared after he did something on the MQSeries side (like
 restart the system and something else). I did not know exactly what he did.
 I am not sure if that will help you but worth trying.
 If that does work either, I'd suggest that you contact the BEA Customer Support
 and somebody will look at it for you in depth.
 Thanks,
 Dongbo
 Suresh wrote:
 > Thanks for following up on this.
 >
 > This bridge works with 6.1 app server and we are trying to use the same stuff
 > for 8.1 app server too. No, we are not using XAConnectionFactory.
 >
 > Suresh
 >
 > Dongbo Xiao <[email protected]> wrote:
 > >Is there any chance that the JMS connection factory on the MQSeries
 > >side is a XAConnectionFactory?
 > >
 > >Suresh wrote:
 > >
 > >> I am using the debug options (-Dweblogic.Debug.DebugMessagingBridgeStartup="true"
 > >> -Dweblogic.Debug.DebugMessagingBridgeRuntime="true") in my stratip
 > >script,
 > >> but, thats the maximum stack trace I can get. I am using jms-notran-adp.rar
 > >for
 > >> both QOS. Bridge is working fine when I use Exactly-once and repeatedly
 > >getting
 > >> the same message when I use Duplicate_okay. My destination queue is
 > >not able to
 > >> ackowledge the messge to the sender.
 > >>
 > >> Here I am giving nodes from my config.xml
 > >>
 > >> <MessagingBridge AsyncEnabled="false" BatchInterval="40000"
 > >> Name="MQSeries WebLogic Bridge"
 > >> QualityOfService="Duplicate-okay"
 > >> SourceDestination="MQSeries Inbound Destination" Started="true"
 > >> TargetDestination="WebLogic Inbound Destination" Targets="myserver"/>
 > >> <JMSBridgeDestination
 > >> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDINoTX"
 > >> ConnectionFactoryJNDIName="jms.InboundMessageConnectionFactory"
 > >> ConnectionURL="t3://myserver:7001"
 > >> DestinationJNDIName="jms.InboundMessageQueue"
 > >> DestinationType="Queue"
 > >> InitialContextFactory="weblogic.jndi.WLInitialContextFactory"
 > >> Name="WebLogic Inbound Destination" UserName="username" UserPassword="pwd"/>
 > >> <JMSBridgeDestination
 > >> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDINoTX"
 > >> ConnectionFactoryJNDIName="cn=MQ_BROKER_1,ou=inboundConnectionFactories,ou=mqseries,ou=jms,ou=Systems"
 > >> ConnectionURL="ldap://ldapServer:389/o=myroot"
 > >> DestinationJNDIName="cn=queue2,ou=queue,ou=mqseries,ou=jms,ou=Systems"
 > >> InitialContextFactory="com.sun.jndi.ldap.LdapCtxFactory"
 > >> Name="MQSeries Inbound Destination"
 > >> UserName="cn=admin,o=myroot" UserPassword="pwd"/>
 > >> <Application Name="jms-notran-adp"
 > >> Path="C:\bea\weblogic81\server\lib" StagingMode="nostage" TwoPhase="true">
 > >> <ConnectorComponent Name="jms-notran-adp"
 > >> Targets="rdoddapaneni3" URI="jms-notran-adp.rar"/>
 > >> </Application>
 > >>
 > >> Thanks
 > >>
 > >> Tom Barnes <[email protected]> wrote:
 > >> >By the way, if you are looking to improve performance, transactional
 > >> >mode may actually be the fastest. See the JMS Performance
 > >> >Guide white-paper on dev2dev for details.
 > >> >
 > >> >Suresh wrote:
 > >> >
 > >> >> Hi All,
 > >> >>
 > >> >> I am trying to create a bridge between Weblogic 8.1 App Server and
 > >> >IBM MQ Series 5.2 and i am facing issues.
 > >> >>
 > >> >> Bridge works fine if i use QualityOfService="Atmost-once" and i
 > >am
 > >> >getting following error when i use
 > >> >> QualityOfService="Duplicate-okay".
 > >> >>
 > >> >> Error:
 > >> >>
 > >> >> <Oct 16, 2003 6:03:35 PM PDT> <Error> <MessagingBridge> <BEA-200015>
 > >> ><An error occurred in bridge "MQSeries WebLogic Bridge" during the
 > >transfer
 > >> >of messages (java.lang.Exception: weblogic.jms.adapter.JMSConnectionHandle.acknowledge(Ljavax/jms/MessageV).>
 > >> >
 > >> >> <Oct 16, 2003 6:03:35 PM PDT> <Warning> <MessagingBridge> <BEA-200026>
 > >> ><Bridge "MQSeries WebLogic Bridge" encountered some problems in one
 > >> >of its adapters or underlying systems. It stopped transferring messages
 > >> >and will try to reconnect to the adapters shortly. (The exception
 > >caught
 > >> >was weblogic.jms.bridge.internal.MessagingBridgeException.)>
 > >> >>
 > >> >> Any suggestions or comments will be really appreciated.
 > >> >>
 > >> >> Thanks
 > >> >> Suresh
 > >> >
 > >

Need to know schema name and table name associated with a column-URGENT

Hi folks,
I need to know the schema name and the table name associated with a column. Though jdbc has the api to getTableName and getSchemaName, some database vendor like oracle does return empty upon call of mentioned methods. I found that oracle driver does not support that
Can any one give me the solution? It is urgent. Or do you suggest any third pary jdbc driver which can provide those?
Thanks
Angelina

Angelina,
Your question has been discussed several times previously in this forum. Search this forum's archives for "getTableName". Oracle JDBC driver does not implement this (because "it is not feasible" -- according to Oracle).
First of all, I would suggest that you could probably change your application's logic so that you would not need this functionality (but I guess that is not feasible either, right :-)
Alternatively, you could try querying the Oracle database data dictionary.
Good Luck,
Avi.

How does WebLogic 8.1 get the BASE HREF value?

We have a WebLogic 8.1 SP4 server with a Juniper DX load balancer in front. We are trying to get Juniper to handle all the SSL traffic for the WebLogic application. Between Juniper and WebLogic, it would be just HTTP and between Juniper and web clients it would be HTTPS. One of the main issues we are seeing is that Struts HTML:BASE tag is returning the Juniper address as we expected, with the correct SSL port and application context/paths. However, the protocol for this base href is set to HTTP and not HTTPS. Consequently, our pages do not load properly.
I am trying to understand where this value comes from. The underlying code uses request.getScheme() to get the protocol. So, we could "customize" the tags to work around this, but that is a hack that I am trying to avoid. I assume that the HTTP stack that WebLogic 8.1 uses is providing this info from the HTTP request. Does this come from the web browser? How does WebLogic get this to put it into the request object in the web container? We have sniffed the HTTP headers on the web client side and we cannot see where this is coming from.

I remember facing a similar issue with webloigc 8.1 and apache
I dont think its a problem with the tag..
I think i have changed the transport-guarantee in web.xml
If you have NONE try setting that to CONFIDENTIAL and vice versa

Which DDL does Weblogic use?

How does weblogic determine which DDL to use when creating JMS persistent store?

How does weblogic determine which DDL to use when          > creating JMS persistent store?
          The DDL is stored in the weblogic.jar, and a particular DDL is chosen automically based on driver meta-data.
          Version 9.0 (out in beta), provides the option of administratively configuring the DDL file location.
          For unsupported drivers, versions prior to 9.0 require manually running a DDL file to create the JDBC store's backing tables (see JMS doc).
          Tom Barnes, BEA

How does WebLogic clean up stuck threads?

Hi,
Using WebLogic 9.2.2 on Linux OS. In our logs, we are finding some stuck threads and it seems to be due to something WebLogic is doing. While we don't understand the cause (maybe the stack trace helps), does WebLogic do anything to remove stuck threads from its pool, or is there anything we can do to configure it to?
<Jul 21, 2009 2:50:21 PM UTC> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "605" seconds working on the request "Http Request: /RoutingEngine/pcFlow.do", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-69 "[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
jrockit.net.SocketNativeIO.readBytesPinned(Unknown Source)
jrockit.net.SocketNativeIO.socketRead(Unknown Source)
java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
java.net.SocketInputStream.read(SocketInputStream.java:107)
java.io.BufferedInputStream.fill(BufferedInputStream.java:189)
java.io.BufferedInputStream.read(BufferedInputStream.java:234)
^-- Holding lock: java.io.BufferedInputStream@3537712[thin lock]
weblogic.net.http.MessageHeader.isHTTP(MessageHeader.java:214)
weblogic.net.http.MessageHeader.parseHeader(MessageHeader.java:141)
weblogic.net.http.HttpClient.parseHTTP(HttpClient.java:473)
^-- Holding lock: java.io.BufferedInputStream@3537712[thin lock]
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:332)
^-- Holding lock: java.io.BufferedInputStream@3537712[thin lock]
weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:36)
weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:92)
weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:56)
weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
weblogic.wsee.wsdl.WsdlSchema.parse(WsdlSchema.java:120)
weblogic.wsee.wsdl.WsdlSchemaImport.parse(WsdlSchemaImport.java:55)
weblogic.wsee.wsdl.WsdlSchema.parse(WsdlSchema.java:82)
weblogic.wsee.wsdl.WsdlSchema.parse(WsdlSchema.java:62)
weblogic.wsee.wsdl.WsdlTypes.parse(WsdlTypes.java:145)
weblogic.wsee.wsdl.WsdlDefinitions.parseChild(WsdlDefinitions.java:452)
weblogic.wsee.wsdl.WsdlExtensible.parse(WsdlExtensible.java:84)
weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:378)
weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:358)
weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:50)
weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:437)
weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:95)
com.myco.regui.provisioning.client.ProvisioningAccountService_Impl.<init>(ProvisioningAccountService_Impl.java:21)
com.myco.regui.provisioning.client.ProvisioningAccountService_Impl.<init>(ProvisioningAccountService_Impl.java:17)
com.myco.regui.struts.accounts.AccountsForm.contactWPS(AccountsForm.java:208)
com.myco.regui.struts.accounts.AccountsForm.validateAccountid(AccountsForm.java:161)
com.myco.regui.struts.accounts.AccountsForm.validatePCAccountId(AccountsForm.java:144)
com.myco.regui.struts.accounts.AccountsForm._validatePCFields(AccountsForm.java:112)
com.myco.regui.struts.accounts.AccountsForm.validate(AccountsForm.java:83)
org.apache.struts.chain.commands.servlet.ValidateActionForm.validate(ValidateActionForm.java:57)
org.apache.struts.chain.commands.AbstractValidateActionForm.execute(AbstractValidateActionForm.java:94)
org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:48)
org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:176)
org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:303)
org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:176)
org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:272)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1903)
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
javax.servlet.http.HttpServlet.service(HttpServlet.java:736)
javax.servlet.http.HttpServlet.service(HttpServlet.java:851)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:224)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:198)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
com.myco.regui.servlets.filters.TransactionFilter.doFilter(TransactionFilter.java:23)
.......

You can configure these actions to occur when not all threads are stuck, but the number of stuck threads have exceeded a configured threshold:
* Shut down the Work Manager if it has stuck threads. A Work Manager that is shut down will refuse new work and reject existing work in
the queue by sending a rejection message. In a cluster, clustered clients will fail over to another cluster member.
* Shut down the application if there are stuck threads in the application. The application is shutdown by bringing it into admin mode. All
Work Managers belonging to the application are shut down, and behave as described above.
* Mark the server instance as failed and shut it down it down if there are stuck threads in the server. In a cluster, clustered clients that
are connected or attempting to connect will fail over to another cluster member.
Link : [http://e-docs.bea.com/wls/docs103/config_wls/overload.html]

Weblogic cluster for 24x7 environment and a front OHS server

Hi experts,
We are going to set up a reliable J2EE application server environment by using clustering webgoic servers on TWO nodes, and a front OHS https server in DMZ for load balancing.
I am new to weblogic cluster and load balance by OHS. I have visited this forum for Fusion MiddleWare clustering etc. Can some experts share some light on this?
Will our deployment architecture be able to handle the J2EE applications failover? In other word, we can restart one of Weblogic Managed Servers when a new release of J2EE codes are re-deployed without impacting business end users’s usage?
Problems we want to solve:
1. All J2EE applications are available for 24x7 even when new J2EE codes are released and deployed on weblogic Managed Servers ANY TIME, side-by-side deployment and restart a managed server if we need to clean the HTTP cache.
2. The J2EE applications should be accessed by external and internal users with a Single Access Point, like
https://apps.company1.com/j2ee1
https://apps.company2.com/j2ee1
https://apps.company1.com/j2ee2
https://apps.company2.com/j2ee2
All J2EE applications (j2ee1, j2ee2, j2ee3 etc) should be deployed on both of weblogic Servers in a cluster, and pointing to a SAME backend database.
Can some experts share with us the best practices on components and configurations? Thanks.

Seems your architecture is like Browser => OHS ( DMZ ) => Weblogic => DB OR Browser => HLB( like bigip ) => OHS ( DMZ ) => Weblogic => DB
Cluster is the solution for load balancing however if you are using OHS for redirection to weblogic then OHS does the load balancing in round robin way. using cluster in this way has a benefit of in case of any one of your managed server is down the OHS will divert connection request to any one of the active managed server ( you have to turn on dynamic list on at OHS ).
http://weblogicserveradministration.blogspot.com/2010/10/load-balancing-in-weblogic-server.html
Failover is something different, if in case any of the any managed server goes down then your user you get the application session from another server but new one, means the the tasks not saved by the users on earlier session will lost. for that yo need to use cluster and then need to enable the session replication. another best option is you can use the coherence web if you are using latest versions of weblogic supporting coherence web. with that you not need to worry on user sessions and you can start any of the managed server anytime without worrying about the user sessions.
http://weblogicserveradministration.blogspot.com/2010/10/manage-http-session-states-session.html
http://weblogicserveradministration.blogspot.com/2011/05/oracle-coherence-37-coherenceweb.html
http://weblogicserveradministration.blogspot.com/2010/11/clustering-part-i.html
another way is, you can use side by side deployment feature in case you don't want shutdown your application completely, with this, old connections and new requests will goes to old application and once new application activated all new requests will come to new application and once all requests on old application will complete that application will retire automatically.
Regards
Mukesh Negi
http://weblogicserveradministration.blogspot.com

Does Weblogic Server 5.1 supports RedHat Linux 6.2?

Hello All,
Does Weblogic Server 5.1 supports RedHat Linux 6.2?
Best Regards,
Samuel Yung
[email protected]

FYI.
I am running RH 6.2 and Weblogic 5.10 with no problems.
w/Apache 1.3.12
Only using WL for EJBs and jdbc pool at this time. So your milage may vary.
Michael Girdley wrote:
No, not yet. Version 6.0 will.
The platform support page for WebLogic Server is located at:
http://www.weblogic.com/platforms/index.html
This page has the latest and greatest information on the platforms that
WebLogic is certified and supported on.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Samuel Yung" <[email protected]> wrote in message
news:[email protected]..
Hello All,
Does Weblogic Server 5.1 supports RedHat Linux 6.2?
Best Regards,
Samuel Yung
[email protected]
/\/\i|<e
Mike Kincer
Solutions Developer/Engineer
Atlas Commerce "ebusiness evolved"
Office phone: +1-607-741-9988
mailto:[email protected] [http://www.atlascommerce.com]

Does Weblogic Server 5.1 supports RedHat Linux 7?

Does Weblogic Server 5.1 supports RedHat Linux 7?
Thanx in advance.

FYI.
I am running RH 6.2 and Weblogic 5.10 with no problems.
w/Apache 1.3.12
Only using WL for EJBs and jdbc pool at this time. So your milage may vary.
Michael Girdley wrote:
No, not yet. Version 6.0 will.
The platform support page for WebLogic Server is located at:
http://www.weblogic.com/platforms/index.html
This page has the latest and greatest information on the platforms that
WebLogic is certified and supported on.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Samuel Yung" <[email protected]> wrote in message
news:[email protected]..
Hello All,
Does Weblogic Server 5.1 supports RedHat Linux 6.2?
Best Regards,
Samuel Yung
[email protected]
/\/\i|<e
Mike Kincer
Solutions Developer/Engineer
Atlas Commerce "ebusiness evolved"
Office phone: +1-607-741-9988
mailto:[email protected] [http://www.atlascommerce.com]

[Java 7] Zip file system does not handle nested zip files

The ZIP FileSystem which is shipped as an extension with Java7 does not support nested ZIP files. I.e., you can open the outer zip file as a FileSystem, but if you try to open an inner zip as a FileSystem, you get this exception:
java.nio.file.ProviderNotFoundException: Provider not found
at java.nio.file.FileSystems.newFileSystem(FileSystems.java:403)Since the ZIP FileSystem is an extension, and not a part of the core JDK, I'm posting this here (and on Xueming's blog) in the hope that it will get resolved. It doesn't seem right to report it as a JDK bug.

872883 wrote:
The zip file system definitely allows zip entries to be read without extracting them first. And--based on reviewing the ZipFS source code that Oracle has included with the JDK--it doesn't appear to be silently extracting the data to a temporary file.you missed the point of what Peter Lawrey said. in order to create a ZipFS on a zip file, it must be a file in the first place (i.e. have random access). there is no way to do random access on an entry within an existing zip file, therefore in order to create a ZipFS on a nested zip file, you would first have to extract it to a file.

WSDL import does not import my schema file

I have a local WSDL that imports a schema. When I create a new partner link, I get the dialogue box that tells me it has to make a local copy. It makes the local copy. It still refers to my schema import (which has a relative path) but it does not move the schema as well.
Am I doing something wrong or is this a bug?
Thanks,
Greg

This is not exactly the behavior I am seeing.
This is what I see: Lets say that I have a WSDL file that resides in c:\mywsdls\pp-wsif.wsdl. It has an import statement in my wsdl for the schema types that is relative (../schema/schema.xsd). Lets also assume that my BPEL process project resides in c:\<BPEL_HOME>\mywork\bpelproj.
When I go to create a partner link using my local wsdl file, two wsdl files show up in my BPEL project. One is an exact copy of pp-wisf.wsdl and one is the pp-wisfRef.wsdl. The pp-wisfRef.wsdl has the partner link stuff and it also references the wsdl in c:\<BPEL_HOME>\mywork\bpelproj, not my original wsdl.
Now is when my problem comes up. the "new" pp-wisf.wsdl file still has that import with a relative path. But, since the wsdl file got moved and the xsd did not that relative path is no longer valid. Thus, my origial problem.
There is an obvious work around to edit my wsdls to fix the paths but I am wondorering if I am doing something wrong or if this is in fact a bug.
Greg

Does weblogic suppports nested Schema ComplexType and BTP.

Similar Messages

Maybe you are looking for