Problem:
- Product Name: BES App Server
- Product Version: 5.x & 6.x
- Product Component: BES Partition, BES Configuration, BES Management Agent
- Platform/OS Version: All
- JDK/Compiler Version: Same versions bundled with BES
BES Partitions are automatically started by default when the parent BES Configuration(6.x) or BES Management Agent(5.x) starts. However, you may like to manually start your BES Partition during your development, debugging, or testing phases.
Hence, this document takes you through the exact steps to configure your BES Partition not to auto-start.
Resolution:
For BES 6.x Users:
1. Locate the folder for *-dynamic.xml files for your BES Managed Objects.
i.e. var\\domains\\base\\configurations\\agents\\2. Find the respective *-dynamic.xml for your Partition.
e.g. MyPartition-dynamic.xml3. Lookup for the attribute called "desired-state" in -dynamic.xml file.
4. Modify the value of "desired-state" attribute to "Stopped" (default is "Running").5. Lookup for the attribute called "manage" in the same -dynamic.xml file.
6. Change the value of the "manage" attribute to "false" (default is "true").
7. You will see that Partition is not automatically started up when you bring up BES Server(scu) next time.
For BES 5.x Users:
1. Locate the Server properties directory for your BES.
i.e. \\var\\servers\\adm\\properties\\2. Find the "server.properties" file and use a text editor to open it.
3. Lookup for the entry "server.service.autostart" in your "server.properties" file.
e.g. server.service.autostart=management_osagent standard ots servermanager osagent MyPartition4. Remove the BES Partition in question from the list of the entry "server.service.autostart".
e.g. server.service.autostart=management_osagent standard ots servermanager osagent
5. Now, restart your BES Server(ias) to see that those removed BES Partition is not autostarted.
i.e. "standard" is started automatically, but MyPartition is not started.
#AppServer
#VisiBroker
#partition
#Security
