Deployment order of MDBs vs EJBs in WL startup sequence

          This is a problem that follows on from my last posting.
          To recap, we have multiple WL servers not clustered, one acts as the JMS server that
          all of them use as their MDB jndi-provider-url so when a message (on a JMS topic)
          is published to the main server, all the WL servers receive it.
          The main WL server acting as the JMS server is started up first, then the others.
          The following problem can occur.
          A message can arrive at the main server while another server is booting up. The MDBs
          on this booting server can deploy it's MDBs before it's EJBs. Because this server
          is subscribing using the JMS server on the main server, the message is delivered
          and the onMessage() method is called. But this method may have to do lookups on EJBs
          that have not been deployed yet.
          So the question is, is it possible to ensure that all the EJBs deploy before the
          MDBs in a WL startup sequence? Does it require two separate JAR files to control
          the order, or can you control the order within a JAR file or have you simply no control
          over the order at all?
          Regs,
          Paul

That's correct.
 "Paul Hammond" <[email protected]> wrote in message
 news:[email protected]...
 >
 > In my response to my own question I have seen in the WL docs that JMS
 servers are
 > deployed before EJB components, but within EJB components you can specify
 a deployment
 > order so presumably there by having separate JARs, one with EJBs, one with
 MDBs,
 > you can ensure your MDBs are deployed last?
 >
 > Paul
 >
 >
 >
 >
 > "Paul Hammond" <[email protected]> wrote:
 > >
 > >This is a problem that follows on from my last posting.
 > >
 > >To recap, we have multiple WL servers not clustered, one acts as the JMS
 > >server that
 > >all of them use as their MDB jndi-provider-url so when a message (on a
 JMS
 > >topic)
 > >is published to the main server, all the WL servers receive it.
 > >
 > >The main WL server acting as the JMS server is started up first, then the
 > >others.
 > >
 > >The following problem can occur.
 > >
 > >A message can arrive at the main server while another server is booting
 > >up. The MDBs
 > >on this booting server can deploy it's MDBs before it's EJBs. Because
 this
 > >server
 > >is subscribing using the JMS server on the main server, the message is
 delivered
 > >and the onMessage() method is called. But this method may have to do
 lookups
 > >on EJBs
 > >that have not been deployed yet.
 > >
 > >So the question is, is it possible to ensure that all the EJBs deploy
 before
 > >the
 > >MDBs in a WL startup sequence? Does it require two separate JAR files to
 > >control
 > >the order, or can you control the order within a JAR file or have you
 simply
 > >no control
 > >over the order at all?
 > >
 > >Regs,
 > >
 > >Paul
 > >
 >

Similar Messages

Deployment Order of modules.

Hi,
I have an en EAR that contains multiple jars and each jar contains multiple EJBs
and the jars depends each others (not circular).
that means that the deployment order of modules it's
very important so I won't get NoClassDefErrorFound.
How Can I set the modules deployment order ?, I know that for each of the jars
I can set the deployment order (in my case ejb deployment order) but what about
modules ?
Any help will be appreciated.
Haim

If I understand correctly, you're asking if there is any ordering of the jar files in WEB-INF/lib of a war file? ie if you have the same class in multiple jars files which one is first on the classpath?
AFAIK, this is undefined in the J2EE specs, and we don't guarantee any ordering.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Application deployment order with weblogic-ejb-jar.xml and jndi-name

I have two applicatation working on Weblogic server v. 10.3.6.
First of them creating one ejb stateless bean and creates JNDI maping for it (in weblogic-ejb-jar.xml file):
<weblogic-enterprise-bean>
 <ejb-name>ConfigMenegerBean</ejb-name>
 <stateless-session-descriptor>
 <stateless-session-descriptor>
 <business-interface-jndi-name-map>
 <business-remote>package.ConfigurationSessionRemote</business-remote>
 <jndi-name>ConfigMeneger</jndi-name>
 </business-interface-jndi-name-map>
 </stateless-session-descriptor>
 <enable-call-by-reference>true</enable-call-by-reference>
 <jndi-name>ConfigMeneger</jndi-name>
