Transfer portal db to db2

在unix上,db2_dblibrary选择4的时候,2个jar文件之间用冒号 : 分割

在windows上用分号 ;分割.

 

db2 "CREATE DB wpsdb using codeset UTF-8 territory us COLLATE USING UCA400_NO PAGESIZE 8192"
db2 "UPDATE DB CFG FOR wpsdb USING applheapsz 4096"
db2 "UPDATE DB CFG FOR wpsdb USING app_ctl_heap_sz 1024"
db2 "UPDATE DB CFG FOR wpsdb USING stmtheap 8192"
db2 "UPDATE DB CFG FOR wpsdb USING dbheap 2400"
db2 "UPDATE DB CFG FOR wpsdb USING locklist 1000"
db2 "UPDATE DB CFG FOR wpsdb USING logfilsiz 1000"
db2 "UPDATE DB CFG FOR wpsdb USING logprimary 12"
db2 "UPDATE DB CFG FOR wpsdb USING logsecond 20"
db2 "UPDATE DB CFG FOR wpsdb USING logbufsz 32"
db2 "UPDATE DB CFG FOR wpsdb USING avg_appls 5"
db2 "UPDATE DB CFG FOR wpsdb USING locktimeout 30"

db2 "CREATE DB lkmddb using codeset UTF-8 territory us COLLATE USING UCA400_NO PAGESIZE 8192"
db2 "UPDATE DB CFG FOR lkmddb USING applheapsz 4096"
db2 "UPDATE DB CFG FOR lkmddb USING app_ctl_heap_sz 1024"
db2 "UPDATE DB CFG FOR lkmddb USING stmtheap 8192"
db2 "UPDATE DB CFG FOR lkmddb USING dbheap 2400"
db2 "UPDATE DB CFG FOR lkmddb USING locklist 1000"
db2 "UPDATE DB CFG FOR lkmddb USING logfilsiz 1000"
db2 "UPDATE DB CFG FOR lkmddb USING logprimary 12"
db2 "UPDATE DB CFG FOR lkmddb USING logsecond 20"
db2 "UPDATE DB CFG FOR lkmddb USING logbufsz 32"
db2 "UPDATE DB CFG FOR lkmddb USING avg_appls 5"
db2 "UPDATE DB CFG FOR lkmddb USING locktimeout 30"

db2 "CREATE DB fdbkdb using codeset UTF-8 territory us COLLATE USING UCA400_NO PAGESIZE 8192"
db2 "UPDATE DB CFG FOR fdbkdb USING applheapsz 4096"
db2 "UPDATE DB CFG FOR fdbkdb USING app_ctl_heap_sz 1024"
db2 "UPDATE DB CFG FOR fdbkdb USING stmtheap 8192"
db2 "UPDATE DB CFG FOR fdbkdb USING dbheap 2400"
db2 "UPDATE DB CFG FOR fdbkdb USING locklist 1000"
db2 "UPDATE DB CFG FOR fdbkdb USING logfilsiz 1000"
db2 "UPDATE DB CFG FOR fdbkdb USING logprimary 12"
db2 "UPDATE DB CFG FOR fdbkdb USING logsecond 20"
db2 "UPDATE DB CFG FOR fdbkdb USING logbufsz 32"
db2 "UPDATE DB CFG FOR fdbkdb USING avg_appls 5"
db2 "UPDATE DB CFG FOR fdbkdb USING locktimeout 30"

db2 "CREATE DB jcrdb using codeset UTF-8 territory us COLLATE USING UCA400_NO PAGESIZE 8192"
db2 "UPDATE DB CFG FOR jcrdb USING applheapsz 4096"
db2 "UPDATE DB CFG FOR jcrdb USING app_ctl_heap_sz 1024"
db2 "UPDATE DB CFG FOR jcrdb USING stmtheap 8192"
db2 "UPDATE DB CFG FOR jcrdb USING dbheap 2400"
db2 "UPDATE DB CFG FOR jcrdb USING locklist 1000"
db2 "UPDATE DB CFG FOR jcrdb USING logfilsiz 1000"
db2 "UPDATE DB CFG FOR jcrdb USING logprimary 12"
db2 "UPDATE DB CFG FOR jcrdb USING logsecond 20"
db2 "UPDATE DB CFG FOR jcrdb USING logbufsz 32"
db2 "UPDATE DB CFG FOR jcrdb USING avg_appls 5"
db2 "UPDATE DB CFG FOR jcrdb USING locktimeout 30"

 

