Problem:

• Product Name: Borland Enterprise Server, AppServer Edition
• Product Version:  5.2.1
• Product Component: Partition
• Platform/OS Version: All

By default, the Borland Enterprise Server 5.2.1 services (web container, Java Session Storage and EJB container) in the partition are clustered together. The osagent will re-distribute the load across multiple partitions. How would you configure a standalone partition?

Resolution:

To configure a standalone partition, you need to follow the steps below to ensure all the services are not clustered.

1. Apache Configuration (\\var\\servers\\\\apache2\\conf)

a. In the WebClusters.properties, you need to amend the following line.

ClusterList = cluster1, cluster2, cluster_standalone
cluster_standalone.webcontainer_id = tc_standalone
cluster_standalone.enable_loadbalancing = false

b. In the UriMapFile.properties, you need to add the following lines depending on the no of war (web context) deployed. My war file web context is web.

/web=cluster_standalone

/web/*=cluster_standalone

2. Tomcat Container (\\var\\servers\\\\adm\\properties\\partitions\\\\tomcat\\conf\\server.xml)

a. Change the name for the IIOP connector to an unique name. (Eg. tc_standalone). The default name is tc_inst1.

tc_standalone" debug="0" minprocessors="5" maxprocessors="75">

b. Change the storeName to the Java Session Storage name defined in the next step.

ejb_standalone" debug="0">

3. Java Session Storage (\\var\\servers\\\\adm\\properties\\partitions\\\\services\\jss.properties)

a. Amend the following line

Jss.factoryName=ejb_standalone

4. EJB Container (\\var\\servers\\\\adm\\properties\\partitions\\\\services\\ejbcontainer.properties)

a. Amend the following line. The name must be unique and exclude tc_standalone used in the example above.

ejb.name=ejb_standalone