</weblogic-enterprise-bean>
Second appication have to refer for this bean by JNDI using spring been lookup :
<jee:jndi-lookup id="configManager" jndi-name="ConfigMeneger"/>
I changed deployment order parameter for both apllication(first=100 and second=500) in order to first app start first and share bean by jndi to another application. Unfortuantelly I got an error :
javax.naming.NameNotFoundException: Unable to resolve 'ConfigMeneger'. Resolved ''; remaining name 'ConfigMeneger'
How can I configure deployment order that first application make jndi mapping for bean, before the second application will use it ?

Ok in a way I have solved my problem (even if I am not completely satisfied by the way on how to proceed...). So thanks to message "JBuilder7.0 and Weblogic6.1" on EJB sun forum :
http://forum.java.sun.com/thread.jsp?thread=285735&forum=13&message=1255488
I have tried the following actions (mentionned in the other forum messages):
- To preserve changes to weblogic*.xml, the safest way is to change the ejb-borland.xml.
(I am not sure that I have applied this advice correctly, because I suppose that syntax is not similar in weblogic file or borland file).
And you can MANUALLY update the weblogic file in your JAR archive.
1. Open the EJB JAR file in Winzip and extract the weblogic-ejb-jar.xml file, so that a copy exists in your
project directory.
2. Open this file (in Notepad), add the WebLogic specific information, and then save the file.
3. Now, when you are finished with the build cycle and are ready to deploy, you may open the EJB jar file
and swap in the weblogic-ejb-jar.xml file."
Good Luck.

Deployement order of MDBs and SSBs

Hi All,
Facing the issue with deployment order of EJBs in one ear,
MDBs start reading and processing message before SSBs are initialised in JNDI while server startup.
And JNDI lookup for SSB from MDB failes JNDI lookup exception gets raised, failing the whole processing of message.
1) MDBs jar and SSBs jar are in one EAR, so deployment order attribute can't be specified in config.xml or thru admin console, as it is with an application.
2) Have tried <start-mdbs-with-application>false</start-mdbs-with-application> (even with true)
as per http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ejb/message_beans.html#wp1167264
but it doesn't work.
3) Now planning to use WL LifeCyclelistner and get server state = RUNNING, before starting to process the messages in MDB.
Anybody has any viable solution other than this?
Thanks & Regards,
Keyur

Hi Keyur,
Which version on weblogic are you using because its seems that this might be a bug and similar bug was seen in WLS-9.2 version more details are given below:
From the link below which you gave it states that
“Set to false to defer message processing until after WebLogic Server opens its listen port.”
Search for: start-mdbs-with-application
Link-1 http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ejb/message_beans.html#wp1167264
# Conclusion:
This means that “false” should have resolved your issue but it is not so this might be a bug. Similar bug was seen in WLS-9.2 version which was fixed in WLS-9.2 Mp-1 version check out the link below.
Search for: CR293982 or CR299012
Link-2 http://download.oracle.com/docs/cd/E13222_01/wls/docs92/issues/known_resolved.html
However if it was fixed in WLS 9.2 Mp-1 then the same issue is most probably taken care in WLS 10.x.x version also.
# Suggestion:
- Try to set “start-mdbs-with-application” as “true” and check if that works for you.
This is because if you read the “Link-1″ carefully it states that “With default setting of true”, however when you check the “Default” column it shows “false”. Hence cant say which one is default. It might be document bug as well. However you have tried it so you can skip this suggestion.
# How to solve this issue:
1) Create a simple test case to prove that “start-mdbs-with-application” when set as “false” does not work.
2) Open a ticket with Oracle and provide all the details with the test case and let them do their job.
Hope this information helps.
Regards,
Ravish Mody

Deployment issues, how is weblogic-ejb-jar.xml linked to ejb-jar.xml

