WebSphere Portal v8.5 安装截图
包括内容： portal server 8.5 数据库 db2 ldap服务器 wcm8.5
数据库 db2 安装
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
安装数据库补丁
19
Stop all running DB2 processes
To stop all DB2 server processes:
– “su – db2inst1” – db2stop – exit – “su – dasusr1” – db2admin stop – exit
Running a “ps –ef | grep –i db2” should result in no processes running.
69
Need to register license or else DB2 will stop working after a certain period …
Note: Got license from the following download package: IBM DB2 Enterprise Server Edition - PVU Option - Quick Start and Activation V10.5.0.1 for Linux, UNIX and Windows Multilingual (CIPH3ML)
Lastly, the server is a lightweight/small version and only needs to be started if/when we want to manage the LDAP server via the web admin console.
35
36
1) su – idsldap 2) db2start 3) db2 upgrade database ldapdb user idsldap using <password> 4) db2rbind ldapdb –l bind.log –u idsldap –p <password> 5) db2 activate database ldapdb
•
•
52
At this point, the LDAP Server has been configured. Next I will upgrade DB2 to V10.5 so that MediaBeacon can be installed later. I have to go through this extra step as the IBM Directory Server would only install with DB2 V10.1 and not V10.5
20
Start the DB2 Fixpack Installer ….
ices are Running …
To start DB2:
– “su – db2inst1” – db2start – “su – db2admin” – db2admin start
37
Directory Server installed – Now to Configure ….
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Import users from LDIF file …
• The LDIF file I used matched what we use on our Softlayer and POT images There is a main LDIF for normal showcase users named “showcaseportal85.ldif” There is a second and smaller LDIF named “showcase-portal85ext.ldif“. This second file defines “external” users. These users are used by Connections to show integration with external users/customers.
24
安装 IBM Directory Server V6.3.1
25
Install ksh shell ….
IMPORTANT NOTE: The IBM Directory Server install requires the ksh shell. Without it, the install will fail with a “Directory Server licenses cannot be installed” error message. See following technote for additional details: /support/docview.wss?uid=swg2166 5599
85
NOTE: Since we will later be moving to LDAP as the user registry, and our normal „wpadmin‟ id already exists in LDAP, I am just using „admin‟ here. This id does not exists in LDAP so I will not run into conflicts during the LDAP xfer. Once the LDAP xfer is done, „wpadmin‟ will become my primary portal/was administrative id.
95
96
97
98
Note: Since I sometimes had problems in the past when doing the DB transfer, I choose NOT to click the “Start Configuration” button, which would cause the wizard to automatically run each step. I prefer to go through them one by one so I can do extra checking/validating.
70
Uninstall DB2 V10.1
Now that we have everything moved to DB2 V10.5 we can uninstall DB2 V10.1 by running the following command as root
– /opt/IBM/db2/V10.1/install/db2_deinstall -a
26
Start Directory Server V6.3.1 Installer …
27
28
29
30
31
32
33
34
I find it‟s easier to have the LDAP Server have its own embedded WAS Server for running the LDAP Admin Console. In doing so the admin console web app is automatically setup and I don‟t need to manually deploy it. Plus it will not conflict or rely on any other existing WAS Server to be running.
86
87
88
Transfer Portal Database to DB2
89
90
91
92
93
94
NOTE: If you choose the “Yes create my databases for me” the “ConfigEngine createdatabase” command will end up running. For some reason, not all the tablespaces in the JCR gets created and as a result the database-transfer task will end up failing. From searches online it seems this problem has showed up on previous versions. Resolution was to manually create the database using the DB commands.
71
安装 IBM WebSphere Portal V8.5 and WCM V8.5
72
Verify ulimit
As describe in the InfoCenter, we should verify the ulimit is set to unlimited:
73
Start the Installer …
74
75
76
77
78
79
80
81
82
83
84
NOTE: Since we will later be moving to LDAP as the user registry, and our normal „wpadmin‟ id already exists in LDAP, I am just using „admin‟ here. This id does not exists in LDAP so I will not run into conflicts during the LDAP xfer. Once the LDAP xfer is done, „wpadmin‟ will become my primary portal/was administrative id.