cmds to configure jcrdb:

db2 "update db cfg for jcrdb using sheapthres_shr 50000"
db2 "CONNECT TO jcrdb USER db2admin USING passw0rd"
db2 "CREATE BUFFERPOOL ICMLSFREQBP4 SIZE 1000 PAGESIZE 4 K"
db2 "CREATE BUFFERPOOL ICMLSVOLATILEBP4 SIZE 8000 PAGESIZE 4 K"
db2 "CREATE BUFFERPOOL ICMLSMAINBP32 SIZE 8000 PAGESIZE 32 K"
db2 "CREATE BUFFERPOOL CMBMAIN4 SIZE 1000 PAGESIZE 4 K"
db2 "CREATE REGULAR TABLESPACE ICMLFQ32 PAGESIZE 32 K MANAGED BY SYSTEM  USING  ('ICMLFQ32') BUFFERPOOL ICMLSMAINBP32"
db2 "CREATE REGULAR TABLESPACE ICMLNF32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('ICMLNF32') BUFFERPOOL ICMLSMAINBP32"
db2 "CREATE REGULAR TABLESPACE ICMVFQ04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('ICMVFQ04') BUFFERPOOL ICMLSVOLATILEBP4"
db2 "CREATE REGULAR TABLESPACE ICMSFQ04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('ICMSFQ04') BUFFERPOOL ICMLSFREQBP4"
db2 "CREATE REGULAR TABLESPACE CMBINV04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('CMBINV04') BUFFERPOOL CMBMAIN4"
db2 "CREATE SYSTEM TEMPORARY TABLESPACE ICMLSSYSTSPACE32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('icmlssystspace32') BUFFERPOOL ICMLSMAINBP32"
db2 "CREATE SYSTEM TEMPORARY TABLESPACE ICMLSSYSTSPACE4 PAGESIZE 4 K MANAGED BY SYSTEM USING ('icmlssystspace4') BUFFERPOOL ICMLSVOLATILEBP4"
db2 "DISCONNECT jcrdb"
db2 "TERMINATE"

 

Update wkplc.properties, wkplc_comp.properties and wkplc_dbtype.properties

./ConfigEngine.sh validate-database-driver -DTransferDomainList=release,customization,community,
jcr,feedback,likeminds
./ConfigEngine.sh validate-database-connection -DTransferDomainList=release,customization,community,
jcr,feedback,likeminds

Stop both WebSphere Application Server and the WebSphere Portal server

./ConfigEngine.sh database-transfer -DTransferDomainList=release,customization,community,jcr,
feedback,likeminds

After transferring the database tables, perform a reorg check to improve performance

 

 

The follwoing is writed by xuli:

 

 

Setting up a production environment on AIX

Preparing the WebSphere Application Server Deployment Manager on AIX
Install WebSphere Application Server Network Deployment

Choose manageprofile commands to create a default deployment manager profile

Run the following command to start the deployment manager: ./startManager.sh, from the dmgr_profile_root\bin directory.
Log into the deployment manager administrative console.

Increase the HTTP connection timeouts for the deployment manager.
   1. Click System Administration > Deployment Manager > Web container transport chains.
   2. Increase the timeout values. For the WCInboundAdmin and WCInboundAdminSecure entries listed in the web container transport chains section, complete the following steps to increase the timeout values:
         1. Click HTTP Inbound Channel.
         2. Change the Read timeout value to 180.
         3. Change the Write timeout value to 180.
         4. Save the configuration changes.

Change the timeout request period for the Java Management Extensions (JMX) connector.
   1. Click System administration > Deployment Manager > Administration Services > JMX connectors > SOAPConnector > Custom Properties.
   2. Select the requestTimeout property, and increase the value from 600 to 6000.
   3. Save the configuration changes.

Click System administration > Deployment manager > Java and Process Management > Process Definition > Java Virtual Machine.
Update the value in the Maximum Heap Size field. Click OK, and then save your changes.