Hey guys,
I'm getting the following error I think because i have something configured incorrectly in my xml files. Instead of yousing activationConfig properties in my MDB I wanted to set them in the ejb-jar.xml file manually. The following error I'm getting is...
Unable to deploy EJB: MyMDB from MDBtest2:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'inQueue' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
 at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:641)
 at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:330)
 at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1097)
 at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:991)
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
 <display-name>MDBtest2</display-name>
 <enterprise-beans>
 <message-driven>
 <ejb-name>MyMDB</ejb-name>
 <ejb-class>cms.crown.mdb.MyMDB</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-destination-link>omg</message-destination-link>
 <resource-ref>
 <res-ref-name>weblogic.jms.XAConnectionFactory</res-ref-name>
 <res-type>javax.jms.XAConnectionFactory</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
 <resource-env-ref>
 <resource-env-ref-name>inQueue</resource-env-ref-name>
 <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
 </resource-env-ref>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <container-transaction>
 <method>
 <ejb-name>MyMDB</ejb-name>
 <method-name>onMessage</method-name>
 <method-params>
 <method-param>javax.jms.Message</method-param>
 </method-params>
 </method>
 <trans-attribute>Required</trans-attribute>
 </container-transaction>
 </assembly-descriptor>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-ejb-jar xmlns:wls="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">

<wls:message-destination-descriptor>

<wls:message-destination-name>omg</wls:message-destination-name>
<wls:destination-jndi-name>inQueue</wls:destination-jndi-name>
<wls:initial-context-factory>weblogic.jms.XAConnectionFactory</wls:initial-context-factory>
<wls:provider-url>http://localhost:8010</wls:provider-url>
</wls:message-destination-descriptor>
</wls:weblogic-ejb-jar>
Hope this is readable, thanks for any assistance

Hi,
It looks like first thing you are using EJB3 but your XML files are still pointing to version="2.1" and very old.

<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee "http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
 
*try this: In below "ejb-jar.xml" file*
QCF = your Connection factory JNDI Name
TestQ = your Queue JNDI Name
Transaction Attribute is ByDefault = Required ...so no need to add it here.
<?xml version='1.0' encoding='UTF-8'?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" metadata-complete="true">
<enterprise-beans>
<message-driven>
<ejb-name>MyMDB</ejb-name>
<mapped-name>TestQ</mapped-name>
<ejb-class>cms.crown.mdb.MyMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>connectionFactoryJndiName</activation-config-property-name>
<activation-config-property-value>QCF</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destinationJndiName</activation-config-property-name>
<activation-config-property-value>TestQ</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
"weblogic-ejb-jar.xml":
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
 Now u need to Just define the Provider URL here...if you want a remote provider...else not required JNDI names are already defined in the ejb-jar.xml file 
</weblogic-ejb-jar>
Some Links which you can refer:
To Generate the Deployment Descriptors ...in case of EJB3 Applications: *http://jaysensharma.wordpress.com/2010/04/02/generating-ejb3-clientjar/*
MDB3.0 Sample: *http://jaysensharma.wordpress.com/2009/08/17/mdb3-0-sample-for-weblogic-application-server/*
Thanks
Jay SenSharma

Deployment order in 6.0

I'm sure this has been covered before but is there anyway to dictate the
deployment order of EJB's contained in a single EAR file?
Or does WL use some default scheme - alphanumeric sorting, order in the
applications.xml file??
Thanks
Tom

