Sequencing the startup beans in different Enterprise Application Archive (EAR) files
 Technote (FAQ)
 
Question
If we have multiple EAR files, can we sequence the startup beans in the different EAR files?
 
Answer
The bean environment property java:comp/env/wasStartupPriority is used to order startup beans within an Enterprise JavaBeans™ JAR file. This property can be set to an integer. This allows an ordering to be specified if multiple startup beans are present in an Enterprise JavaBeans module. The beans are started from low to high. However, the wasStartupPriority can only be used to sequence the startup beans in an Enterprise JavaBeans JAR file. The order in which this process is applied to different Enterprise JavaBeans JAR files in a single EAR file is undefined.

Enterprise application startup order can also be sequenced by setting the Starting Weight Property for an enterprise application using the administrative console. Hence, if each enterprise application has only one Enterprise JavaBeans module that has startup beans in it, then by using the wasStartupPriority environment property within the beans, and by setting the Starting Weight property for the enterprise applications, the startup beans in the various enterprise applications can be sequenced to a certain degree.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Enterprise Edition (EE)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1107976
IBM Group: Software Group
Modified date: Apr 16, 2003