Use clsetup command to simplify the task of setting
up a cluster on a typical machine configuration. The clsetup
command can create instances if they do not already exist, and perform cluster
setup on these instances based on the configurations in the input files.
The following input files are required for the clsetup
command to function:
-
clinstance.conf
-
contains information about the application server instances that are
part of the cluster.
-
clresource.conf
-
contains information about the HADB database and other resource information.
-
clpassword.conf
-
contains the asadmin password and is pre-populated
with the correct password during a standard installation.
By default, the input files are located in the application server configuration
directory:/etc/opt/SUNWappserver7. Additionally, the clsetup command is located by default in installdir/bin.
Before editing the input files, ensure the following:
-
The order of the entries must not be changed.
-
Any line that starts with a hash mark (#) is treated as a
comment.
-
If the entities to be handled (HADB database nodes and application
server instances) already exist, the clsetup command does
not delete or reconfigure them, and the respective configuration steps are
skipped.
Before running the clsetup command you must:
-
have the asadmin and hadbm
command on the local machine.
-
use the clsetup command as-is to setup
a typical cluster configuration.
-
set up HADB for administration. The HADB management agents
should be running on all hosts that are part of the cluster.
-
use the same administrator password for all domains that are
part of the cluster.
-
start the administration servers of all instances that are
part of the cluster.
During standard installation, the clinstance.conf
file is created with entries for two instances. This occurs only if the Sun
Java System Application Server is also installed. However, if only the application
server administration client is installed on the machine, the clinstance and clpassword files installed on this machine
are not pre-populated. If you add more instances to the cluster, you must
update the clinstance.conf file with the information
for the new instances. The information about the instances in each cluster
must be defined in the instance file (default name is clinstance.conf). The following are the possible entries in the clinstance.conf file:
Table 1: Entries in the clinstance.conf file
| Entry | Definition | Default Value(s) |
| instance | Name of the application server instance | server1, server2 |
| user | Administration server user name | admin |
| host | Host name | localhost |
| port | Port number of the Administration Server | 4848 |
| domain | Name of the Administrative
domain | domain1 |
| instanceport | Port number of the
application server instance | 80, 81 |
| master | Boolean to indicate the
master instance | true. For first
time installation. |
The clresource.conf file contains information about
the HADB database, JDBC connection pool, JDBC resource, session store, and
session persistence. Permissions 0600 are preset on the clresource.conf file and it can be accessed only by the root user. The following
are the possible entries in the clresource.conf file:
Table 2: Entries in the clresource.conf file
| Entry | Definition | Default Value |
| HADB Database Information |
| historypath | Path for the history
files | On Unix: /var/tmpOn Windows:
REPLACEDIR (REPLACEDIR is replaced by the actual URL at runtime.) |
| devicepath | Path for the data
and log devices | On Unix: installdir/SUNWhadb/4.4.*On Windows: C:\Sun\AppServer7\SUNWhadb\4.4.* |
| datadevices | The number of data
devices on each node | 1 |
| portbase | The port base number
used for node 0 | 15200 |
| spares | The number of spare nodes | 0 |
| set | Comma separated list of database configuration attributes in the name=value
format. This option allows for specifying different file paths for each node. | Node-nodeno.device-devno.Path=pathAny device path that is not set for a particular node or device defaults to
the --devicepath value.NOTE; The managementProtocol attribute
has been deprecated. |
| agent | Specifies the host and port number where the management agent is listening. This value can be modified to be a remote machine if HADB is located on a different machine than where the application Server is installed.
The value for the remote agent would be of the form: hostname (or IP address):port. | localhost:1862 |
| adminpassword | The new adminpassword option introduced in HADB 4.4 version provides additional
security. The default used in the clresource.conf file is: password. Users can change the default value to suit their
requirements. | password |
| devicesize | Size of the device in MB | 512 |
| dbpassword | Password for the system user of the database | password |
| hosts | All hosts used for all data nodes | localhost,localhost |
| JDBC Connection Pool Information |
| steadypoolsize | Minimum and initial number of connections maintained in the pool | 8 |
| maxpoolsize | Maximum number of connections that can be created | 32 |
| datasourceclassname | Name of the vendor supplied JDBC datasource | com.sun.hadb.jdbc.ds.HadbDataSource |
| isolationlevel | Transaction isolation level on the pooled database connections | repeatable-read |
| isisolationguaranteed | Transaction isolation level guaranteed | true |
| validationmethod | type of validation method | meta-data |
| property | Property used to specify username, password, and resource configuration | username=appservusr:password=password:cacheDataBaseMetaData=false:eliminateRedundantEndTransaction=true:serverList=replaceurl |
| JDBC Resource Information |
| connectionpoolid | Name of the connection pool | appservCPL |
| Session Store Information |
| storeurl | JDBC URL of the HADB database | replaceurlValue is replaced by the actual URL at
runtime. |
| storeuser | HADB user who has access to session store | appservusr |
| storepassword | password for store user | password |
| dbsystempassword | Database system password | password |
| Session Persistence Information |
| type | The session persistence type | ha |
| frequency | The session persistence frequency | web-method |
| scope | The session scope | session |
| store | Session store | jdbc/hastore |
| Stateful Session Bean Information |
| sfsb | The stateful session bean failover | true |
| RMI IIOP Failover Information |
| rmi_iiop | RMI IIOP cluster configuration | true |
| Cluster ID Information |
| cluster_id | Cluster ID | cluster1 |
The clpassword.conf file contains the administration
server password. While executing the cladmin command, the asadmin command requires the administration server password specified
in the clpassword.conf file. The format for the clpassword.conf file is :
AS_ADMIN_PASSWORD=password
Where password is the administration server
password.
Permissions 0600 are preset on the clpassword.conf
file and it can be accessed only by the root user.
A log file, named clsetup.log, is available in the /var/tmp directory. By default the clsetup command
executes in verbose mode and logs information in the log file. Log file entries
start and end with timestamp tags. If the log file exists prior to execution,
the output is appended to the existing log file. Scan the log after each execution
to verify that it ran properly.
