portal群集安装文档

Portal群集安装手册一、 安装准备安装环境如下：两台Portal服务器+一台Oracle服务器+AD LDAP服务器其中：34 服务器安装以下软件：IBM WebSphere Portal IBM WebSphere Network Deployment IBM Http Web Server 35 服务器安装以下软件：IBM WebSphere Portal IBM Http Web Server而I解析为34.数据库服务器：59 sid:bpm二、 Portal1安装步骤1、 执行install.sh2、 选择Portal Enable 版本Wpadmin/password3、 安装完成。4、 升级Portal升级WAS安装WAS 升级程序IBM Update Installer for WebSphere Software之后，运行安装程，启动升级程序界面升级portal安装成功结束。安装CF4 package三、 Portal2的安装1、 执行安装脚本2、 升级WAS的补丁。参考Portal1的升级3、 升级Portal的补丁。参考 Portal1的升级四、 安装ND 部署平台使用IL-2的安装盘，执行如程序：按照WAS升级的方法升级ND.五、 安装IBM HTTP ServerPortal2主机安装执行脚本Ihsadmin/password在Portal2服务器上安装,需要把Web 服务器定义为webserver2.把configurewebserver2.sh 复制到/websphere/appserver/bin在WebSphere/AppServer/bin目录修改configurewebserver2.sh文件如下部分,把主机名替换为门户的主机名,保持一致./wsadmin.sh $PROFILE_NAME_PARAMETER $WSADMIN_USERID_PARAMETER $WSADMIN_PASSWORD_PARAMETER -f $WAS_HOME/bin/configureWebserverDefinition.jacl webserver2 IHS /home/WebSphere/HTTPServer /home/WebSphere/HTTPServer/conf/httpd.conf 80 MAP_ALL /home/WebSphere/HTTPServer/Plugins unmanaged -node linux 8008 ihsadmin $IHS_ADMIN_PASSWORD_PARAMETER在/WebSphere/wp_profile/bin目录执行. ./setupCmdLine.sh 初始化环境确认门户系统已经启动,确保server1已经启动.改变目录到/websphere/AppServer/bin目录执行如下脚本:./configurewebserver2.sh结束,重新启动门户,不启动server1.类似方法创建portal1服务器的IBM Web Server.六、 迁移数据库1、 迁移数据库前的准备# Locate the following files and create a backup copy of each before changing any values: * wp_profile_root/ConfigEngine/properties/perties * wp_profile_root/ConfigEngine/properties/wkplc_perties * wp_profile_root/ConfigEngine/properties/wkplc_perties * If you are transferring from a database other than Derby: wp_profile_root/ConfigEngine/properties/wkplc_sourceDpertiesDefault values are listed in these files. Unless otherwise noted, all values are of type alphanumeric text string. Print out the steps below for reference before modifying the properties files. Make sure to enter the appropriate values for each instance of each property. In wkplc_perties, most properties are repeated for each domain.# Use a text editor to open the properties file wkplc_perties and modify the values to correspond to your environment. 1). For dbdomain.DbType, type oracle. 2). For dbdomain.DbName, type the name of the WebSphere Portal domain database. Note: This value is also the database element in the dbdomain.DbUrl property. 3). For dbdomain.DbSchema, type the schema name of the database domain. Note: Review your target database management system documentation to define a valid schema name. Some database management systems have schema name restrictions that you need to understand. The dbdomain.DbName should be the same value used for the dbdomain.DbSchema 4). For dbdomain.DataSourceName, type the name of the data source that WebSphere Portal uses to communicate with its databases. Do not use the following reserved words: * releaseDS * communityDS * customizationDS * jcrDS * lmdbDS * feedback 5). For dbdomain.DbUrl, type the database URL used to access the WebSphere Portal database with JDBC. The value must conform to the JDBC URL syntax specified by the database. Note: * The database element of this value should match the value of DbName. * For Oracle RAC only, the WebSphere Portal server must explicitly connect to one RAC node during database transfer. You need to specify the information of one Oracle RAC node as if it is the only database server. For example, the Oracle database URL should look like the following: jdbc:oracle:thin:PRIMARY_NODE_HOSTNAME:1521:PRIMARY_NODE_INSTANCENAME. When database transfer is completed, the WebSphere Portal server will be configured to use this single database server. 6). For dbdomain.DbUser, type the user ID for the database configuration user. 7). For dbdomain.DbPassword, type the password for the database configuration user. 8). For dbdomain.DbConfigRoleName, type the name of the group for database configuration users. Database rights are granted to this group instead of individuals. The user specified for dbdomain.DbUser must be assigned to this group. 9). Optional: For dbdomain.DbRuntimeUser, type the user ID of the database user that should be used by WebSphere Portal to connect to the database at runtime. If no value is specified for this setting, the database configuration user will be used to connect to the databases at runtime. 10). If dbdomain.DbRuntimeUser is specified, you must set dbdomain.DbRuntimePassword to be the password of the runtime database user. 11). For dbdomain.DbRuntimeRoleName, type the name of the group for database runtime users. Database rights are granted to this group instead of individuals. The user specified for dbdomain.DbRuntimeUser must be assigned to this group. 12). Optional: For dbdomain.DBA.DbUser, type the database administrator user ID for privileged access operations during database creation. If you do not need this parameter, you can either accept the default value or leave blank. 13). Optional: For dbdomain.DBA.DbPassword, type the database administrator password for privileged access operations during database creation. If you do not need this parameter, you can either accept the default value or leave blank. 14). For dbdomain.DbHome, type the root location for the database. Note: This value is used to specify the location to create the tablespaces.# Save and close the file.# Update the following properties in the file wkplc_perties. 1. For oracle.DbDriver, type the name of the Oracle JDBC driver class. 2. For oracle.DbLibrary, type the directory and name of the .jar file that contains the JDBC driver class. 3. For oracle.JdbcProviderName, type the name of the JDBC provider that WebSphere Portal uses to communicate with its databases.# Save and close the file.Example:#wkplc_perties文件oracle.DbDriver=oracle.jdbc.OracleDriveroracle.DbLibrary=/home/WebSphere/lib/ojdbc6.jaroracle.JdbcProviderName=wpdbJDBC_oracle# wkplc_perties文件feedback.DbType=oraclefeedback.DbName=bpmfeedback.DbSchema=fdusrfeedback.DataSourceName=fdDSfeedback.DbUrl=jdbc:oracle:thin::1521:bpmfeedback.DbUser=fdusrfeedback.DbPassword=fdusrfeedback.DbConfigRoleName=WP_PZN_CONFIG_USERSfeedback.DbRuntimeRoleName=WP_PZN_RUNTIME_USERSlikeminds.DbType=oraclelikeminds.DbName=bpmlikeminds.DbSchema=lmusrlikeminds.DataSourceName=lmDSlikeminds.DbUrl=jdbc:oracle:thin::1521:bpmlikeminds.DbUser=lmusrlikeminds.DbPassword=lmusrlikeminds.DbConfigRoleName=WP_PZN_CONFIG_USERSlikeminds.DbRuntimeRoleName=WP_PZN_RUNTIME_USERSrelease.DbType=oraclerelease.DbName=bpmrelease.DbSchema=relusrrelease.DataSourceName=relDSrelease.DbUrl=jdbc:oracle:thin::1521:bpmrelease.DbUser=relusrrelease.DbPassword=relusrrelease.DbConfigRoleName=WP_BASE_CONFIG_USERSrelease.DbRuntimeRoleName=WP_BASE_RUNTIME_USERScommunity.DbType=oraclecommunity.DbName=bpmcommunity.DbSchema=comusrcommunity.DataSourceName=comDScommunity.DbUrl=jdbc:oracle:thin::1521:bpmcommunity.DbUser=comusrcommunity.DbPassword=comusrcommunity.DbConfigRoleName=WP_BASE_CONFIG_USERScommunity.DbRuntimeRoleName=WP_BASE_RUNTIME_USERScustomization.DbType=oraclecustomization.DbName=bpmcustomization.DbSchema=cususrcustomization.DataSourceName=cusDScustomization.DbUrl=jdbc:oracle:thin::1521:bpmcustomization.DbUser=cususrcustomization.DbPassword=cususrjcr.DbType=oraclejcr.DbName=bpmjcr.DbSchema=jcrusrjcr.DataSourceName=jcrdbDSjcr.DbUrl=jdbc:oracle:thin::1521:bpmjcr.DbUser=jcrusrjcr.DbPassword=jcrusrjcr.DbConfigRoleName=WP_JCR_CONFIG_USERSjcr.DbRuntimeRoleName=WP_JCR_RUNTIME_USERS# Update the WasPassword value in the perties file. This value is the password for the WebSphere Application Server security authentication used in your environment.# Save and close the file.2、 创建用户六个用户：ComUsrCususrRelusrJcrusrFdusrLmusr分别授予resource,connect权限,互相之间能查看表、视图等权限。同时赋予以下权限GRANT UNLIMITED TABLESPACE TO GRANT CREATE TABLE, CREATE TABLESPACE, CREATE ANY INDEX, CREATE SEQUENCE, CREATE TRIGGER, CREATE TYPE, CREATE VIEW, CREATE SESSIONTO ;GRANT SELECT ON DBA_PENDING_TRANSACTIONSTO ;3、 执行脚本./ConfigEngine.sh create-jcr-jms-resources-post-dbxfer command to create JMS resources in the new database.Note: Regardless of the method used to transfer data (configuration wizard or the steps in this topic), you must run this task to create JMS resources.七、 构建群集1. 准备工作# Run the ./ConfigEngine.sh enable-profiles -DWasPassword=password task, from the wp_profile_root/ConfigEngine directory of the profile that you will use as the primary node of the cluster. This command creates a configuration archive (CAR) file that is used to create additional WebSphere Portal profiles. The Portal.car file is saved to the PortalServer_root/profileTemplates/default.portal/configArchives directory.Type 4 database drivers only: If you configured WebSphere Portal for a remote database and placed your database drivers inside of the wp_profile_root/PortalServer directory, they will be included in the configuration archive file that is created when running the enable-profiles script.# Run the ./ConfigEngine.sh package-profiles -DWasPassword=password task to zip the profileTemplates directory and create a profileTemplates.zip file in the PortalServer_root/profileTemplates directory.2. Removing search collections on Linux在门户管理后台,删除搜索结果集合.删除后的界面.同时通过如下设置,禁用定时的搜索.Open the perties file, located in the wp_profile_root/PortalServer/jcr/lib/com/ibm/icm/ directory, and set the jcr.textsearch.enabled property to false更新为false3. 准备 ND#把主节点上的/WebSphere/PortalServer/filesForDmgr/filesForDmgr.zip 复制到 ND服务器并解开放到ND目录,例如: /opt/IBM/WebSphere/AppServer #启动ND #执行以下脚本,./manageprofiles.sh -augment -templatePath /home/ND/AppServer/profileTemplates/management.portal.augment-profileName Dmgr01注意:如果这一步错误,请重新创建ND的profile,如下:1) 删除ND上所有的Profile./manageprofiles.sh -deleteAll2) 增加Dmgr01 Profile./manageprofiles.sh -create -templatePath /home/ND/AppServer/profileTemplates/management -hostName -profileName Dmgr01 -profilePath /home/ND/AppServer/profiles/Dmgr01 -cellName ndCell -nodeName ndNode-enableAdminSecurity true -adminUserName wpadmin -adminPassword password3) 重新解开filesForDmgr.zip4) 重新执行以下步骤./manageprofiles.sh -augment -templatePath /home/ND/AppServer/profileTemplates/management.portal.augment-profileName Dmgr01重新启动 ND.4. 加入主节点执行如下脚本:./addNode.sh 8879 -includeapps -includebuses -username wpadmin -password password5. 修改主节点相关参数修改文件perties如下参数：l # Set WasSoapPort to the port used to connect remotely to the deployment manager. （8879）l # Set WasRemoteHostName to the full host name of the server used to remotely connect to the deployment manager.l # Verify that WasUserid is set to your Deployment Manager administrator user ID.l # Verify that WasPassword is set to your Deployment Manager administrator password.l # Verify that PortalAdminPwd is set to your WebSphere Portal administrator password.l # Verify that ClusterName is set.l # Verify that PrimaryNode is set to true.Example:WasSoapPort=8879WasRemoteHostName=ServerName=WebSphere_PortalWasUserid=uid=wpadmin,o=defaultWIMFileBasedRealmWasPassword=passwordPortalAdminId=wpadminPortalAdminPwd=passwordClusterName=PortalClusterPrimaryNode=true6. 创建静态群集执行以下脚本:./ConfigEngine.sh cluster-node-config-post-federation./ConfigEngine.sh cluster-node-config-cluster-setup -DWasPassword=dmgr_password7. 配置ND控制台删除Portal的JCRSeedBus八、 启用安全性Tip: Perform these steps on the primary node only.Note: Use the wp_add_federated_perties helper file, located in the wp_profile_root/ConfigEngine/config/helpers directory, when performing this task to ensure the correct properties are entered. In the instructions below, when the step refers to the perties file, you will use your wp_add_federated_perties helper file.# Use a text editor to open the perties file, located in the wp_profile_root/ConfigEngine/properties directory.# Required: Enter a value for the following required parameters in the perties file under the VMM Federated LDAP Properties heading:Note: See the properties file for specific information about the required parameters and for advanced parameters. * federated.ldap.id * federated.ldap.host * federated.ldap.port * federated.ldap.bindDN * federated.ldap.bindPassword * federated.ldap.ldapServerType * federated.ldap.baseDN# Required: Enter a value for the following required entity types parameters in the perties file under the LDAP entity types heading:Note: See the properties file for specific information about the required parameters and for advanced parameters. * federated.ldap.et.group.objectClasses * federated.ldap.et.group.objectClassesForCreate * federated.ldap.et.group.searchBases * federated.ldap.et.personaccount.objectClasses * federated.ldap.et.personaccount.objectClassesForCreate * federated.ldap.et.personaccount.searchBases# Required: Enter a value for the following required group member parameters in the perties file under the Group member attribute heading:Note: See the properties file for specific information about the required parameters and for advanced parameters. * federated.ldap.gm.groupMemberName * federated.ldap.gm.objectClass * federated.ldap.gm.scope * federated.ldap.gm.dummyMember# Save your changes to the perties file.Example:WasUserid=uid=wpadmin,o=defaultWIMFileBasedRealm WasPassword=passwordPortalAdminId=wpadminPortalAdminPwd=passwordfederated.ldap.id=ad_idfederated.ldap.host=federated.ldap.port=389federated.ldap.bindDN=CN=BnQ_Portal,cn=users,DC=b-and-qchina,DC=comfederated.ldap.bindPassword=Pssw0rdfederated.ldap.ldapServerType=ADfederated.ldap.baseDN=DC=b-and-qchina,DC=comfederated.ldap.et.group.searchFilter=(objectclass=group)federated.ldap.et.group.objectClasses=groupfederated.ldap.et.group.objectClassesForCreate=federated.ldap.et.group.searchBases=DC=b-and-qchina,DC=comfederated.ldap.et.personaccount.searchFilter=(objectclass=user)federated.ldap.et.personaccount.objectClasses=userfederated.ldap.et.personaccount.objectClassesForCreate=federated.ldap.et.personaccount.searchBases=DC=b-and-qchina,DC=comfederated.ldap.gm.groupMemberName=memberfederated.ldap.gm.objectClass=groupfederated.ldap.gm.scope=directfederated.ldap.gm.dummyMember=uid=dummy验证LDAP./ConfigEngine.sh validate-federated-ldap增加 LDAP存储库./ConfigEngine.sh wp-create-ldap -DWasPassword=password九、 加入第二个节点确保主机的host能ping通主节点NDLDAPDB服务器。1、 环境准备从主节点Copy profileTemplates.zip（PortalServer_root/profileTemplates目录下）到附加节点，并解开。需要重建一个profileTemplates目录，和主节点的profileTemplates目录下的文件相同。同时设置一下文件访问权限：chmod -R 775 profileTemplates2、 create a new profile that will be used for additional cluster members在AppServer/bin目录下执行以下脚本：./manageprofiles.sh -create -templatePath /home/WebSphere/PortalServer/profileTemplates/managed.portal -profileName wp1_profile -profilePath /home/WebSphere/PortalServer/profiles/wp1_profile -cellName portal2Cell -nodeName portal2Node -hostName 3、 检查配置文件wp1_profile目录下wkplc_perties以及wkplc_perties and wkplc_perties4、 检查数据库的配置./ConfigEngine.sh validate-database -DWasPassword=password5、 修改perties （位于wp_profile_root/PortalServer/jcr/lib/com/ibm/icm/）set the jcr.textsearch.enabled property to false6、 加入群集在wp_profile_root/bin目录下执行如下语句：./addNode.sh 8879 -username wpadmin -password password7、 确认属性文件相关信息# Verify that WasUserid is set to your deployment manager administrator ID.# Verify that WasPassword is set to your deployment manager administrator password.# Verify that WasRemoteHostName is set to the fully qualified host name of the deployment manager.# Verify that WasSoapPort is set to the SOAP port that the deployment manager is using; the default value is 8879.# Verify that ServerName is set to the correct server name. The default is WebSphere_Portal but you can change this on your additional nodes.# Verify that PrimaryNode is set to false.# Verify