MPA Installation on StandAlone Server
This is an immaculate record describes how to install Mobile Portal Accelerator on a stand-alone server.
This installation takes into account database as DB2 and Mobile Portal Accelerator version 7.0 and 7.0.1 .
Pre-Reqs :
1. Install WebSphere Application Server /WebSphere Portal along with any applicable fix packs.
2. Install Java™ SDK service release if it is not already installed.
3. To ensure that WebSphere Portal is running without errors check the logs for errors as shown in the following example:
Log in to WebSphere Portal as administrator and view pages.
Check the following log file:
wp_profile_root/logs/WebSphere_Portal/SystemOut.log
4. Install the database DB2 (in this case),Create all Dbs and do the DB migration.
5. Refer the link below to configure WebSphere Portal to use Database.
Please refer the DOC (ConfigureWeb Sphere Portal to use DB2.doc) :
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/MPA_Installation_on_StandAlone__Server_with_DB2
Before you Proceed please verify
Ø Portal version
Ø WAS version
Ø DB version
Check out the below link for Mobile Portal Accelerator V7.0 h/w and s/w requirements :
http://www-01.ibm.com/support/docview.wss?uid=swg27019887 –
An Overview :
MPA | Portal Server Enable | WebSphere Application Servers | Database -DB2 | Database-Oracle | WebServer |
|
|
|
|
|
|
|
|
MPA 615 | V6.1.05 and V6.1.5.2 | WebSphere Application Server V7.0.0.11 with IBM SDK 1.6 SR12
Or
WebSphere Application Server V6.1.0.31 with IBM SDK 1.5 SR7
| DB2 V9.7 FP1
DB2 V9.5 FP5 Workgroup Server Edition
DB2 V9.1 FP9
| Oracle 11gR2 V11.2.0.1 (including RAC)
Oracle 11gR1 V11.1.0.7 (including RAC)
| IBM HTTP Server for WAS V7.0 and 6.1 |
|
MPA V7.0 | V7.0 | 7.0.0.11
Apply Java SDK along with WAS FP
(UpdateInstaller V7.0.0.13 needed to Upgrade Fix packs)
| DB2 9 for 9.1.0.9
DB2 9 for 9.5.0.5
DB2 Enterprise Server Edition 9.7.0.1
| Oracle 10g or Oracle 11g Enterprise /Standarad Edition 11.1.0.6/11.1.0.7/11.2.0.1 | IBM HTTP Server 7.0
IBM HTTP Server 6.1
|
|
MPA V7.0.1 | V7.0.0.1 | 7.0.0.13
Apply Java SDK along with WAS FP
(UpdateInstaller V7.0.0.13 needed to Upgrade Fix packs)
| DB2 9 for 9.1.0.9
DB2 9 for 9.5.0.5
DB2 Enterprise Server Edition 9.7.0.1
| Oracle 10g or Oracle 11g Enterprise Edition 11.1.0.6 /11.1.0.7 / 11.2.0.2
Also Oracle 11g Standard Edition 11.2.0.2
| IBM HTTP Server 7.0
IBM HTTP Server 6.1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6. Check out Portal page is coming properly with no error in the logs after db migration.
After All these required steps now proceed to MPA installation.
MPA Installation Steps :
1.Unzip wp.mobile.zip to your local directory.
2. Switch to the ConfigEngine Directory:
$ cd /opt/IBM/WebSphere/wp_profile/ConfigEngine
Run the following command to register the mobile portal assembly with WebSphere Portal
./ConfigEngine.sh -install -assemblyIudd sdd.xml -assemblyRoot /tmp/wp.mobile -installLocation /IBM/WebSphere -offeringName PortalServer
3. Follow the MCS and MWP installation procedures, with the following change
4. Create MCS DB
Ø Log in as the DB2 instance user su – db2instance_userID e.g su – db2inst1
Ø Run the db2start command to ensure db2 is started
Ø Create a new database and update the database configuration using the following command.
db2 create db mcs using codeset UTF-8 territory us
db2 update db cfg for mcs using logfilsiz 10000 logprimary 10 logsecond 10
Ø Connect to the mcs database
db2 connect to mcs user db2instance_userID using db2instance_password
e.g db2 connect to mcs user db2inst1 using
passwordØ If your database server is on the same server as WebSphere Portal, change the working directory to:
wp_root/wp.mobile/wp.mobile.mcs/repository/db2
Otherwise, copy the file wp_root/wp.mobile/wp.mobile.mcs/repository/db2/create_vm_tables.sql from your WebSphere Portal server to a directory on your database server. Then, make that directory your working directory.
Ø Create the WebSphere Portal tables using the following command.
db2 -tf create_vm_tables.sql
Ø If you used the su command when you logged in as the DB2 instance user, issue the exit command.
5. Change your working directory to
wp_profile_root/ConfigEngine.
6. Make sure that the correct values are specified for WAS and Portal password in the file
wp_profile_root/ConfigEngine/properties/wkplc.properties
7. Run the following command :
./ConfigEngine.sh init mcs-deploy-mcs -DMcsRepositoryType=odbc -DMcsDbVendor=db_vendor -DMcsDbHost=hostname -DMcsDbPort=port_number - DMcsDbSource=db_name -DMcsDbUser=db2instance -DMcsDbPassword=db2instance_password -DMcsProject=mobile-portal
You must specify mobile-portal as the project name. Definitions for the variable parameters follow.
· db_vendor: db2-type4
· hostname: the fully qualified host name of the database server.
· port_number: the port number used by the JDBC applet ("net") driver on the database server for the MCS database. Use 50000—unless another application (including another database instance) is already using that port.
· db_name: the name of the MCS database
· db2instance: the user ID of the DB2 instance user.
· db2instance_password: the DB2 instance password for the MCS database
e.g
./ConfigEngine.sh init mcs-deploy-mcs -DMcsRepositoryType=odbc -DMcsDbVendor=db2-type4 -DMcsDbHost=wpmls10.in.ibm.com -DMcsDbPort=50000 -DMcsDbSource=mcs -DMcsDbUser=db2inst1 -DMcsDbPassword=
password -DMcsProject=mobile-portal
8. Using a text editor, open the ImportPolicies script or batch file in the wp_root/wp.mobile/wp.mobile.mcs/repository/bin directory. Add the path to the database driver to the end of the JDBC_DRIVER= line as illustrated in this example.
(for version 9.1 (with fix pack 5) or 9.5 (with fix pack 3))
:db_root/db2instance/sqllib/java/db2jcc.jar:db_root/db2instance/sqllib/java/db2jcc_license_cu.jar
(for version 9.7)
:db_root/db2instance/sqllib/java/db2jcc4.jar:db_root/db2instance/sqllib/java/db2jcc_license_cu.jar
9. To import default device policies, run the following command:
./ConfigEngine.sh init mcs-import-devices -DMcsProject=mobile-portal
10. Restart the servers. (server1 & WebSphere_Portal)
11. Check out SystemOut logs ,there should not be any exception.
Installation of MWP
1) ./ConfigEngine.sh mwp-config-all
2) ./ConfigEngine.sh mwp-import-policies
3) ./ConfigEngine.sh mwp-import-portlet-policies
4) Restart Servers ( WebSphere Portal and Server1)
5) No errors reflect on SystemOut logs.
6) Browse MMP page on WebSphere Portal and try to render it on any User Agent ,if MPA installation is successful page will render without any error in the logs.
Uninstallation MWP/MCS
1. ./ConfigEngine.sh mwp-uninstall
{ Set -DPortalAdminPwd=
password -DWasPassword=
password in wkplc.properties}
3. ./ConfigEngine.sh init mcs-uninstall-mcs -DskipCleanup=true
4. ./ConfigEngine.sh -uninstall -assemblyList wp.mobile
5. Drop the mcs db in DB server.
db2 drop database mcs
db2 list db directory