The default scheme is random.
in your config.xml you can specify the order in 6.x, it's just not documented.
The format is:
<EJBComponent DeploymentOrder="9" Name="discount"
Targets="wlcsServer" URI="discount.jar"/>
We were told by a Bea consultant to set all of the out of the box
EJBs to 9, all of our beans that are not run through ejbc to something like 80,
and all of the rest to 99.
WLS will randomly pick the order for all EJBs with the some deployment order,
for example 9.
The catch, once it finds one EJB that is fully packaged (tan through ejbc, it
will assume that all of the remainder are fully packaged. This can cause problems.
Tom Gerber <[email protected]> wrote:
I'm sure this has been covered before but is there anyway to dictate
the
deployment order of EJB's contained in a single EAR file?
Or does WL use some default scheme - alphanumeric sorting, order in the
applications.xml file??
Thanks
Tom

Deployment Order

I am running WLS 7.0 and I've noticed that the deployment order
of EJBs does not appear to work. I have 3 ejbs in 3 different
ears. If I set the deployment order to be 1 for A.ear, 2 for B.ear, and 3 for
C.ear and startup weblogic and watch the
startup.log, I get different results each time I stop and start
weblogic.
Is there something that I'm missing? Is this fixed in SP1?

I'm not sure if it's fixed in SP1 or not. It's worth giving it a shot.
If SP1 doesn't fix this problem, i would suggest that you talk to
[email protected]
Kumar
Brian wrote:
I am running WLS 7.0 and I've noticed that the deployment order
of EJBs does not appear to work. I have 3 ejbs in 3 different
ears. If I set the deployment order to be 1 for A.ear, 2 for B.ear, and 3 for
C.ear and startup weblogic and watch the
startup.log, I get different results each time I stop and start
weblogic.
Is there something that I'm missing? Is this fixed in SP1?

Deployment order across applications

I have a web app that implements ServletContextListener. This app on deployment
looks for an ejb on another app. How do I tell weblogic to deploy the web app
before the ejb app. These two have to be different applications. I cannot combine
them into the same ear. I am not able to find ways to identify deployment order
across applications. Any thoughts.
Any ideas on other approaches if this is not possible will be greatly appreciated.
Thanks in advance.

We don't want the dependency between the EAR application and this web app. We also
plan to deploy this web app on multiple boxes that will require only a servlet
container and will not require an app server. Also the EAR app will be deployed
on multiple boxes and we do not want the extra overhead of this web app. Hope
this answers your question.
Do you know of any alternative approach to this problem since I do not see having
deployment ordering across apps in weblogic.
Thanks.
Gajendra Sanil
"Dimitri I. Rakitine" <[email protected]> wrote:
I'm curious, why you cannot deploy your EJBs and WAR in the same EAR?
Deploying them separately will result in a very serious performance
penalty because local RMI optimization will not be used.
Gajendra Sanil <[email protected]> wrote:
I have a web app that implements ServletContextListener. This app ondeployment
looks for an ejb on another app. How do I tell weblogic to deploy theweb app
before the ejb app. These two have to be different applications. Icannot combine
them into the same ear. I am not able to find ways to identify deploymentorder
across applications. Any thoughts.
Any ideas on other approaches if this is not possible will be greatlyappreciated.
Thanks in advance.--
Dimitri

MDB and EJB in transactions

Hi ,
          I have an MDB running on weblogic 8.2 and calling a remove ejb running on a different machine. After getting home interface when I tried to create the remote object Iam getting the following error.
          java.lang.NullPointerException
          at weblogic.transaction.internal.PropagationContext.useNewMethod(PropagationContext.java:866)
          at weblogic.transaction.internal.PropagationContext.writeExternal(PropagationContext.java:169)
          at weblogic.common.internal.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:100)
          at weblogic.common.internal.ChunkedObjectOutputStream.writeObjectWL(ChunkedObjectOutputStream.java:122)
          at weblogic.rjvm.MsgAbbrevOutputStream.setTxContext(MsgAbbrevOutputStream.java:122)
          at weblogic.rjvm.BasicOutboundRequest.setTxContext(BasicOutboundRequest.java:156)
          at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:106)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:276)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
          Can any body tell what could be the reason. The message sent from MDB to ejb is a transactional message.
          Thanks in advance
          Manikyala

