Within a network of machines, you may wish to use some of the WACS tool sets from another machine on the network. In order to use some of the facilities, you will need to make sure that the database server will allow network connections, that a copy of the WACS configuration file is available to the programs you're trying to use on that other machine and that the database client side code has been installed. The table below is a basic checklist on how to get things working - refer to the database documentation for specifics.
Table 3.1. Steps To Get Network Connections To Work
| Database | Task | Description |
|---|---|---|
| Oracle 10i/11i | 1 | Start TCP network listener on database server:
$ORACLE_HOME/bin/lsnrctl start - if that doesn't work,
check for database entity in
$ORACLE_HOME/network/admin/listener.ora file and try
start again. Same command supports stat and
stop requests. |
| 2 | Install Oracle instant client or similar software on the client
machine (ie laptop or workstation). Create entry for database server in
client's $ORACLE_HOME/network/admin/tnsnames.ora file.
Install the wacs-core module and the perl DBD::Oracle driver. | |
| 3 | Copy the server's wacs.cfg across to the client,
changing the
locations specified in the fsloc section as necessary for where they are
imported on the client system. | |
| 4 | Make sure you can connect to the database using the creditials in
the wacs.cfg file using the sqlplus
SQL interpreter. | |
| MySQL 5 | 1 | Edit the /etc/my.cnf file on the database server
and make sure the line bind-address=0.0.0.0 is present
and has not been commented out - this ensures TCP mode connections are
enabled. If you make a change, restart the MySQL server. |
| 2 | Install the WACS software on the client machine - if using packages this will bring in all the necessary runtime modules. | |
| 3 | Copy the server's wacs.cfg across to the client,
changing the
locations specified in the fsloc section as necessary for where they are
imported on the client system. Additionally change all references to
localhost to the servers name - mostly these will be in the
database section. | |
| 4 | Make sure you can connect to the database using the MySQL root user
using the mysql SQL interpreter. Then determine the
wacs database creditentials from wacs.cfg and create
and then use them as per the notes below. |
With the likes of Oracle 10g, that is all that is necessary. For MySQL, you additionally have to tell the MySQL server that the wacs account is allowed to access the database from that location, so you would need to do the following steps on the server to allow that to happen:
nemesis% mysql -u root -p
Password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 80
Server version: 5.0.45 Source distribution
Type 'help;' or \h for help. Type '\c' to clear the buffer.
mysql> CREATE USER 'wacs'@'fawn.mydomain.info'
-> IDENTIFIED BY 'wacs';
Query OK, 0 rows affected (0.00 sec)
mysql> CREATE USER 'wacs'@'fawn'
-> IDENTIFIED BY 'wacs';
Query OK, 0 rows affected (0.00 sec)
mysql> COMMIT;
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
mysql> QUIT;
Bye
nemesis%
You will also need to make sure that the actual hostname, eg nemesis in our examples, is used in the wacs.cfg file rather than localhost. While localhost will work fine on nemesis itself, fawn won't work with that.