Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Installation instructions
1.
2.
3.
4.
5.
2. This command is also applicable to any supported external application server (eg:
weblogic, websphere, tomcat..)
3. Please type the commands in command prompt, dont copy/paste from this.
If you want to migrate default MySQL CMS data to SQLAnywhere database then you
need to use cmsmigrate flag with biekpatch.exe. It is recommended not to use this flag
if cms database is not the default MySQL.
When you trigger this patch build on upgradable CABI machine with default MySQL as
CMS database using cmsmigrate flag, you will be prompted for existing MySQL CMS
database details and new SQLAnywhere CMS database details.
Fill the existing MySQL CMS database details and click Next.
Note: Selecting or unselecting of Already selected My SQL as auditing database has no
impact, because automigration of Audit data is not supported.
Fill the SQLAnywhere CMS database details and select Select SQL Anywhere as auditing
database option if you want auditing to be enabled, irrespective of whether you had
auditing enabled with MySQL database or not.
CMSDBUser=<SQLAnywhere Username>
Replace the BOXIMysql=1 with BOXISQLAnywhere=1
(Optional) Post Installation Steps:
After successful upgrade with default MySQL CMS database with cmsmigrate flag, MySQL
database will be retained. Follow below steps to remove the MySQL database and corresponding entries
from your windows machine.
Caution: This process also removes the Audit database (if any), so migrate the audit data before
proceeding.
Follow the steps:
1. Login to CABI server windows machine as an administrator
2. Open Central Configuration Manager (CCM) and stop the Server Intelligence Agent (SIA) service
3. After the SIA has stopped completely, open SIA properties and go to the Dependency tab
6. Select BOE120SQLAW (or similar) and click Add and then click OK
7. Go to services.msc and stop the BOE120MySQL (or similar) service
8. Open command prompt and run the following command to remove BOE120MySQL service
sc delete BOE120MySQL
9. Go to C:\Program Files (x86)\CA\SC\CommonReporting3 (or similar) location and delete MySQL5
folder
10. Open the odbcad32.exe file (32-bit ODBC Data Sources) that is located at
C:\Windows\SysWOW64 on 64-bit windows system and at C:\Windows\System32 on 32-bit
windows system
If the completion message indicates any error code then there is some problem with
installation. See below for error codes.
Exit Code
Message
---------
-----------------------------------------------------------------------
3010
16001
16005
16022
16023
Validation
Through web browser
Log into the Central Management Console via a web browser as administrator.
Select "Settings"
Product version should be 12.7.0.1983
If you used cmsmigrate flag in valid landscape, before starting this upgrade process
you would see MySQL value as 5.0.46-enterprise for Database Name entry. After
upgrade you can find the SQLAnywhere value as boe120sqlaw_<SQLAnywhere
Username>;boe120;sql anywhere;12.00.0001 for the same Database Name entry.
In windows
Note: If you trigger this process on Windows 2012/Windows 2012 R2 machine then you will get bunch
of message boxes as shown below. You can ignore/close these.
Certification Matrix
Operating System
CABI Version
Database
App Server
Installation type
Win2k12-EN
3.3
DEFAULT
DEFAULT
GUI
Win2k12-EN
3.3
DEFAULT
DEFAULT
SILENT
Win2k8R2-EN
3.3+FP 5.2
Oracle
WebLogic
GUI
Win2k8R2-EN
3.3+FP 5.2
Oracle
WebLogic
SILENT
Win2k8SP2-EN
3.3+SP5+SP6
External Mysql
DEFAULT
GUI
Win2k8SP2-EN
3.3+SP5+SP6
External Mysql
DEFAULT
SILENT
Win2k3SP2-EN
3.2+SP5
DEFAULT
DEFAULT
GUI
Win2k3SP2-EN
3.2+SP5
DEFAULT
DEFAULT
SILENT
Win2k8R2-PT
3.3
DEFAULT
DEFAULT
GUI
Win2k8R2-PT
3.3
DEFAULT
DEFAULT
SILENT
Win2k8R2-IT
3.3
DEFAULT
DEFAULT
GUI
Win2k8R2-IT
3.3
DEFAULT
DEFAULT
SILENT
Win2k8R2-KO
3.3
DEFAULT
DEFAULT
GUI
Win2k8R2-KO
3.3
DEFAULT
DEFAULT
SILENT
Win2k8R2-ES
3.3+FP 5.2
Oracle
WebLogic
GUI
Win2k8R2-ES
3.3+FP 5.2
Oracle
WebLogic
SILENT
Win2k8R2-FR
3.2+SP5
DEFAULT
DEFAULT
GUI
Win2k8R2-FR
3.2+SP5
DEFAULT
DEFAULT
SILENT
Win2k8R2-DE
3.2+SP5+SP6
External Mysql
DEFAULT
GUI
Win2k8R2-DE
3.2+SP5+SP6
External Mysql
DEFAULT
SILENT
Win2k8R2-CN
3.2+SP5+SP6
External Mysql
DEFAULT
GUI
Win2k8R2-CN
3.2+SP5+SP6
External Mysql
DEFAULT
SILENT
Win2k8R2-JA
3.2+SP5
DEFAULT
DEFAULT
GUI
Win2k8R2-JA
3.2+SP5
DEFAULT
DEFAULT
SILENT
Important Notes:
After installation of CABI 3.3 SP2 build with previous applied patch is other than CABI 3.3
SP1, CAF content (and any other custom content) will not work because the application
server got changed to Tomcat 7. To overcome the issue, redeploy those content
manually using wdeploy commands.
Eg: wdeploy tomcat7 DAPP=CAFName deploy
During the installation of CABI 3.3 SP2 patch using GUI installation process on top of
CABI 3.3 full installation with or without FP52 with default tomcat application server,
9
Install Tomcat 7 and Re-Deploy Web Applications screen will show Tomcat as Tomcat
5.5. You can ignore this message and can proceed further.
If you are using external application server as CABI application server, it will get stop
during the installation. Start the server after installation is done.
If you are installing on Portuguese environment with default tomcat, deploy all the web
applications to tomcat7 after installation using wdeploy utility.
If you are using external application server then redeploy the all web applications to
that server after installation using wdeploy utility.
After installation of CABI 3.3 SP2 on top of CABI 3.3 full installation with or without FP52
if Apache Tomcat 7.0.27 is stopped and Apache Tomcat 6.0.24 is running in Central
Configuration Manager then
o Stop Apache Tomcat 6.0.24
o Start Apache Tomcat 7.0.27
After the uninstallation of CABI 3.3 SP2 if the earlier version of tomcat is not running,
restart the machine.
If the CABI 3.3 SP2 is installed on top of CABI 3.3 SP1 patch, when uninstalled all the web
applications will be undeployed from tomcat 7. Use wdeploy utility to redeploy all the
applications again.
10