Change the timeout request period for the Simple Object Access Protocol (SOAP) client. Edit the soap.client.props file, located in the Dmgr_profile/properties directory:
Change the line to: com.ibm.SOAP.requestTimeout=6000.

Preparing the primary node on AIX
Installing WebSphere Portal on AIX

Configuring WebSphere Portal to use DB2

Creating remote databases

Run the following commands on the DB2 server system to create the necessary databases:
db2 "CREATE DB dbname using codeset UTF-8 territory us PAGESIZE 8192"
db2 "UPDATE DB CFG FOR dbname USING applheapsz 4096"
db2 "UPDATE DB CFG FOR dbname USING app_ctl_heap_sz 1024"
db2 "UPDATE DB CFG FOR dbname USING stmtheap 32768"
db2 "UPDATE DB CFG FOR dbname USING dbheap 2400"
db2 "UPDATE DB CFG FOR dbname USING locklist 1000"
db2 "UPDATE DB CFG FOR dbname USING logfilsiz 4000"
db2 "UPDATE DB CFG FOR dbname USING logprimary 12"
db2 "UPDATE DB CFG FOR dbname USING logsecond 20"
db2 "UPDATE DB CFG FOR dbname USING logbufsz 32"
db2 "UPDATE DB CFG FOR dbname USING avg_appls 5"
db2 "UPDATE DB CFG FOR dbname USING locktimeout 30"
db2 "UPDATE DB CFG FOR dbname using AUTO_MAINT off"

Complete the following:

   1. On the DB2 server system, run the following commands. This step is only required for the IBM Java Content Repository database (jcrdb).
      db2 "CONNECT TO jcrdb USER jcr USING dbpassword"
      db2 "CREATE BUFFERPOOL ICMLSFREQBP4 SIZE 1000 PAGESIZE 4 K"
      db2 "CREATE BUFFERPOOL ICMLSVOLATILEBP4 SIZE 8000 PAGESIZE 4 K"
      db2 "CREATE BUFFERPOOL ICMLSMAINBP32 SIZE 8000 PAGESIZE 32 K"
      db2 "CREATE BUFFERPOOL CMBMAIN4 SIZE 1000 PAGESIZE 4 K"
      db2 "CREATE REGULAR TABLESPACE ICMLFQ32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('ICMLFQ32') BUFFERPOOL ICMLSMAINBP32"
      db2 "CREATE REGULAR TABLESPACE ICMLNF32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('ICMLNF32') BUFFERPOOL ICMLSMAINBP32"
      db2 "CREATE REGULAR TABLESPACE ICMVFQ04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('ICMVFQ04') BUFFERPOOL ICMLSVOLATILEBP4"
      db2 "CREATE REGULAR TABLESPACE ICMSFQ04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('ICMSFQ04') BUFFERPOOL ICMLSFREQBP4"
      db2 "CREATE REGULAR TABLESPACE CMBINV04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('CMBINV04') BUFFERPOOL CMBMAIN4"
      db2 "CREATE SYSTEM TEMPORARY TABLESPACE ICMLSSYSTSPACE32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('icmlssystspace32') BUFFERPOOL ICMLSMAINBP32"
      db2 "CREATE SYSTEM TEMPORARY TABLESPACE ICMLSSYSTSPACE4 PAGESIZE 4 K MANAGED BY SYSTEM USING ('icmlssystspace4') BUFFERPOOL ICMLSVOLATILEBP4"

      db2 "DISCONNECT jcrdb"
      db2 "TERMINATE"

   2. On the DB2 server system, check the services file. If it does not specify DB2 connection and interrupt service ports, specify the ports for your operating system:
      Use a text editor to open the file /etc/services and add the following text (where db2inst1 is the name of the DB2 instance ID on the system): db2c_db2inst1 50000/tcp # DB2 connection service port db2i_db2inst1 50001/tcp # DB2 interrupt service port

On the DB2 server system, set DB2COMM to TCP/IP by using the db2set command: db2set DB2COMM=TCPIP

Modifying database properties

Update wkplc.properties, wkplc_comp.properties and wkplc_dbtype.properties

./ConfigEngine.sh validate-database-driver -DTransferDomainList=release,customization,community,
jcr,feedback,likeminds
./ConfigEngine.sh validate-database-connection -DTransferDomainList=release,customization,community,
jcr,feedback,likeminds

