Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
5 install
I downloaded the following files prior to installing:
IBM Connections for Intranet and Extranet V4.5 for AIX, Windows, Linux, IBMi
Multilingual eAssembly (CRM1CML)
IBM Connections V4.5 for Windows Multilingual (CIHC5ML)
IBM Connections V4.5 Wizard for Windows Multilingual (CIHC8ML)
IBM DB2 and Tivoli for IBM Connections for Intranet and Extranet V4.5 for
Multiplatforms Multilingual eAssembly (CRM1DML)
IBM DB2 Enterprise Server Edition V10.1 for Windows on AMD64 and
EM64T systems (x64) Multilingual (CI6WEML)
IBM Data Server Client V10.1 for Windows on AMD64 and Intel EM64T
systems (x64) Multilingual (CI6V8ML)
IBM Tivoli Directory Integrator Identity Edition V7.1 for Windows x86-64,
Multilingual (CZ9MKML)
IBM WebSphere Application Server V8.0 for IBM Connections for Intranet and Extranet
V4.5 for Multiplatforms Multilingual eAssembly (CRM1EML)
IBM WebSphere Application Server Network Deployment V8.0 (1 of 4) for
Multiplatform, Multilingual IMPORTANT: All parts of this image (CZM9KML,
CZM9LML CZM9MML and CZVG4ML) must be extracted into the same
directory to create a local repository (CZM9KML)
IBM WebSphere Application Server Network Deployment V8.0 (2 of 4) for
Multiplatform, Multilingual IMPORTANT: All parts of this image (CZM9KML,
CZM9LML CZM9MML and CZVG4ML) must be extracted into the same
directory to create a local repository (CZM9LML)
IBM WebSphere Application Server Network Deployment V8.0 (3 of 4) for
Multiplatform, Multilingual IMPORTANT: All parts of this image (CZM9KML,
CZM9LML CZM9MML and CZVG4ML) must be extracted into the same
directory to create a local repository (CZM9MML)
IBM WebSphere Application Server Network Deployment V8.0 (4 of 4) for
Multiplatform, Multilingual IMPORTANT: All parts of this image (CZM9KML,
CZM9LML CZM9MML and CZVG4ML) must be extracted into the same
directory to create a local repository (CZVG4ML)
IBM Connections Content Manager V4.5 AIX, Windows, Linux Multilingual eAssembly
(CRLS4ML)
IBM FileNet Content Platform Engine V5.2 Windows Multilingual (CIG8XML)
IBM FileNet Content Platform Engine Client V5.2 Windows English (CIG9FEN)
IBM FileNet Collaboration Services V2.0 Windows Multilingual (CIG7ZML)
Post Install Fixes
NOTE: These are what I downloaded on 02 April 2013. Check the following location
for the latest supported releases:
http://www-01.ibm.com/support/docview.wss?uid=swg27037782
WebSphere Application Server, IBM HTTP Server and plug-ins 8.0 fixpack 5
http://www-01.ibm.com/support/docview.wss?uid=swg24033754
Required ifixes
PM62615 - http://www933.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~Web
Sphere&product=ibm/WebSphere/WebSphere+Application+Serve
r&release=8.0.0.5&platform=All&function=aparId&apars=PM626
15&source=fc
PM71430 - http://www933.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~Web
Sphere&product=ibm/WebSphere/WebSphere+Application+Serve
r&release=8.0.0.5&platform=All&function=aparId&apars=PM714
30&source=fc
TDI 7. 1 - fixpack 6
10.
Configure IBM Connections Content Manager Libraries ................................... 155
10.1.
Update the transaction time .......................................................................... 155
10.2.
Create Filenet domain, GCD, Object Store and AddOns ............................. 157
10.3.
Generate the SID value ................................................................................. 160
10.4.
Configure Filenet to be Activity Stream producer ....................................... 161
10.5.
Setting up anonymous access for a new FileNet deployment ...................... 169
10.5.1.
Add anonymous users to runAs role in FileNet .................................... 169
10.5.2.
Generate SID for anonymous user ........................................................ 172
10.5.3.
Add anonymous user to Download Count Anonymous User Ids property
173
1.
1.
2.
3.
4.
5.
1. Go to File Preferences .... to add the WebSphere repository to IBM Install Manager
2.
3.
4.
5.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
19.
20.
21.
22.
23.
24.
25.
WebSphere Application Server is now installed on the machine
2.
2. Login with the user created during the WebSphere Application Server install
4. Select Federated Repositories from the Available realm definitions field, and then
click Configure.
6. and then, on the Repository reference page, click Add Repository - LDAP repository
10. If your directory does not allow LDAP attributes to be searched anonymously,
provide values for the Bind distinguished name and Bind password fields. For
example, the Domino LDAP directory does not allow anonymous access, so if you
are using a Domino directory, you must specify the user name and password with
administrative level access in these fields.
11. Specify the login attribute or attributes that you want to use for authentication in the
Login properties field. Separate multiple attributes with a semicolon. For example:
uid;mail.
12. Click Apply
All other ldap directories, set both entries to the base of your directory. My ldap
directory is IBM Directory Server, so I set the base to dc=ibm,dc=com
16. In the Repository Identifier column, click the link for the repository or repositories
that you just added.
17. In the Additional Properties area, click the LDAP entity types link.
18. Click the Group entity type and modify the object classes mapping.
19. Set the objectClass to the group objectClass for you directory, and add the search
base for groups, Click Apply,
21. You can do the same for PersonAccount, in my ldap, we use inetOrgPerson, so I did
not change anything
22. In the navigation links at the top of the page, click the name of the repository that you
have just modified to return to the Repository page.
d. Enter group membership values in the Name of member attribute and Object class
fields. Click Ok
b. Select the Administrative Security and Application Security check boxes. Make
sure the Java 2 security check box is unchecked
c. Click Apply
25. Log out of the WebSphere Application Server Integrated Solutions Console and
restart WebSphere Application Server
a. Run C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin>stopManager.bat username localadmin -password password
b. Then C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin>startManager.bat
26. Verify that users in the LDAP directory have been successfully added to the
repository:
a. From the WebSphere Application Server Integrated Solutions Console, select
Users and Groups > Manage Users.
b. In the Search by field, enter a user name that you know to be in the LDAP
directory and click Search. If the search succeeds the user exists in your ldap
directory.
c. Click on the user, then click the Groups tab, you should see a list of groups the
user belongs to
27. Once the DMGR is finding users correctly from LDAP, restart the nodeagent to pick
up the changes by running
a. C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>stopNode.bat -username
localadmin -password password
b. C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>startNode.bat
3.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
4.
4. Add a user named lcuser. Enter the required details, including the password. Clear the
User must change password at next logon check box. Click Create.
5. Click Close.
6. Open the Users object, right-click lcuser, and select Properties from the context menu.
7. Click the Member Of tab and then click the Add button.
8. Type DB2USERS in the Enter the object names to select field, and click Check
Names.
10. Click OK again to save your changes and Close the Computer Management console
1. Run C:\downloads\ic4\IBM_Connections_4.5_win\Wizards\dbWizard.bat
2.
3.
4.
5.
6.
7.
5.
1. Run C:\downloads\ic4\TDI_71_64\launchpad.exe
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
3. After the fix pack is installed, verify the Tivoli Directory Integrator fix pack version
installed on your system by running
C:\IBM\TDI\V7.1\bin\applyUpdates.bat -queryreg
You should get the following results
Information from .registry file in: C:\IBM\TDI\V7.1
Edition: Identity
Level: 7.1.0.6
License: None
Fixes Applied
=-=-=-=-=-=-=
TDI-7.1-FP0006(7.1.0.0)
Components Installed
=-=-=-=-=-=-=-=-=-=
BASE
-TDI-7.1-FP0006
SERVER
-TDI-7.1-FP0006
CE
-TDI-7.1-FP0006
JAVADOCS
EXAMPLES
-TDI-7.1-FP0006
EMBEDDED WEB PLATFORM
AMC
Deferred: false
6.
2. Run C:\downloads\ic4\IBM_Connections_4.5_win\Wizards\populateWizard.bat
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
7.
4.
5.
6.
7. I went ahead and scrolled down and selected IBM Connections Content Manager
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18. I will set up the cognos piece later, so I select Do later here
19.
20.
21.
22. I have a domino server in my environment listening on port 25 for smtp traffic, so I
went ahead and configured notifications to that server.
23.
24.
25.
26.
27. Restart DMGR by running:
a. C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin>stopManager.bat -username
localadmin -password password
b. C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin>startManager.bat
28. Start the node agent by running:
a. C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>startNode.bat
29. At this point the DMGR begins syncing the applications down to the node. You should wait
for this process to complete. It may take 30 minutes to an hour. On my server it took 15
minutes. I typically watch the processes in windows task manager as I start the nodeagent.
You will see a java task use a lot of cpu, once it's drops to 0% cpu for a min or 2, it should be
done. Look in the nodeagent systemout.log log located at
C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent for the following line:
[4/3/13 19:44:48:011 EDT] 00000039 AppBinaryProc I ADMA7021I: Distribution of
application <connections_app> completed successfully.
You will see the following applications get synced:
ADMA7021I: Distribution of application WebSphereOauth20SP completed successfully.
ADMA7021I: Distribution of application Common completed successfully.
ADMA7021I: Distribution of application Mobile completed successfully.
ADMA7021I: Distribution of application Mobile Administration completed successfully.
ADMA7021I: Distribution of application WidgetContainer completed successfully.
ADMA7021I: Distribution of application Metrics completed successfully.
ADMA7021I: Distribution of application FileNetEngine completed successfully.
ADMA7021I: Distribution of application Search completed successfully.
ADMA7021I: Distribution of application Activities completed successfully.
ADMA7021I: Distribution of application Profiles completed successfully.
ADMA7021I: Distribution of application Moderation completed successfully.
ADMA7021I: Distribution of application Files completed successfully.
ADMA7021I: Distribution of application Communities completed successfully.
ADMA7021I: Distribution of application ibmasyncrsp completed successfully.
ADMA7021I: Distribution of application News completed successfully.
ADMA7021I: Distribution of application FNCS completed successfully.
ADMA7021I: Distribution of application Homepage completed successfully.
ADMA7021I: Distribution of application Forums completed successfully.
ADMA7021I: Distribution of application Wikis completed successfully.
2. Go to Servers > Server Types > WebSphere application servers and click on the
connections cluster server
3. on the right hand side, scroll down to Server Infrastructure, open Java and Process
Management and click on Process definition
d. Once you get the successfully started message, you are ready to test Connections:
8.
1. Run IBM Installation Manager by going to Start - All Programs - IBM Installation
Manager - IBM Installation Manager
2.
3.
4. Browse to the location of the WAS 8 Supplements files and supplements fp5 files
5.
6.
7.
8. Make sure to select both IBM HTTP Server v8.0 and Web Server Plug-ins for IBM
WebSphere Application Server v8.0 and change the Install path:
9.
10.
11.
12.
13.
4.
5. Update the Web server install location and Plug-in install location to the directories
used during the install
6.
7.
8. Select the webserver and click Generate Plug-in
C:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\CPRICESMCell01\nod
es\CPRICESMNode01\servers\webserver1\plugin-cfg.xml in our example
10. Open C:\IBM\HTTPServer\conf\httpd.conf in notepad
14. At this point you should be able to open a browser to any component that does not
require authentication. Profiles for example,
http://cpricesm.swg.usma.ibm.com/profiles
If you attempted to login or navigate between the products you will be sent back to the
WAS appserver ports. To stay on the HTTP server complete the remaining steps below:
2. Click New
6. Set the Key Label and Common name to the hostname of the IHS Server, and set
validity period to the length of time you want this certificate to be valid
8.4.3. Add the plug-in key file certificate to the HTTP server key file
1. Start IBM Key Management Utility by going to Start All Programs IBM HTTP
Server v8.0 Start Key Management Utility
2. Click Open
3. Click Browse
NOTE: If you are unsure of the file being used. Open the plugin-cfg.xml (you can
find this in the following line of C:\IBM\HTTPServer\conf\httpd.conf
WebSpherePluginConfig
"C:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\CPRICESMCell01\no
des\CPRICESMNode01\servers\webserver1\plugin-cfg.xml"
Open plugin-cfg.xml and look for the following line:
<Property Name="keyring"
Value="C:\IBM\WebSphere\Plugins/config/webserver1/plugin-key.kdb"/>
7. Set Data type to Base64-encoded ASCII data, give it a file name and location
Now we will open the HTTP Server key file and import this key file.
12. Enter the password you used when you created this file
15. Enter the file name and location of the plugin certificate we just exported.
16. Enter a Label, the name is not important, just something to help you remember its
the plugin used on this IHS Server
8.4.4. Add the WAS Web Container certificate to the plug-in key file
I typically have to do these steps, but in this version I did not have to do this, at the end
when I imported the arm file, I got a message that it already existed. I left the steps here
in case you need them...
Now we need to add the WebSphere Web Container certificate into the plug-in key file.
First we will get the Web Container certificate.
1. Open the WAS Admin console
(https://tamconfig40.swg.usma.ibm.com:9043/ibm/console/logon.jsp) and login
3. Click on CellDefaultKeyStore
6. Set a path and filename and set the Data type to Base64-encoded ASCII data
8. Start IBM Key Management Utility by going to Start All Programs IBM HTTP
Server v8.0 Start Key Management Utility
9. Click Open
NOTE: If you are unsure of the file being used. Open the plugin-cfg.xml (you can
find this in the following line of C:\IBM\HTTPServer\conf\httpd.conf
WebSpherePluginConfig
"C:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\CPRICESMCell01\no
des\CPRICESMNode01\servers\webserver1\plugin-cfg.xml"
Open plugin-cfg.xml and look for the following line:
<Property Name="keyring"
Value="C:\IBM\HTTPServer\Plugins/config/webserver1/plugin-key.kdb"/>
Then open the plugin-key.kdb from that location
12. Enter the password, by default the plugin-key.kdbs password is WebAS
Then you didn't need to do this step either, either way, close iKeyMan and go to the next
stesps:
4. Click on CellDefaultTrustStore
7. Enter a host, port and alias of the HTTP Server and click Retrieve signer information
8. Click OK
9. Click Save
9.
3. Under Container Settings, open Container Services and click Transaction service
4. Click the Configuration tab, and set the Maximum transaction timeout parameter
value to at least 600. Mine was set to 0 (unlimited) so I left this alone
5. Restart IBM Connections server
3.
4.
5.
6. Change directory back to C:\IBM\Connections\addons\ccm\ccmDomainTool
7. Run C:\IBM\Connections\addons\ccm\ccmDomainTool\createObjectStore.bat
8.
9.
2.
3.
4.
5. Copy SID : value, you will need it the next step
1. Open the Administration Console for Content Platform Engine (ACCE) and login
(http://cpricesm.swg.usma.ibm.com/acce)
3. Click Search
5. From the Select Columns list select the asterisk (*). Use the move button to place "*"
into the Selected pane
8. A single row is returned, Click the link in the ID column to open it for viewing and
editing:
Property Value
{ecm_files}
https://cpricesm.swg.usma.ibm.com
{connections}/resources/web/com.ibm.social.ee/Connection
sEE.xml
password
localadmin
NOTE: login name of a Connections user and will be
encrypted after input. This user must be in the
trustedExternalApplication role on the Widget Container
application in IBM Connections. By default, the
Connections administrator has these privileges and may be
used here.
Activity Stream Extended a. Click the small triangle associated with the Property
Settings
Value for this entry and select Display or Edit Value.
activityStreamFileLinkURL={0}/atom/library/{1}/docu
ment/{2}/media/{3}
activityStreamNullifyActionableURL={0}/connections/o
pensocial/basic/rest/activitystreams/@me/@all/@all/{1}
Download Count
Anonymous User Ids
10.5.1.
2. Click Applications -> Application Types -> WebSphere enterprise applications, and
click on FNCS
4. Select the Anonymous role and enter the username and password of the user
designated for the anonymous access role (anonymous_localuser : password). Click
Apply
10.5.2.
1. Run C:\IBM\Connections\addons\ccm\ccmDomainTool\generateSID.bat
2.
4.
5. Copy SID : value, you will need it the next step
2. Expand the Object Stores node on the side navigation tree. Right-click on
ICObjectStore and click Open.
4. From the Select Columns list, select the asterisk (*). Use the move button to place
(*) into the Selected pane
9. On the Properties tab, Scroll down and look for the Property Value Download
Count Anonymous User Ids, Click on the down arrow button.
11. add the SID value of the user created in the previous step (S-1-98-878917172845242677-845230893-892611889-1630364212-758460720-845309489-
14.
15.