I suggest posting to the EJB newsgroup.
          (1) Transactions certainly are supported for remote services. This is a common use case.
          (2) Your problem seemed to occur when getting the remote home - but likely would not occur when actually using it. Since I think (not 100% sure) that the action of obtaining the remote home need not be transactional, I previously suggested suspending the transactions, but only for the duration of the call to get the remote home.
          Tom
          > Hi Tom,
          >
          > Looks like what Iam doing is not correct.
          >
          > Iam calling a remote ejb which on a different server
          > from my MDB. Iam using t3 to get the context. Also in
          > the weblogic-ejb-jar.xml I put transaction value as
          > Required.
          >
          > Now I replaced that with NotSupported and problem is
          > solved.
          >
          > The conclusion is (if Iam not wrong) when creating a
          > remote home we should not use transactions since the
          > remote service is not participating in transaction.
          >
          > Thanks again Tom
          >
          >
          > Manikyala

Issue with create deployment order with BAPI_POSRVAPS_SAVEMULTI3

Hi Experts,
We are trying to create deployment orders with BAPI_POSRVAPS_SAVEMULTI3. The following are the input:
LOGICAL_SYSTEM RR1CLNT010
ORDER_TYPE 2
EXT_NUMBER_ASSIGNMENT
COMMIT_CONTROL E
PLNG_VERSION 000
NO_CREATE
PLANNING_MODE_USAGE 0
EVENT_CONTROL 1
And for receipts and requirement, we put ATP category as EG and EF.
But it return error 'Events are supported only for Purchase Requisitions'. For u2018EGu2019 and 'EF', I can see it is category typ '2'.
Does this BAPI able to create deployment STR or it can only create SNP STR?
Thanks.
best regards,
Wenyan

Hi Wenyan,
In the BAPI, the following code should be responsible for the error message:
* -> check: event_control is only available for purchase requisition
if event_control = gc_apo_bapi_create_event and order_type <> gc_requisition.
* -> error message
 _apo_bapi_message_add_itab0 gc_error gc_apo_bapi_msgclass '342'
 return.
 lv_error = gc_true.
endif.
The relevant constants are:
* -> constants for event control
CONSTANTS:
gc_apo_bapi_no_event TYPE bapi10503eventcontrol VALUE space, "collect but no direct sending
gc_apo_bapi_create_event TYPE bapi10503eventcontrol VALUE '1', "collect + send event
gc_apo_bapi_no_event_collect TYPE bapi10503eventcontrol VALUE '2'. " no collect and no sending
*--> External Order types
CONSTANTS:
* Bestand
gc_stock TYPE /sapapo/r3obj VALUE '0',
* Bestellanforderung
gc_requisition TYPE /sapapo/r3obj VALUE '1',
* Bestellung
gc_purchase_order TYPE /sapapo/r3obj VALUE '2',
As you can see, if you want to create an order other than SNP purchase requistion, you cannot set the control_event as '1'.
Best Regards,
Ada

Weblogic 8.1 SP2 does not support 'Order by' clause in EJB-QL

It seems that Weblogic 8.1 SP2 does not support 'Order by' clause in EJB-QL. EJB 2.1 spec supports 'Order by' clause in EJB-QL. Am I right when I say that it indicates : "Weblogic 8.1 SP2 does not support EJB 2.1" ? In that case, what can be the alternative since I am using Weblogic 8.1 and I require 'Order by' clause in Ejb-QL as well.

In WL 8.1 SP4 I can use the ORDERBY just fine.
Try ORDERBY instead of Order by

How to Confirm the SDAs deploy order of SCA in RemoteGUI of SDM

Hello everybody,
 We assemblied a sca file in NWDI when we finished development.
 But when we used RemoteGUI to deploy the SCA file in another NetWeaver2004s engine.The Deploy order is wrong.The SDM doesn't first deploy the Library,EAR.It deployed the SDA ordering by the letter order ,not the dependence order.
 For example,there are two SDA in the SCA file, one's name is d_lib,another name is a_ear.The a_ear depend on the d_lib.When SDM deploy the SCA,it first deploy the a_ear,not d_lib.
 How to Confirm the SDAs deploy order of SCA in RemoteGUI of SDM?

