At a Sametime 9 Deployment, we ran into an issue where the database tables were not created at install, and received the following error in the IBM Installation Manager:
Exception thrown when trying to register installation with Sametime System Console
Register the Sametime Media Server in Sametime System Console Server by running registerProduct.bat/sh utility
Exception thrown when trying to add SIP Peer in Sametime Video Manager Server
Exception thrown when trying to modify the default Conference Template in Sametime Video Manager Server
Exception thrown when trying to create a new user in Sametime Video Manager Server. Use the default credentials.
To check if the installer created the solidDB tables required, run the following commands:
[root@vmgrserver1 ~]# cd /opt/solidDB/soliddb-7.0/bin/
[root@vmgrserver1 bin]# ./solsql
IBM solidDB SQL Editor (teletype) - Version: 7.0.0.0 Build 2011-10-14
Copyright Oy International Business Machines Ab 1993, 2011.
Username: admin
Password:
Connected to default server.
Execute SQL statements terminated by a semicolon.
Exit by giving command: exit;
solsql> list tables;
RESULT
------
Catalog: PROXIAS
Schema: ADMIN
TABLES:
-------
CHANGE_MONITOR
COMMOBJECT
COMMOBJECT_H323IDENTITY_H323ID
COMMOBJECT_H323IDENTITY_EMAILID
COMMOBJECT_H323IDENTITY_MOBILEUIM
COMMOBJECT_H323IDENTITY_URLID
COMMOBJECT_H323IDENTITY_PARTYNUMBER
COMMOBJECT_H323IDENTITY_DIALEDDIGITS
COMMOBJECT_H323IDENTITY_TRANSPORTID
COMMOBJECT_H323IDENTITY_CALLSIGNALADDRESS
COMMOBJECT_H323IDENTITY_SECONDARYKEY
COMMOBJECT_H323IDENTITY_RASADDRESS
COMMOBJECT_H323IDENTITY_TERMINALTYPE
COMMOBJECT_H323IDENTITY_FLATNAMESPACEUSERNAMES
COMMOBJECT_H323IDENTITY_EMAILIDDERIVEFROMUSER
COMMOBJECT_SIPIDENTITY_IDENTITYADDRESSESEXPIRE
COMMOBJECT_SIPIDENTITY_IDENTITYSECONDARYKEY
COMMOBJECT_SIPIDENTITY_IDENTITYTERITARYKEY
COMMOBJECT_DEVICESITEUID
HIBERNATECONFERENCEROOMIMPL
HIBERNATECONFERENCEROOMTEMPLATEIMPL
DIALRULE
DEVICEAUTHENTICATION
ENTERPRISEDIRECTORYCONFIG
ENTERPRISEDIRECTORYREPORTSTATUS
ENTERPRISEDOMAIN
DOMAINSTATUSIMPL
ENTERPRISEGROUPMAPPING
ENTERPRISEGROUPMAPPING_ROLES
EXTGATEKEEPER
EXTMCUZONE
EXTMCUZONEORDER
EXTSBC
EXTSIPPROXY
EXTSIPPROXY_DOMAINLIST
MEDIAPATHEXCLUSION
NETWORK
NETWORKUSAGESCOPE
SUPERCLUSTERNODE
SUPERCLUSTERNODE_ALTNAMES
OUTBOUNDSIPAUTHENTICATION
SCHEDULEDBANDWIDTHRESERVATION
SCHEDULEDBANDWIDTHRESERVATION_THROTTLEPOINTBANDWIDTH
SIMPLIFIEDGWDIALING
SITE
SITE_ISDNNUMBERASSIGNMENTCONFIG_ISDNNUMBERRANGES
SITELINK
TERRITORY
TERRITORYOWNER
PERSISTEDUSERINFO
PERSISTEDUSERINFO_CONFERENCECODEERRORS
PERSISTEDUSERINFO_INDIVIDUALROLES
PERSISTEDUSERINFO_GROUPROLES
VERTICALSERVICECODE
VIRTUALENTRYQUEUE
ACCOUNTCONFIG
ALERTCONFIGURATION
AVPROTECTIONCONFIG
CALENDARCONFIG
CALLSERVERCONFIGURATION
CALLSERVERCONFIGURATION_SIPDOMAINLIST
CMAINTEGRATIONCONFIGURATION
CONSOLESESSIONCONFIG
DEFAULTCONFERENCESETTINGSIMPL
DNSPUBLISHINGCONFIGURATION
DEVICEAUTHENTICATIONCONFIGURATION
ENTERPRISEDIRECTORYSTATUS
JUNIPERCONFIGURATION
LOGINBANNERCONFIGURATION
PASSWORDCONFIG
REGISTRATIONPOLICYCONFIGURATION
REPLICATIONSERVER
REPLICATIONSERVER_NAMES
SITETOPOLOGYSERVERCONFIGURATION
VIRTUALENTRYQUEUEDEFAULT
MRCCONFIGURATION
GATEKEEPERBLACKLISTCONFIGURATION
WHITELIST
WHITELIST_WHITELISTIPS
DMAFARMCONFIGURATION
DAILY_STATISTICS
CONFERENCEAUDIT
CALLDEVICEALIASES
CALLEVENT
CALLPROPERTY
CALLAUDIT
NETWORKUSAGE
CONFERENCEEVENT
HOURLY_STATISTICS
SUBSCRIPTIONBEGIN
CALLMETADATA
NETWORKUSAGE_SCOPE
REGISTRATIONBEGIN
CALLENDINFO
MINUTELY_STATISTICS
CONFERENCEPROPERTY
REGISTRATIONSIGNALINGMESSAGE
REGISTRATIONALIAS
SUBSCRIPTIONEND
CDRPROPERTY
ALERTAUDIT
SUBSCRIPTIONSIGNALINGMESSAGE
REGISTRATIONEND
EXPORTHISTORY
1 rows fetched.
solsql>
To create the required database schemas, need to run the following commands
loadSolidDBSchema.sh
createLBSchema.sh
When running this script the issue was that the customer installed Websphere in /local/IBM/Websphere/AppServer/ instead of /opt/IBM/WebSphere/AppServer and the creation script is looking for /opt/IBM/WebSphere/AppServer/java for the install path.
2 comments:
Hello Dan. Do you have any idea what username and password I should be trying to use in this procedure? IBM seemed to think it would be our wasadmin user account, but that doesn't appear to be working...
Mark: Should be admin/admin by default
Post a Comment