Before you begin
You must install a Java EE library before you can start it. See Install a Java EE library
When you start a Java EE library, you can make it immediately available to clients, or you can start it in Administartion Mode to first ensure that it is working as you expect. Starting in Administration mode allows you to perform final ("sanity") checking of the library directly in the production environment without disrupting clients.
Similarly, you can stop a Java EE library so that no clients can use it, or you can stop it in Administration Mode so that only administrative tasks can be performed.
Stopping a library does not remove its source files from the server; you can later redeploy (also called update) a stopped library to make it available to deployed WebLogic Server modules and applications once again.
Libraryentry in the Type column.
When you start a Java EE library, you must pick one of the following options:
Servicing all requests: Specifies that WebLogic Server make the library immediately available to all modules and applications that reference it.
Servicing only administrative requests: Specifies that WebLgoic Server make the library available in Administration Mode only.
When you stop a Java EE library, you must pick one of the following options:
When work completes: Specifies that WebLogic Server wait for the library to finish its work and for all modules or applications that are currently using it to stop.
Force stop now: Specifies that WebLogic Server stop the library immediately, regardless of the work that is being performed and the modules and applications that are currently using it.
Stop, but continue servicing administrative requests: Specifies that WebLogic Server stop the library once all its work has finished, but to then put the library in Administration Mode so it can be accessed for administrative purposes.