Stop both WebSphere Application Server and the WebSphere Portal server

./ConfigEngine.sh database-transfer -DTransferDomainList=release,customization,community,jcr,
feedback,likeminds

After transferring the database tables, perform a reorg check to improve performance

Configuring the primary node to communicate with the deployment manager on AIX
Perform the following steps to collect files from the primary node and copy them to the deployment manager:
   1. Run the ./ConfigEngine.sh collect-files-for-dmgr -DWasPassword=password task, from the wp_profile_root/ConfigEngine directory of the primary node, to create a zip file containing all the files which need to be copied to the Deployment Manager.
      Note: The zip file will be placed in the wp_profile_root/filesForDmgr directory and the file will be called filesForDmgr.zip.
   2. Stop the deployment manager.
   3. Expand each of the files in the filesForDmgr.zip file into the proper location on the Deployment Manager based on the directory names within the zip file. The directory names in the zip file are based on the typical default directory names. The directory called "AppServer/profiles/Dmgr01" is used to identify the Deployment Manager profile root, and the "AppServer" directory is used to identify the Deployment Manager installation root directory. If the Deployment Manager was installed into the default directory (AppServer) and the profile was created in the default directory (AppServer/profiles/Dmgr01), then the zip file can be expanded directly into the directory above the AppServer directory; for example /IBM/WebSphere.
   4. Start the deployment manager.

Verify that the following properties are set in the wkplc.properties file, located in the wp_profile_root/ConfigEngine/properties directory of the primary node:
   1. Verify that WasPassword is set to your WebSphere Application Server password.
   2. Verify that PortalAdminPwd is set to your WebSphere Portal password.
   3. Verify that WasRemoteHostName is set to the fully qualified hostname of the deployment manager.
   4. Verify that WasSoapPort is set to the SOAP port that the deployment manager is using; the default value is 8879.
   5. Verify that PrimaryNode is set to true.
   6. Verify that ClusterName is set.

Creating a static cluster on AIX
Stop the server1 and WebSphere_Portal servers on the primary node and ensure that the following parameters are set correctly in the wkplc.properties file, located in the wp_profile_root/ConfigEngine/properties directory:
    * Set WasSoapPort to the port used to connect remotely to the WebSphere Application Server.
    * Set WasRemoteHostName to the full hostname of the server used to remotely connect to the WebSphere Application Server.

./ConfigEngine.sh cluster-node-config-pre-federation -DDMgrUserid=dmgr_userid -DDMgrPassword=dmgr_pw

./ConfigEngine.sh cluster-node-config-post-federation

./ConfigEngine.sh wp-change-portal-admin-user -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroup

./ConfigEngine.sh cluster-node-config-cluster-setup

Configuring a Web server and a deployment manager profile on the same machine
Install the IBM HTTP Server

Launch the Plug-ins installation wizard on the machine with the Web server

Copy configurewebserver1.sh script from <plugin_root>/bin to <was_root>/bin on Deployment Manager

Run configurewebserver1.sh

Configuring a stand-alone LDAP user registry on AIX
Preparing a Tivoli Directory Server

Update wkplc.properties file
    * standalone.ldap.id
    * standalone.ldap.host
    * standalone.ldap.port
    * standalone.ldap.bindDN
    * standalone.ldap.bindPassword
    * standalone.ldap.ldapServerType
    * standalone.ldap.userIdMap
    * standalone.ldap.groupIdMap
    * standalone.ldap.groupMemberIdMap
    * standalone.ldap.userFilter
    * standalone.ldap.groupFilter
    * standalone.ldap.serverId
    * standalone.ldap.serverPassword
    * standalone.ldap.realm
    * standalone.ldap.primaryAdminId
    * standalone.ldap.primaryAdminPassword
    * standalone.ldap.primaryPortalAdminId
    * standalone.ldap.primaryPortalAdminPassword
    * standalone.ldap.primaryPortalAdminGroup
    * standalone.ldap.baseDN

    * standalone.ldap.et.group.searchFilter
    * standalone.ldap.et.group.objectClasses
    * standalone.ldap.et.group.objectClassesForCreate
    * standalone.ldap.et.group.searchBases
    * standalone.ldap.et.personaccount.searchFilter
    * standalone.ldap.et.personaccount.objectClasses
    * standalone.ldap.et.personaccount.objectClassesForCreate
    * standalone.ldap.et.personaccount.searchBases

    * standalone.ldap.gm.groupMemberName
    * standalone.ldap.gm.objectClass
    * standalone.ldap.gm.scope
    * standalone.ldap.gm.dummyMember
 
    * standalone.ldap.personAccountParent
    * standalone.ldap.groupParent
    * standalone.ldap.personAccountRdnProperties
    * standalone.ldap.groupRdnProperties