Hi Marc,
Thanks for your help!
I found the Prodiver.xml,and the content is:
<?xml version="1.0" encoding="utf-8" ?>
- <provider-descriptor>
<display-name>om/library</display-name>
<component-name>om/library</component-name>
<description />
<major-version>7</major-version>
<minor-version>00</minor-version>
<micro-version>0</micro-version>
<provider-name>pjs.com</provider-name>
- <jars>
<jar-name>pjs.comomwcalistwcalist_daoWcalistPackage.jar</jar-name>
<jar-name>pjs.comomlogequipdao~daoPackaged.jar</jar-name>
<jar-name>pjs.comomnotificationnotification_daoNotificationPackage.jar</jar-name>
<jar-name>pjs.comombasedaodaoPackaged.jar</jar-name>
<jar-name>pjs.comomlogareaareadaopackaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoPostPackage.jar</jar-name>
<jar-name>pjs.comompostpost_daoSpecialtyPackage.jar</jar-name>
<jar-name>pjs.comomtaskdaopackaged.jar</jar-name>
<jar-name>pjs.comomgradeprojectgradedaopackagSDA.jar</jar-name>
<jar-name>pjs.comomlogreconlredaopackaged.jar</jar-name>
<jar-name>pjs.comomsafeexcepreportExcepReportPackage.jar</jar-name>
<jar-name>pjs.comomsaferecorddaoapi.jar</jar-name>
<jar-name>pjs.comomlogelogelogdaopackaged.jar</jar-name>
<jar-name>pjs.comomsysdaopackaged.jar</jar-name>
<jar-name>pjs.comombasevindbasedaopackaged.jar</jar-name>
<jar-name>pjs.comomlogsearchpersondao~SearchPersonSDA.jar</jar-name>
<jar-name>pjs.comomplacarddaoplacardPackaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoPersonPackage.jar</jar-name>
<jar-name>pjs.comomsbillrecorddaosbillRecordPackaged.jar</jar-name>
<jar-name>pjs.comomdutyperson_dao~DutyPersonSDA.jar</jar-name>
<jar-name>pjs.comomrptdaoRptSDA.jar</jar-name>
<jar-name>pjs.comompostpost_daoEquipmentPackage.jar</jar-name>
<jar-name>pjs.comomlogtypelogdaopackaged.jar</jar-name>
<jar-name>pjs.comomsafeproeval_daoProEvalPackage.jar</jar-name>
<jar-name>pjs.comompersonpostdaopackaged.jar</jar-name>
<jar-name>pjs.comomlogsearchlogdao~SearchSDA.jar</jar-name>
<jar-name>pjs.comompublic~packaged.jar</jar-name>
<jar-name>pjs.comomspellgroupdaodaoPackaged.jar</jar-name>
<jar-name>pjs.comomlogpersonlogdao~packaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoRlogPackage.jar</jar-name>
<jar-name>pjs.comomschedule_dao~ScheduleSDA.jar</jar-name>
<jar-name>pjs.comomreportrptdaopackaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoRecordClassPackage.jar</jar-name>
<jar-name>pjs.comompostpost_daoReqpPackage.jar</jar-name>
<jar-name>pjs.comomlogshiftclassdao~ShiftClassSDA.jar</jar-name>
<jar-name>pjs.comomverifyrecorddao~RecordPackage.jar</jar-name>
<jar-name>pjs.comomunit_dao~UnitSDA.jar</jar-name>
<jar-name>pjs.comomdatadefinedefdaopackaged.jar</jar-name>
<jar-name>pjs.comomheader_dao~HeaderSDA.jar</jar-name>
<jar-name>pjs.comomspellspedaopackaged.jar</jar-name>
<jar-name>pjs.comomlogrecdlcddaopackaged.jar</jar-name>
<jar-name>pjs.comomlogsearchequip_dao~SearchEquipSDA.jar</jar-name>
<jar-name>pjs.comomcompanycomdaopackaged.jar</jar-name>
<jar-name>pjs.comommaceasyformdao~daoJAR.jar</jar-name>
<jar-name>pjs.comomdeclaredecdaopackaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoFunlcodePackage.jar</jar-name>
<jar-name>pjs.comomlogeventlevdaopackaged.jar</jar-name>
<jar-name>pjs.comomclient_dao~ClientSDA.jar</jar-name>
<jar-name>pjs.comomlogdepldedaopackaged.jar</jar-name>
<jar-name>pjs.comomlogceqplceqdaopackaged.jar</jar-name>
<jar-name>pjs.comomrptinforptdaopackaged.jar</jar-name>
</jars>
</provider-descriptor>
I checked it and didn't find any error! What can i do?

