Before you can effectively run WebSphere Application Server, you must create a Sybase database named WAS, which WebSphere Application Server uses.
Create a database named WAS by performing the following steps:
#
to $
to indicate
your login identity.$ asecfg
<home_directory>/master
<home_directory>/sybsystemprocs
<home_directory>/sybsystemdb
Server '<server_name>' was successfully created. Done
$ <home_directory>/OCS-12_0/bin/isql -Usa -P \ -S<server_name>> sp_password null, <new_sa_password>
Note: The Adaptive Server installation and setup processes require certain user roles. Different user roles own different responsibilities and privileges. User sybase is the UNIX login account that owns all of the Sybase installation directories and files, sets permissions on those directories and files, and performs the installation and upgrading of Adaptive Server. User sa, created when you install the Sybase software, is not a UNIX login account; it is specific to Adaptive Server and is used to log in to Adaptive Server with the isql command. It is the Sybase System Administrator in charge of creating user accounts, assigning permissions on databases, and creating new databases. Immediately after a new installation, there is no password on the sa account, and one must be created.
$ <home_directory>/OCS-12_0/bin/isql -Usa -P<new_sa_password> -S<server_name>
If server <server_name> is running, you will see the isql prompt:
1>
quit
.$ isql -Usa -P<new_sa_password> -S<server_name> -n \ -i<home_directory>/ASE-12_0/scripts/instmsgs.ebf -o<output_file>
$ <home_directory>/OCS-12_0/bin/isql -Usa -P<new_sa_password> \ -S<server_name>
disk init name = 'WASDEV', physname = '/<home_directory>/was.dat', vdevno = 3, size = 5000
vdevno must be set to the next available (unused) device. To list devices in use, enter the commands:
isql -Usa -P 1> sp_helpdevice
size = 5000 is equivalent to 10 MB. You might need to specify a higher value for production use. The Sybase default is 2 MB, which is too small for WebSphere Application Server. You can use the alter database command.
go create database WAS on WASDEV = 10
go use WAS
The database will be your WebSphere Application Server administrative repository specified during installation of Application Server. The database name must be in uppercase.
go sp_addlogin EJSADMIN, <6-or-more-character_password>, WAS go sp_adduser EJSADMIN
These commands give the database user ID and password you will use when installing WebSphere Application Server. The user ID must be in uppercase. The password must be a minimum of 6 characters.
go sp_addlogin EJB, <6-or-more-character_password>, WAS
These commands give the user ID and password you will use to access your data source for EJBs in WebSphere Application Server. The user ID must be in uppercase. The password must be a minimum of 6 characters.
go sp_adduser EJB go grant all to EJSADMIN, EJB go grant role dtm_tm_role to EJB go COMMIT go use master go sp_dboption WAS, "trunc log on chkpt", true go COMMIT go use WAS go COMMIT go CHECKPOINT go
isql -Usa -P -S<server_name> 1> sp_configure "enable DTM", 1 2> go
Next, stop ASE:
isql -Usa -P -S<server_name> 1> shutdown 2> go
Finally, restart ASE:
<Sybase_install_root>/ASE-12_0/install/startserver -f RUN_serverfile
Later, grant dtm privileges to the user EJB.
#
to $
to indicate your
login identity.$ <home_directory>/OCS-12_0/bin/isql -Usa -P<new_sa_password> -S<server_name>
If server <server_name> is running, you will see the isql prompt:
1>
1> shutdown
2> go
$ cd <home_directory>/ASE-12_0/install
$ startserver -f RUN_$DSQUERYwhere $DSQUERY is the value that you set for this environment variable.
Check the messages that appear to ensure that no errors are reported.
00:00000:00001:2000/05/09 13:19:14.32 server 'iso_1' (ID = 1).
$ cd <home_directory>/jConnect-5_2
java sample2.SybSample Version
The SybSample screen appears, which displays source code in the top pane, text in the middle pane, and status information in the bottom pane. If you see the following text in the middle Sample Output pane, jConnect has been installed correctly:
Using JDBC driver version 5.2 jConnect (TM) for JDBC(TM)/5.2. . .