What exactly happens when starting/stopping an EJB application (SAP J2EE Engine 6.30)?
start_app: First, the files that are needed by the container during start (i.e. jar files and other configuration stuff) are downloaded from the DB. Then the descriptors for the application are built and they are used to create the naming contexts for each bean. After that the specific EJB class loader for the application is created and registered, the containers for each EJB are initialized and their EJBHomes and/or EJBLocalHomes are bound to JNDI. Persistence Managers for the CMP entity beans are created and initialized. Finally, the pools for stateless, entity, and message-driven beans are initialized. The default initial pool size is 0 – this means that no instances will be created (and respectively no setSessionContext/setEntityContext/setMessageDrivenContext wil be invoked) at start time.
Related Questions
- How can I deploy my application into the J2EE engine in SAP NetWeaver AS? Does the certification require that we use a particular method?
- What really happens internally when the UI Engine initiates a connection to a ULC application?
- What happens if I do not return the recredentialing application by the stated deadline?