Meaning of the Deployment Order attribute

Does anyone know to what the Deployment Order attribute corresponds in
          the Create a new Connector window ?
          Thanks in advance.


Hello Lee,
The origin of the front panel is denoted by the diamond shape in the front panel grid. As you place your tab control farther from this axis, the value of the Position:Left property will increase. You might want to read this property at runtime and configure any other positions as relative to this one. I hope this is what you needed!
Mike D.
Message Edited by Duffman Says: on 04-18-2007 12:12 PM
Attachments:
ScreenShot.JPG ‏15 KB

Changing of Means of Transport for deployment order

Hi All,
Is it possible to manually/ programatically change the means of transport of a deployment order ? for example once deployment has run, it has created a deployment order with means of transport, lets say, 0001 ( Truck). Now i want to change the means of Transport to 0003 ( Air). Is it possible using some BADI etc ?
Pls note that i know that by assigning product speciic means of product of 0003, it is possible to directly create deployment order for 003 means of transport. Due to some requirement, we want to change it manually.
Regards,
Pawan.

Hi Senthil,
I tried that option already. Infact there is no need to delete existing deployment order, you can simply run deployment with replan all option. This will create deployment orders on the new means of transport. What i wanted is, without running deployment, is there some option possible wherein i can change the means of transport of an existing order, which is already created on another means of transport ?
regards,
Pawan.

Changing Deployment Order

Hi,
Is there a way to alter deployment order through WLST? Or, does someone know about altering deployment order(not from Admin Console though!) ?
Thanks
Nitin

Hi Nitin,
This can be done in Offline Mode:
Step1). run . ./setWLSEnv.sh
Step2). java weblogic.WLST
Step3). wls:/offline> readDomain(r'C:\bea103\user_projects\domains\7001_Domain')
OR
wls:/offline> readDomain('C:/bea103/user_projects/domains/7001_Domain')
Step4). cd ('AppDeployment')
Step5). ls()
wls:/offline/7001_Domain/AppDeployment> ls()
drw- PolicyTestEAR
drw- WebAppEar
drw- SecondWebAppEar
Step6). cd ('SecondWebAppEar')
Step7). cmo.setDeploymentOrder(111)
wls:/offline/7001_Domain/AppDeployment/SecondWebAppEar> set('DeploymentOrder',111)
wls:/offline/7001_Domain/AppDeployment/SecondWebAppEar> ls()
-rw- AltDescriptorPath..........................null
-rw- AltWlsDescriptorPath..........................null
-rw- ApplicationIdentifier..........................null
-rw- ApplicationName..........................null
-rw- CompatibilityName..........................null
-rw- DeploymentOrder ..........................111
-rw- DeploymentPrincipalName..........................null
-rw- InstallDir..........................null
-rw- ModuleType..........................ear
-rw- Name..........................SecondWebAppEar
-rw- Notes..........................null
-rw- PlanDir..........................null
-rw- PlanPath..........................null
-rw- SecurityDdModel..........................DDOnly
-rw- SourcePath..........................C:\JavaTest\Diagnostics\SecondWebAppEar
-rw- StagingMode..........................stage
-rw- Target..........................AdminServer
-rw- ValidateDdSecurityData..........................false
-rw- VersionIdentifier..........................null
============================================
As well as in Online Mode :
http://weblogic-wonders.com/weblogic/2010/05/23/changing-deploymentorder-of-datasources/
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 14, 2010 1:57 PM
Edited by: Jay SenSharma on Jan 14, 2010 1:58 PM

Deployment order of MDBs vs EJBs in WL startup sequence

Similar Messages

Maybe you are looking for