./ConfigEngine.sh validate-standalone-ldap -DWasPassword=password
./ConfigEngine.sh wp-modify-ldap-security -DWasPassword=password

Choose the following options to propagate the security changes:
Clustered environment  Run the following tasks to propagate the security changes in a clustered environment:
   1. ./stopManager.sh, from the dmgr_profile_root\bin directory
   2. ./stopNode.sh -username admin_userid -password admin_password, from the wp_profile_root/bin directory
   3. ./stopServer.sh server1 -username admin_userid -password admin_password, from the wp_profile_root/bin directory
   4. ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password, from the wp_profile_root/bin directory
   5. ./startManager.sh, from the dmgr_profile_root\bin directory
   6. ./startNode.sh, from the wp_profile_root/bin directory
   7. ./startServer.sh server1, from the wp_profile_root/bin directory
   8. ./startServer.sh WebSphere_Portal, from the wp_profile_root/bin directory

./ConfigEngine.sh wp-validate-standalone-ldap-attribute-config -DWasPassword=password

Preparing additional nodes on AIX
Installing WebSphere Portal on AIX

Adding additional nodes to the static cluster on AIX

copy the JDBC Type 4 jar files to the secondary node from the DB2 server.

Set all database properties in the wkplc_dbtype.properties and wkplc_comp.properties files with the appropriate values from the primary node.

Verify that the following properties are set in the wkplc.properties file, located in the wp_profile_root/ConfigEngine/properties directory of the secondary node:

   1. Verify that WasUserid is set to your WebSphere Application Server administrator ID.
   2. Verify that WasPassword is set to your WebSphere Application Server password.
   3. Verify that PortalAdminId is set to your WebSphere Portal administrator ID.
   4. Verify that PortalAdminPwd is set to your WebSphere Portal password.
   5. Verify that WasRemoteHostName is set to the fully qualified hostname of the deployment manager.
   6. Verify that WasSoapPort is set to the SOAP port that the deployment manager is using; the default value is 8879.
   7. Verify that PrimaryNode is set to false.
   8. Verify that ClusterName is set to the primary node's ClusterName.

Run the following tasks to validate your database settings:

   1. ./ConfigEngine.sh validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds
   2. ./ConfigEngine.sh validate-database-connection -DWasPassword=password -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

./ConfigEngine.sh cluster-node-config-pre-federation -DDMgrUserid=dmgr_userid -DDMgrPassword=dmgr_pw

./ConfigEngine.sh cluster-node-config-post-federation

./ConfigEngine.sh wp-change-portal-admin-user -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroup
comment: make sure node agent is started on additional node server
./ConfigEngine.sh cluster-node-config-cluster-setup

Wait at least 30 minutes before stopping and restarting the deployment manager because the node agent runs a background thread to expand all EAR files into their target directories.
Note: Attempting to restart the deployment manager while the expansion is in process can result in an unusable application. Although the time to complete an EAR expansion is environment-dependent, a 30 minute wait is sufficient for a typical environment.

Run the following tasks, from the wp_profile_root/bin directory, to propagate your changes:
   1. ./stopManager.sh, from the dmgr_profile_root\bin directory
   2. ./stopNode.sh -username admin_userid -password admin_password, from the wp_profile_root/bin directory
   3. ./stopServer.sh server1 -username admin_userid -password admin_password
   4. ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
   5. ./startManager.sh, from the dmgr_profile_root\bin directory
   6. ./startNode.sh, from the wp_profile_root/bin directory
   7. ./startServer.sh server1
   8. ./startServer.sh WebSphere_Portal

Perform the following steps to synchronize the nodes:
   1. Log in to the deployment manager administrative console.
   2. Select System Administration > Nodes, select the node from the list, and then click Full Resynchronize.