Filenet Sharepoint Connector Guide

IBM FileNet Connector for SharePoint Web Parts
Version 2.2.2.0
Installation and Upgrade Guide
GC31-5528-04
IBM FileNet Connector for SharePoint Web Parts

Version 2.2.2.0
Installation and Upgrade Guide
GC31-5528-04
Note
Before using this information and the product it supports, read the information in Notices on page 29.
This edition applies to version 5.0.0 of IBM FileNet Content Manager (product number 5724-R81), version 5.0.0 of
IBM FileNet Business Process Manager (product number 5724-R76), and to all subsequent releases and
modifications until otherwise indicated in new editions.
Copyright IBM Corporation 2001, 2011.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
ibm.com and related resources. . . . . v
How to send your comments . . . . . . . . . v
Contacting IBM . . . . . . . . . . . . . vi
Installing IBM FileNet Connector for

Microsoft SharePoint Web Parts . . . . 1
Planning the Installation . . . . . . . . .
Software requirements . . . . . . . . .
SSL Configuration . . . . . . . . . .
Preparing for installation . . . . . . . .
Non-English environment installation . . . .
Authentication and database requirements . .
Installation Tasks . . . . . . . . . . . .
(Optional) Creating a Microsoft SQL Server User
Profile Database manually . . . . . . . .
Installing IBM FileNet Connector for Microsoft
SharePoint Web Parts . . . . . . . . .
Specifying the Application Pool security account
Adding and configuring IBM FileNet Connector
for Microsoft SharePoint Web Parts . . . .
Installing a highly available IBM FileNet Connector
for Microsoft SharePoint Web Parts . . . . .
Installing IBM FileNet Connector for Microsoft
SharePoint Web Parts in a farm environment .
Verifying IBM FileNet Connector for Microsoft
SharePoint Web Parts installation in a farm
environment . . . . . . . . . . . .
.
.
.
.
.
.
.
1
1
2
2
5
7
8
. 9
. 9
10
Copyright IBM Corp. 2001, 2011
.
.
.
.
.
.
.
.
. 18
. 18
. 19
. 20
Maintaining IBM FileNet Connector for

Manually deploying web parts to new web
applications . . . . . . . . . . . . . .
Updating the web.config file. . . . . . . . .
(IBM FileNet credential store authentication)
Updating the web.config file. . . . . . . .
(Integrated Windows authentication) Updating
the web.config file . . . . . . . . . . .
Updating .webparts files with IBM FileNet P8 URLs
21
22
22
24
25
. 11
. 12
. 12
. 14
Upgrading IBM FileNet Connector for

SharePoint Web Parts . . . . . . . . 17
Planing the upgrade . . . . . .
Upgrading to SharePoint Server 2010 .
Upgrading IBM FileNet Connector for Microsoft

SharePoint Web Parts software . . . . . . .
SharePoint Web Parts silently . . . . . .
SharePoint Web Parts interactively. . . . .
Updating the IBM FileNet Connector for Microsoft
SharePoint Web Parts documentation URL . . .
. 17
. 18
Removing IBM FileNet Connector for

Uninstalling IBM FileNet Connector
SharePoint Web Parts interactively.
Uninstalling IBM FileNet Connector
SharePoint Web Parts silently . .
for
.
for
.
Microsoft
. . . .
Microsoft
. . . .
. 27
. 28
Notices . . . . . . . . . . . . . . 29
Trademarks .
. 31
Index . . . . . . . . . . . . . . . 33
iii
iv
Installation and Upgrade
ibm.com and related resources

Product support and documentation are available from ibm.com.
Support and assistance

Product support is available on the Web. Click Support from the product Web site
at:
FileNet Content Manager Support
http://www.ibm.com/software/data/content-management/filenet-contentmanager/support.html
Information center
You can view the product documentation in an Eclipse-based information center
that you can install when you install the product. By default, the information
center runs in a Web server mode that other Web browsers can access. You can also
run it locally on your workstation. See the information center at
http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp.
PDF publications
You can view the PDF files online using the Adobe Acrobat Reader for your
operating system. If you do not have the Acrobat Reader installed, you can
download it from the Adobe Web site at http://www.adobe.com.
See the following PDF publications Web sites:
Product
Web site
Product Documentation for FileNet http://www.ibm.com/support/docview.wss?rs=3278

P8 Platform
&uid=swg27010422
How to send your comments

Your feedback is important in helping to provide the most accurate and highest
quality information.
Send your comments by using the online reader comment form at
https://www14.software.ibm.com/webapp/iwm/web/signup.do?lang=en_US
&source=swg-rcf.
Consumability survey
You are invited to tell IBM how to improve the consumability of software
products. If you want to help IBM make IBM FileNet P8 easier to use, take the
Consumability Survey at http://www.ibm.com/software/data/info/
consumability-survey/.
Contacting IBM
To contact IBM customer service in the United States or Canada, call
1-800-IBM-SERV (1-800-426-7378).
To learn about available service options, call one of the following numbers:
v In the United States: 1-888-426-4343
v In Canada: 1-800-465-9600
For more information about how to contact IBM, see the Contact IBM Web site at
http://www.ibm.com/contact/us/.
vi
Installing IBM FileNet Connector for Microsoft SharePoint

Web Parts
Installing IBM FileNet Connector for Microsoft SharePoint Web Parts gives you the
ability to combine SharePoint's familiar interface with the content, process, and
compliance infrastructure provided by the IBM FileNet P8 platform.
Planning the Installation

The topics in this section provide guidelines and other relevant information to help
you plan for the IBM FileNet Connector for Microsoft SharePoint Web Parts
installation.
Important installation information:
v You must install IBM FileNet Connector for Microsoft SharePoint Web Parts on
each front-end SharePoint server that you wish to support with this IBM FileNet
P8 software.
v All paths listed in this guide are default locations. If you installed to a location
other than the default, remember to substitute the alternate installation path
appropriately.
v Directory names must use ASCII characters only.
Software requirements
You must meet some the following general requirements for installing IBM FileNet
Connector for Microsoft SharePoint Web Parts.
v IBM FileNet P8 Platform components, including the following:
Content Engine.
Content Search Engine (Autonomy K2 or IBM Content Search Services), if you
require Content-Based Retrieval (CBR).
Microsoft .NET Framework runtime.
Web Service Enhancements for Microsoft .NET runtime for non-SSL
configurations. An SSL connection to the Content Engine is required if Web
Service Enhancements for Microsoft .NET runtime is not installed.
Process Engine.
Application Engine, or Workplace XT.
v Microsoft SharePoint Foundation 2010, Microsoft SharePoint Server Standard
2010, or Microsoft SharePoint Server Enterprise 2010 with the 2010 user interface
active.
v Microsoft SQL Server.
Restriction: Microsoft SharePoint servers that have been upgraded to 2010 from
2007 must use the new 2010 interface.
Related information
Product documentation for IBM FileNet P8 Platform
Download the IBM FileNet P8 Compatibility Matrix and PDF's of other IBM
FileNet P8 documentation.
SSL Configuration
To allow for successful SSL connectivity to a Content Engine and Application
Engine, or Workplace XT server, both SSL certificates must be installed to the
Trusted Root Certification Authorities folder of the Local Computer store on the
SharePoint server that hosts the IBM FileNet Connector for Microsoft SharePoint
Web Parts. This allows ASP.NET applications to use the certificate on behalf of a
user.
Note: Within the web parts settings for the Content Engine URL and the
Workplace or Workplace XT URL, you must ensure the host_name in each URL
matches the host_name as it is stated in the settings page of the SSL Certificate.
Preparing for installation

Preparation tasks for IBM FileNet Connector for Microsoft SharePoint Web Parts
are required before installation. Capture IBM FileNet P8 environment installation
values in the Installation and Upgrade Worksheet before you begin to install IBM
FileNet Connector for Microsoft SharePoint Web Parts. You can use the worksheet
to complete your installation.
Definition of installation roles

The tasks in this guide and the rows in the Installation and Upgrade Worksheet are
organized by administrative roles. Your organization might have different roles,
and some of the responsibilities of listed roles will vary from those assigned by
default in this documentation.
Installation administrator
v Runs IBM FileNet P8 installers during initial setup.
v Runs the Configuration Manager tool during initial setup, followed by starting
IBM FileNet Enterprise Manager.
v Runs IBM FileNet P8 Upgrade programs during upgrades.
v Abbreviated as IA. Responsible for coordinating the information described in
this worksheet. The information itself will require the input from the other roles.
The role of IA is usually filled by an IBM FileNet Certified Professional (FCP).
Information technology administrator

v Responsible for the networking and operating systems settings required by IBM
FileNet P8.
v Responsible for performing certain security configurations.
v Abbreviated as ITA. Responsible for providing the information in the rows in
the Installation and Upgrade Worksheet with a value of ITA in the Role column.
Security administrator
v Responsible for configuring the directory servers required by IBM FileNet P8
components, including Content Engine and Application Engine.
v Creates and maintains directory server user and group accounts.
v Abbreviated as SA. Responsible for providing the information in the rows in the
Installation and Upgrade Worksheet with a value of SA in the Role column.
Database administrator
v Creates, configures, maintains database installations and database or table
spaces.
v Responsible for creating database accounts needed by IBM FileNet P8.
v For purposes of this documentation, the database administrator is expected to
have responsibilities regarding the JDBC data sources.
v Abbreviated as DBA. Responsible for providing the information in the rows in
the Installation and Upgrade Worksheet with a value of DBA in the Role column.
Application server administrator

v Responsible for providing the application servers required by IBM FileNet P8.
v Responsible for application server administrative accounts.
v Abbreviated as ASA. Responsible for providing the information in the rows in
the Installation and Upgrade Worksheet with a value of ASA in the Role column.
IBM FileNet P8 administrator

v This role designation actually refers to the administrator or administrators who
perform regular maintenance of Content Engine, Process Engine Application
Engine, Workplace or Workplace XT.
v The administrator who logs on to Enterprise Manager by using the gcd_admin
account or an object_store_admin account is considered an IBM FileNet P8
administrator.
v Abbreviated as P8A. Responsible for providing the information in the rows of
the Installation and Upgrade Worksheet with a value of P8A in the Role column.
E-mail Administrator
v Creates an e-mail account that will be used to configure the Notification tab of
the Process Task Manager so that Process Engine can send e-mail notifications to
end users. (Required only if you use this feature.)
v Abbreviated as EA.
Using the installation and upgrade worksheet

The Installation and Upgrade Worksheet is a Microsoft Excel spreadsheet
(p8_worksheet.xls). The worksheet describes the properties and parameters
required to complete IBM FileNet P8 installation, upgrade, and configuration
programs, and provides a way to record the values you assign to these properties
and parameters.
Administrators who are preparing the environment for installation or upgrade of
IBM FileNet P8 components must use the worksheet during their preparation tasks
to record the appropriate values and provide them to the Installation
Administrator who runs the installation or upgrade programs.
Some of the features of the Installation and Upgrade Worksheet are:
v Instructions: describes the worksheet and includes a button that runs the
Customize Worksheet macro.
v The two highlighted columns, Property or Parameter and ENTER YOUR
VALUE HERE, provide the simplest view of the requirement. The others add
identifying information and help you sort and filter the rows usefully.
Installing IBM FileNet Connector for Microsoft SharePoint Web Parts
v The Role column assigns each row to an administrator and uses the following
acronyms:
ITA: Information Technology Administrator
ASA: Application Server Administrator
DBA: Database Administrator
SA: Security Administrator
P8A: IBM FileNet P8 Administrator
v Property definitions are contained in the column titled Description.
v Some rows, though not all, contain a hyperlink in the IC help link column.
Click this hyperlink to run a query against the IBM Information Center, which
opens with the Search Results pane showing the topics that contain the words in
the query phrase. Browse the search results until you have enough information
to be able to enter a value in the Worksheet row.
Related reference
Installation and Upgrade worksheet
The worksheet is a Microsoft Excel spreadsheet that describes the properties and
parameters required to complete installation, upgrade, and configuration. It also
provides a way to record the values that you assign to these properties and
parameters.
Running the Customize Worksheet macro:
The Customize Worksheet macro lets you extract only those rows that describe
your environment.
About this task
Important: For support of the full range of built-in filter and macro features, use
Microsoft Excel to view the Installation and Upgrade Worksheet file. You can use
other spreadsheet programs to view the file; however, filter and macro support can
vary. For example, in Calc from OpenOffice.Org, the column filters work as
expected, but the Customize Worksheet button does not.
To run the Customize Worksheet macro:
Procedure
1. Open the Installation and Upgrade Worksheet (p8_worksheet.xls) and click the
Instructions worksheet (also called a tab).
2. Scroll down until you see the button representing the Customize Worksheet
macro. Click the button.
3. Select the components and options that describe the environment you are
preparing for IBM FileNet P8.
v Installation or Upgrade
v FileNet P8 Components
v Application Server type
v Operating system
v Database type
v Directory Server type
v Number of object stores (adds new sets of rows for creating additional data
sources)
v Name of customized sheet
4. Click OK. The macro copies the rows that fulfill your selection criteria into a
new worksheet with the name you entered. Enter the values for your
environment into this new worksheet.
5. Click the name of the new worksheet at the bottom of the Excel window. Add
your preparation values into this new worksheet.
6. Notice that the new worksheet has buttons at the top titled Show Installer
View and Show Full View, depending on its state. The Show Installer View
displays only those columns that you need while running installation or
configuration programs.
Autofiltering and sorting the Worksheet:
There are several ways to organize the Worksheet to make finding properties and
entering values easier.
About this task
AutoFiltering is a quick way to display only those rows that meet a certain criteria.
To use AutoFilter:
Procedure
1. Make sure AutoFiltering is enabled. (Select the entire row with the column
headers, then click Data Filter Autofilter.) AutoFilter arrows will appear to
the right of the column labels.
2. Click the AutoFilter arrow in the Installation or Configuration Program
column header and select the program you are interested in (for example, PE
installer).
3. Click the AutoFilter arrow in the Setup Type column header, select Custom,
and specify Setup Type contains Installation.
4. For a custom AutoFilter, click the AutoFilter in any column header, select
Custom, and specify Setup Type contains Installation.
5. To turn off AutoFiltering in a column, click the column AutoFilter arrow and
select (All).
6. To reorder rows alphabetically, do a Sort:
a. Click anywhere in a column, for example, Column A Role.
The only possible values in the Role column are ASA, SA, DBA, ITA, and
P8A. Sorting on Role therefore groups the rows by this attribute, in
alphabetic order. Several other columns also have a limited number of
possible values which means they can be usefully sorted.
b. Click the Sort Ascending icon in the Excel toolbar, or use the Data Sort
menu command. The rows sort on Role.
Sorting the Worksheet reassigns row numbers. If you refer to rows by
number, be aware that row numbers change if you change the sort order.
Non-English environment installation

To enable localized user interface for IBM FileNet Connector for Microsoft
SharePoint Web Parts, the IBM FileNet connector must be added as a web part to a
localized SharePoint site. The Microsoft SharePoint language pack must be
installed (on top of Microsoft SharePoint English platform) in order to have the
language selection enabled when creating a SharePoint site.
Note: For details on the supported levels of third-party software components and
version requirements for non-English installations, refer to the IBM FileNet P8
Hardware and Software Requirements guide.
Microsoft SharePoint US English or localized version is required.
When using a localized version of Microsoft SharePoint, no additional Microsoft
SharePoint language pack is required.
Related information
Product documentation for IBM FileNet P8
For details on the supported levels of vendor software components and version
requirements for non-English installations, see the IBM FileNet P8 Non-English
Support Guide.
Operating System Requirements

To enable IBM FileNet Connector for Microsoft SharePoint Web Parts to support
Windows in non-English environments, install FileNet Connector for Microsoft
SharePoint Web Parts on a localized version of Windows where available.
If the localized version of Microsoft Windows is not available, use the English
language version with the regional settings for the appropriate language. Follow
the Microsoft Windows instructions for changing the regional settings in the
Control Panel.
When using the Microsoft SharePoint English Product, the corresponding Microsoft
SharePoint Language Pack must be installed to enable translations on the IBM
FileNet Connector for Microsoft SharePoint Web Parts user interface. This is also
applicable to Microsoft SharePoint Service Packs.
A Microsoft SharePoint language pack is not required if the Microsoft SharePoint
server contains a fully localized SharePoint installation. Additional Microsoft
SharePoint language packs are required if you want to deploy multiple languages
on one SharePoint server.
Important: When creating a Microsoft SharePoint site, the SharePoint site
administrator needs to take into account the end-user's preferred locale settings,
such as date format. The date format displayed on a client browser is dependent
on the SharePoint user settings. Where a specific SharePoint user locale has not
been set, the calendar locale is then based on the SharePoint site settings. In order
to display a localized calendar on the client for a particular language, the
SharePoint user settings and the SharePoint site settings must match.
Content Engine Requirements

To support Windows in non-English environments, install a language pack.
v For Content Engine 4.x, to get support for non-English languages, you must
install a language pack. The Content Engine language pack is a single executable
that contains the localized default document classes, properties and choice value
lists for a single display language. Once the language packs for the Content
Engine are installed, IBM FileNet Connector for Microsoft SharePoint Web Parts
integration with the Content Engine enables the display of all default document
classes, properties, and choice value lists.
For instructions on installing and deploying a Content Engine language pack, see
the IBM FileNet P8 Non-English Support Guide.
v For Content Engine 4.5 and later, no language pack installation is required
because language-related add-ons are built into the baseline software.
Related information
For details on installing and deploying a Content Engine language pack, see the
IBM FileNet P8 Non-English Support Guide.
Available Languages
IBM FileNet Connector for Microsoft SharePoint Web Parts installs the following
languages.
Language
Locale
Chinese (Simplified)
zh-CN
Chinese (Traditional)
zh-TW
French
fr
German
de
Italian
it
Japanese
ja
Korean
ko
Portuguese (Brazilian)
pt-BR
Spanish
es
Once a translated Microsoft SharePoint site is created and IBM FileNet Connector
for Microsoft SharePoint Web Parts has been added to this site, the translated user
interface displays.
Authentication and database requirements

IBM FileNet Connector for Microsoft SharePoint Web Parts supports two methods
of user authentication.
Windows Integrated Authentication
IBM FileNet Connector for Microsoft SharePoint Web Parts supports
Windows Integrated Authentication (SSO) through Kerberos and SPNEGO.
Windows Integrated Authentication must be installed and configured in
your environment before you run the FileNet Connector for Microsoft
SharePoint Web Parts installation program. Refer to the IBM FileNet P8
Hardware and Software Requirements for information on Single Sign-on (SSO)
and Kerberos.
The SharePoint application pool security account writes to the FileNet
Connector for Microsoft SharePoint Web Parts session state database
(ASPState) that is created by the installation program. This user can either
be the NT AUTHORITY\NETWORK SERVICE user or another user under which
the ASP.NET service runs. The application pool security account must have
owner access rights (db_owner) to the session state database that is created
for FileNet Connector for Microsoft SharePoint Web Parts during
installation. See your Microsoft SQL Server documentation for details on
how to set database user privileges.
IBM FileNet Credential Store
For this method of authentication, you must use a Microsoft SQL Server
database to hold user profile information, taking into account the following
database requirements:
Restriction: For this method of authentication, Application Engine /

Workplace must be installed with application-managed authentication to
integrate with FileNet Connector for Microsoft SharePoint Web Parts.
v A user profile database is required. A Microsoft SQL Server database
user with Database Creator privileges is required to successfully run the
FileNet Connector for Microsoft SharePoint Web Parts installation
program. The installation program prompts you to choose whether to
have the user profile database created during installation or use a
database that was manually created by the database user. This user is
needed only for install. You can remove this user after installation.
Note: If you create the user profile database manually, create it before
running the FileNet Connector for Microsoft SharePoint Web Parts
installation program because the information is required during the
installation process.
v The SharePoint application pool security account writes to the FileNet
Connector for Microsoft SharePoint Web Parts user profile database. This
user can either be the NT AUTHORITY\NETWORK SERVICE user or
another user under which the ASP.NET service runs. Be aware that this
user has access to user profile information. The application pool security
account must have Full Access rights (aspnet_Profile_FullAccess) to
the user profile database you create for FileNet Connector for Microsoft
SharePoint Web Parts. These privileges ensure that this user can properly
administer the database using the User Administration web part (for
example, to add and delete user profiles). See your Microsoft SQL Server
documentation for details on how to set database user privileges.
v An encryption key is required. The FileNet Connector for Microsoft
SharePoint Web Parts installation program prompts the user to enter an
encryption key during installation. The key can be any string and is
used to encrypt the stored user names and passwords in the user profile
database. The key itself is stored in the web.config file and a best
practice is to encrypt the key using the appropriate Microsoft encryption
tool.
v The SharePoint application pool security account writes to the FileNet
Connector for Microsoft SharePoint Web Parts session state database
(ASPState) that is created by the installation program. This user can
either be the NT AUTHORITY\NETWORK SERVICE user or another user under
which the ASP.NET service runs. The application pool security account
must have owner access rights (db_owner) to the session state database
that is created for FileNet Connector for Microsoft SharePoint Web Parts
during installation.
Related information
Download the IBM FileNet P8 System Overview document
Download the IBM FileNet P8 Hardware and Software Requirements document
and other IBM FileNet P8 documentation.
Installation Tasks
To install IBM FileNet Connector for Microsoft SharePoint Web Parts, you must
complete the following tasks.
(Optional) Creating a Microsoft SQL Server User Profile

Database manually
You can manually create the required user profile database instead of having the
IBM FileNet Connector for Microsoft SharePoint Web Parts installation program
create it for you.
About this task

This task describes how to manually create the Microsoft SQL Server database that
is used to map Microsoft SharePoint users to IBM FileNet P8 user credentials. This
task is optional and only needs to be completed if you do not want the IBM
FileNet Connector for Microsoft SharePoint Web Parts installation program to
create the database for you.
Procedure
1. Log on to the SharePoint machine using an account that has local administrator
privileges.
2. Open a command prompt and change the directory to:
C:\Windows\Microsoft.NET\Framework\v2.0.50727
3. Enter the following at the command line. This command creates the database
and necessary table structure for the user profile database. The entry is case
sensitive.
aspnet_regsql.exe -S hostname
-U sa -P sa_password -d FileNetProfile -A p
4. Verify the database has been created.
Installing IBM FileNet Connector for Microsoft SharePoint Web

Parts
This task describes how to install IBM FileNet Connector for Microsoft SharePoint
Web Parts interactively or silently on the SharePoint server.
Before you begin this procedure, ensure all prerequisites are installed.
Note: The installation program checks your system for (and silently installs, if
necessary) a current version of the Content Engine .NET API.

Parts interactively
You can install IBM FileNet Connector for Microsoft SharePoint Web Parts
interactively by running the FileNet Connector for Microsoft SharePoint Web Parts
installation program.
About this task

Procedure
1. Log on to the SharePoint server using an account that has local administrator
privileges.
2. Launch the 2.2.2.0-SPWP.exe file.
3. Refer to your Installation and Upgrade Worksheet to complete the steps in the
wizard and install the IBM FileNet Connector for Microsoft SharePoint Web
Parts software.

Parts silently
To run a silent installation, you must create a response file that contains the
options to pass to the installation program during installation. A sample response
file is included with the IBM FileNet Connector for Microsoft SharePoint Web Parts
Procedure
privileges.
2. From the IBM FileNet Connector for Microsoft SharePoint Web Parts software
package, open the silent_installer.properties file in a text editor. Refer to
your Installation and Upgrade Worksheet and edit the properties file to reflect
the appropriate responses for your installation.
3. Open a command prompt and run the following command from the
appropriate directory:
2.2.2.0-SPWP.exe -i silent -f
silent_installer.properties
4.
Verify that the installation completed successfully by accessing the install log
file at the following default location:
C:\Program Files\IBM\
FileNetConnectorForSharePointWebParts\
sharepoint_web_parts_install_log_2.2.2.0.txt
Specifying the Application Pool security account

You must specify the account that is writing to the IBM FileNet Connector for
Microsoft SharePoint Web Parts user profile and session state databases.
Before you begin

This user must be the same user that is configured to execute within the
application pool of the SharePoint web applications to be processed. Take adequate
caution, as this user has access to user profile information.
The application pool security account must have full access rights
(aspnet_Profile_FullAccess) to the user profile database that you create for IBM
FileNet Connector for Microsoft SharePoint Web Parts and db_owner role to the
ASPState database. These privileges ensure the user profile and session state
databases are updated correctly.
For more detail on the application pool security account, see Authentication and
database requirements on page 7.
About this task

To specify the application pool security account:
Procedure
1. Determine the application pool that is configured for use with the SharePoint
web application. For Internet Information Services version 7:
a. On the SharePoint server, access the Internet Information Services (IIS)
Manager from the Administrative Tools.
b. Expand the Server node and the Sites node.
10
c. Right-click the SharePoint Web site to which the FileNet Connector for
Microsoft SharePoint Web Parts were deployed and select Manage Web Site
Advanced Settings.
d. Record the application pool name, which is listed at the top of the
Advanced Settings window. This is the application pool that is configured
for use with the SharePoint Web Application.
e. Close the Advanced Settings window.
2. Determine the account that is running the application pool. For Internet
Information Services version 7:
a. Click Application Pools.
b. Find the appropriate application under the Name column on the
Application Pools page.
c. Under the Identity column, note the name listed. This is the account that
must be used to write to the user profile database.
d. From Microsoft SQL Server Management Studio, specify the Application
Pool Security Account. Add the user name from step 1 above to the
following nodes:
v Security\Logins node.
v database_profile\Security\Users node. This is the same database name
you entered during installation on the User Profile Database Information
screen.
e. Assign aspnet_Profile_FullAccess role membership to the SharePoint
application pool user in the profile database.
Adding and configuring IBM FileNet Connector for Microsoft

SharePoint Web Parts
The IBM FileNet Connector for Microsoft SharePoint Web Parts solutions are now
deployed to your SharePoint site. You can add the various web parts to your web
sites.
For information about adding and configuring web parts, see the Related reference
links below or access IBM FileNet P8 help topic: Working with documents
Working with documents in Microsoft SharePoint IBM FileNet Connector for
SharePoint IBM FileNet Connector for Microsoft SharePoint Web Parts Add
web parts.
11
Related information
Add web parts
IBM FileNet Connector for SharePoint Web Parts installs custom web parts in your
SharePoint library. IBM FileNet web parts are added to a SharePoint site page in
the same manner as other web parts. This topic lists the basic steps for adding a
web part or creating a search center page. See your SharePoint documentation for a
full discussion of either option.
Configure web parts
To install documentation for IBM FileNet P8 expansion products, you must copy
that documentation onto the application server where IBM FileNet P8 Platform
documentation is already installed. You then rebuild the documentation search
index.
Installing a highly available IBM FileNet Connector for Microsoft

SharePoint Web Parts
You can install and configure IBM FileNet Connector for Microsoft SharePoint Web
Parts to be highly available in an IBM FileNet P8 environment.

Parts in a farm environment
You can install and configure IBM FileNet Connector for Microsoft SharePoint Web
Parts to be highly available in an IBM FileNet P8 environment.
About this task

To complete the following tasks, you will need to refer to the procedures outlined
in the Installation Tasks on page 8 section of this manual. To install IBM FileNet
Connector for Microsoft SharePoint Web Parts in a farm environment:
Procedure
1. Install and configure a SharePoint farm. To set up a farmed SharePoint
environment, follow the instructions provided by Microsoft. For example, see
the Microsoft TechNet article, Deployment overview (SharePoint Server 2010).
2. Note the following information for the Microsoft SQL Server database is
required to set up the Microsoft SQL Server User Profile Database and
configure IBM FileNet Credential Store Authentication:
v Database Server and Instance
v Database Port
v Database User
v Database Password
3. (Optional) Manually create a Microsoft SQL Server User Profile Database. This
step is optional, you can use the IBM FileNet Connector for Microsoft
SharePoint Web Parts installation program to create the database. To manually
create the database in a farmed environment, follow the instructions in the
(Optional) Creating a Microsoft SQL Server User Profile Database manually
on page 9 step in the installation instructions with the following modifications:
Make sure you enter the database server and instance name for the hostname
property. For example: database_server/database_instance.
12
Tip: Enter only the database server name if you use the default database
instance. The Database Name is required to configure IBM FileNet Credential
Store Authentication.
4. Install IBM FileNet Connector for Microsoft SharePoint Web Parts on each farm
node. For each node, follow the installation procedures outlined in the
Installation Tasks on page 8 section of this guide with the following
modifications:
v (IBM FileNet Credential Store Authentication only) Configure the SharePoint
farm to use the Microsoft SQL Server User Profile Database.
If you choose to have the installation program create the database for you,
only do this when running the installation program on the first farm node.
For the consecutive nodes select the option to use an existing database,
and point to the database you created while running the installation
program on the first node.
If you have created the database manually, select the option to use an
existing database, and point to the database you created in "Manually
create a Microsoft SQL Server User Profile Database" task.
For a remote database, make sure you enter the database server and
instance name for the hostname property. For example:
database_server/database_instance
Tip: Enter only the database server name if you use the default database
instance.
For port number enter the instance port number associated with your
database instance.
Encryption Key - each SharePoint node must use the same encryption key.
v Choose a deployment method that suits your SharePoint setup.
v For each node after the first, ensure the FileNet P8 URLs you enter during
installation are identical to what you entered for the first node.
Tip: If your FileNet P8 environment is highly available, make sure you point
to the virtual names of the highly available Content Engine, Application
Engine, and Process Engine installations. For example, for Content Engine
use:
http://CE_farm_name:load_balancer_port#/wsi/FNCEWS40MTOM/
Where CE_farm_name is the virtual name of your Content Engine farm and
load_balancer_port# is the port for the load balancer for your Content Engine
farm.
v Complete the installation on each node before beginning the installation on
the next node.
v Use the same settings on each subsequent node as you did on the first node.
5. Verify that the installation was successful. Check the installation log at
C:\Program Files\IBM\FileNetConnectorForSharePointWebParts\
sharepoint_web_parts_install_log_2.2.2.txt.
6. Verify that the encryption key specified in the web.config file for each
deployed web application is identical for all nodes.
a. Open the web.config file for each web application on each farm node. The
file is typically located in C:\Inetpub\wwwroot\wss\VirtualDirectories\
port# where port# is unique for each installation.
b. Verify that the entry for machineKey is identical for each web application on
all nodes. If you installed the component by using identical input, these
13
entries should not differ. If they do differ, select one of the entries and copy
it to the web.config files on all the other nodes.
7. Specify Application Pool Security Account. Follow the instructions in
Specifying the Application Pool security account on page 10.
8. Add and Configure IBM FileNet Connector for Microsoft SharePoint Web Parts.
For each applicable SharePoint web application server, follow the instructions
in the "Add web parts" and the "Configure web parts" help topics in the IBM
FileNet P8 information center (see reference links below) and use the virtual
URLs for Content Engine, Process Engine, and Application Engine.
Related information
Add web parts
IBM FileNet Connector for SharePoint Web Parts installs custom web parts in your
SharePoint library. IBM FileNet web parts are added to a SharePoint site page in
the same manner as other web parts. This topic lists the basic steps for adding a
web part or creating a search center page. See your SharePoint documentation for a
full discussion of either option.
Configure web parts
To install documentation for IBM FileNet P8 expansion products, you must copy
that documentation onto the application server where IBM FileNet P8 Platform
documentation is already installed. You then rebuild the documentation search
index.
Verifying IBM FileNet Connector for Microsoft SharePoint Web

Parts installation in a farm environment
After you deploy IBM FileNet Connector for Microsoft SharePoint Web Parts in a
highly available environment, you must verify that IBM FileNet P8 and SharePoint
are operating correctly.
About this task

To verify installation in a farm environment:
Procedure
1. Ensure that IBM FileNet P8 and SharePoint are running.
a. To verify that IBM FileNet P8 is running, log in to Workplace or Workplace
XT, and log in to Enterprise Manager.
b. To verify that SharePoint can connect to IBM FileNet P8, log in to
SharePoint and verify that you can browse your object store by using a
Browse web part. Add a document to the object store using SharePoint.
c. Log in to Workplace or Workplace XT or log in to Enterprise Manager and
verify that the document you added is visible.
2. Verify that IBM FileNet Connector for Microsoft SharePoint Web Parts connects
after Content Engine failover.
a. Fail over your highly-available Content Engine.
b. Verify that SharePoint can connect to IBM FileNet P8. Log in to SharePoint
and verify that the various web parts connect to IBM FileNet P8 and that
you can browse, view, and open documents in your object store through
SharePoint web parts.
3. Verify that IBM FileNet Connector for Microsoft SharePoint Web Parts connects
after Application Engine failover.
a. Fail over your highly-available Application Engine.
14
b. Verify that SharePoint can connect to IBM FileNet P8. Log in to SharePoint
and verify that the various web parts connect to IBM FileNet P8 and that
you can open documents in your object store through SharePoint web parts.
4. Verify that SharePoint clients have access after a SharePoint failover.
a. Fail over your highly-available SharePoint server.
b. Verify that the SharePoint client can still connect to SharePoint and that
SharePoint can connect to IBM FileNet P8.
15
16
Upgrading IBM FileNet Connector for SharePoint Web Parts

Follow these guidelines to upgrade IBM FileNet Connector for Microsoft
SharePoint Web Parts.
Planing the upgrade

You must prepare your environment for an upgrade of IBM FileNet Connector for
Microsoft SharePoint Web Parts. Review this information thoroughly before you
start the upgrade.
Note:
v The upgrades described in this guide assume that you have retained your basic
platform configuration from the previous release.
v Before you upgrade the IBM FileNet Connector for Microsoft SharePoint Web
Parts software, you must upgrade your SharePoint server to SharePoint Server
2010 with the SharePoint 2010 user interface active.
v Upgrades to version 2.2.2.0 must be run on the SharePoint servers where version
2.2.1.x is installed.
Attention: Non-English Upgrade Consideration: If the IBM FileNet Connector for
Microsoft SharePoint Web Parts - Language Pack 2.2.1.0 is installed, you must
uninstall this Language Pack before installing FileNet Connector for Microsoft
SharePoint Web Parts 2.2.2.0.
Authentication and Database Requirements
This upgrade of FileNet Connector for Microsoft SharePoint Web Parts
supports both Windows Integrated Authentication and IBM FileNet
Credential Store as methods of authentication. If your previous installation
used a Microsoft SQL Server user profile database for authentication and
you want to switch to Windows Integrated Authentication with this
upgrade, you must install and configure Windows Integrated
Authentication on IBM FileNet P8 Platform and on the SharePoint before
running the installation program.
If you choose Windows Integrated Authentication and your previous
installation of FileNet Connector for Microsoft SharePoint Web Parts used a
Microsoft SQL Server user profile database for authentication, you should
remove the Microsoft SQL user profile database and the Application Pool
Security Account information that was created for the previous installation.
For details on:
How the user profile database was created, see (Optional) Creating a
Microsoft SQL Server User Profile Database manually on page 9.
v How the Application Pool Security Account was created, see
Specifying the Application Pool security account on page 10.
17
Related information
Download PDFs of IBM FileNet P8 Platform documentation.
Upgrading to SharePoint Server 2010

Before you can upgrade the IBM FileNet Connector for Microsoft SharePoint Web
Parts software to version 2.2.2, you must upgrade the SharePoint server to
SharePoint Server 2010.
Restriction: The two following visual upgrade options must be selected during
upgrade to SharePoint 2010 which will enable the new user experience:
v Change existing SharePoint sites to use the new user experience.
v Reset all customized pages to their original templates.
Installation to Microsoft SharePoint servers that have been upgraded to SharePoint
2010 with visual upgrade options other than those listed above are not supported.
Ensure you refer to the Microsoft TechNet article regarding requirements for
upgrading to SharePoint Server 2010: http://technet.microsoft.com/en-us/library/
cc263322.aspx
Upgrading IBM FileNet Connector for Microsoft SharePoint Web Parts

software
Use this information to upgrade IBM FileNet Connector for Microsoft SharePoint
Web Parts software either silently or interactively.
Important: Depending on your configuration, certain folders may have to be
excluded from antivirus scanning in order to complete the IBM FileNet Connector
for Microsoft SharePoint Web Parts software upgrade. See the following Microsoft
knowledge base article: http://support.microsoft.com/kb/952167. Exclude items
listed under both SharePoint Foundation 2010 and SharePoint Server 2010.
Upgrading IBM FileNet Connector for Microsoft SharePoint

Web Parts silently
You can upgrade IBM FileNet Connector for Microsoft SharePoint Web Parts
silently by creating a response file that contains the options to pass to the
installation program during installation. A sample response file is included with
the FileNet Connector for Microsoft SharePoint Web Parts installation program.
Procedure
privileges.
2. Set the Microsoft Windows User Access Control settings to minimum or to
disabled.
3. From the IBM FileNet Connector for Microsoft SharePoint Web Parts software
package, open the silent_installer.properties file in a text editor and enter the
appropriate responses by following the directions in the file.
Important: Under the Choose Deployment Method property, only Single
deployment is a valid, supported entry (1). Do not set this property to All (0).
Deployment to all on an upgrade is not supported. If you want to deploy to all
18
web applications using the installation program, you must completely remove
the previous installation and all web parts that have been added to pages and
then run a new IBM FileNet Connector for Microsoft SharePoint Web Parts
2.2.2.0 installation.
Remember: The documentation set that was provided with previous versions
of IBM FileNet Connector for Microsoft SharePoint Web Parts is no longer
supported. You can point the documentation URL in your web parts to the
current online version of the IBM information center on www.ibm.com by
entering the following URL for the DOCUMENTATION_SERVER_URL
parameter:
http://publib.boulder.ibm.com/infocenter/p8docs/
v5r1m0/topic/com.ibm.p8.doc/sp_help/_start_here.htm
Alternatively, if you have a locally installed information center, you can enter
the appropriate URL for the DOCUMENTATION_SERVER_URL parameter.
4. Open a command prompt and run the following command from the
appropriate directory:
2.2.2.0-SPWP.exe -i silent -f
silent_installer.properties
5. Grant the SharePoint application pool security account owner access rights
(db_owner) to the session state database that was created during installation. See
your Microsoft SQL Server documentation for details on how to set database
user privileges.
Upgrading IBM FileNet Connector for Microsoft SharePoint

Web Parts interactively
You can upgrade IBM FileNet Connector for Microsoft SharePoint Web Parts
About this task

Procedure
privileges.
2. Set the Microsoft Windows User Access Control settings to minimum or to
disabled.
3. Launch the 2.2.2.0-SPWP.exe file.
4. Complete the FileNet Connector for Microsoft SharePoint Web Parts installation
program wizard screens to upgrade the software.
Important: During the upgrade, the URLs you entered for your previous
installation are displayed. The Documentation Server URL that was used for
your previous installation is no longer valid and must be updated. The
Documentation Server URL field in the upgrade installer pre-populates with a
URL that points to the current online version of the IBM information center on
www.ibm.com:
Alternatively, if you have a locally installed information center, you can enter
the appropriate URL in the Documentation Server URL field.
Upgrading IBM FileNet Connector for SharePoint Web Parts
19
5. Grant the SharePoint application pool security account owner access rights
(db_owner) to the session state database that was created during installation. See
your Microsoft SQL Server documentation for details on how to set database
user privileges.
Updating the IBM FileNet Connector for Microsoft SharePoint Web

Parts documentation URL
You must update the documentation URL for all deployed web parts.
About this task

The documentation set that was provided with previous versions of IBM FileNet
Connector for Microsoft SharePoint Web Parts is no longer supported. You can
point the documentation URL in your web parts to the current online version of
the IBM information center on www.ibm.com. Alternatively, if you have a locally
installed information center, you can enter the appropriate URL in each web part.
Procedure
1. Access each web part in edit mode.
2. Click Advanced.
3. Enter the following URL in the Help URL field. This URL points to the online
version of the IBM information center on www.ibm.com:
Note: If you have a locally installed IBM FileNet P8 information center, enter
the appropriate URL in each web part.
4. Click Apply.
5. Save the changes.
20
Maintaining IBM FileNet Connector for Microsoft SharePoint

Web Parts
Once you have installed and configured IBM FileNet Connector for Microsoft
SharePoint Web Parts, you can perform the following tasks to manually deploy the
components to additional SharePoint web applications.
Manually deploying web parts to new web applications

If you have added new SharePoint web applications since you installed IBM
FileNet Connector for Microsoft SharePoint Web Parts and you would like the web
parts to be available from these new SharePoint applications, you must use the
following manual steps to deploy the FileNet Connector for Microsoft SharePoint
Web Parts to each new web application.
About this task

Important: You must have already run the IBM FileNet Connector for Microsoft
SharePoint Web Parts 2.2.2.0 installation program on the SharePoint server for
these procedures to complete successfully. All paths in this section are stated as the
default locations.
To manually deploy the FileNet Connector for Microsoft SharePoint Web Parts:
Procedure
1. Access the SharePoint 2010 Management Shell and stop the Administration
service by running the following command:
net stop SPAdminV4
2. Deploy the IBM FileNet Web Parts solution to the new SharePoint web
application by executing the following STSADM command:
STSADM.exe" -o deploysolution -name FnSPWebParts.wsp -immediate -url
http://localhost:PORT
For example,
STSADM.exe" -o deploysolution -name FnSPWebParts.wsp -immediate -url
http://SDE233:80
3. Deploy the IBM FileNet Administration Web Part to the new SharePoint web
application by executing the following STSADM command:
STSADM.exe" -o deploysolution -name FnSPAdmin.wsp -immediate -url
http://localhost:PORT
For example:
STSADM.exe" -o deploysolution -name FnSPAdmin.wsp -immediate -url
http://SDE233:80
4.
Run all spooled commands by executing the following STSADM command:

STSADM.exe" -o execadmsvcjobs
5. Start the SharePoint 2010 Administration service by running the following

command:
net start SPAdminV4
21
Updating the web.config file

Depending on the method of authentication used for your configuration, choose a
method of updating the web.config file.
(IBM FileNet credential store authentication) Updating the

web.config file
Use this procedure to update the web.config file with the appropriate entries.
About this task

Important: Any edits to the web.config file must be saved in UTF-8 format. For
example, make the edits using Notepad and use save-as UTF-8.
(IBM FileNet credential store authentication) To update the web.config file:
Procedure
1. Add the following entry before the <system.web> element in the SharePoint
web.config file. Replace the Database_Name and Database_Instance variables
with the appropriate entries:
<connectionStrings>
<add name="Database_Name"
connectionString="Data Source=Database_Instance;
Initial Catalog=FileNetProfile;Integrated
Security=True" providerName="System.Data.SqlClient" />
</connectionStrings>
For example:
<connectionStrings>
<add name="FileNetProfileDB" connectionString="Data Source=localhost;
Initial Catalog=FileNetProfile;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
2. Add the following entry to the web.config file in the <system.web> section just
ahead of the <authorization> element:
<profile enabled="true"
defaultProvider="FileNetProfileProvider">
<providers>
<add name="FileNetProfileProvider"
type="System.Web.Profile.SqlProfileProvider, System.Web,
Version=2.0.3600.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="FileNetProfileDB"
applicationName="FileNet"/>
</providers>
<properties>
<add name="FileNetUserName" type="String"/>
<add name="FileNetPassword" type="String"/>
</properties>
</profile>
3. Add the following entry to the <configuration>/<system.web>/

<compilation>/<assemblies> section of the SharePoint web.config file. Replace
CE_.NET_API_version_number below for the correct version of FileNet .NET
API:
22
<add assembly="FileNet.Api, Version=CE_.NET_API_version_number,

Culture=neutral,
PublicKeyToken=63FC2FB3FDEEF4F1" />
<add assembly="Microsoft.Web.Services3,
Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
For example:
<add assembly="FileNet.Api, Version=4.0.0.0,
Culture=neutral,PublicKeyToken=63FC2FB3FDEEF4F1" />
<add assembly="Microsoft.Web.Services3,
4.
Change the value of enableSessionState= attribute from false to true on the

<configuration>/<system.web>/<pages> element: For example:
<pages enableSessionState="true"
enableViewState="true" enableViewStateMac="true"
validateRequest="false"
pageParserFilterType=
"Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter,
Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" asyncTimeout="7">
5.
Add the following entry to the <configSections> section, ahead of the

<sectionGroup name="SharePoint"> section:
<section name="FileNetConfig"
type="System.Configuration.NameValueSectionHandler, System,
PublicKeyToken=b77a5c561934e089" />
6. Add the following entry after the <configSections> section, ahead of the
<SharePoint> section. Replace the Encryption_Key variable with an encryption
key - Enter the key that was used to encrypt the stored user names and
passwords in the user profile database. As a best practice, encrypt this key
using the appropriate Microsoft encryption tool.
<FileNetConfig>
<add key="ProfileKey" value="Encryption_Key" />
</FileNetConfig>
For example:
<FileNetConfig>
<add key="ProfileKey" value="1234567" />
</FileNetConfig>
7.
Add the following entry to the <system.web> / <security policy> section:

<trustLevel name="FileNetCustom"
policyFile="C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\12\config\filenetcustom.config" />
Note: The filenetcustom.config policy file was created when you ran the
IBM FileNet Connector for Microsoft SharePoint Web Parts installation
program.
8. Add the following entry above the <webparts> section:
<trust level="FileNetCustom" originUrl="" />
9.
For Microsoft SharePoint Server installations, add the following entry within
the <configuration><appsettings> element:
<add key="FileNetAuthenticationMode"
value="CredentialStore" />
<add key="FileNetMetaDataCacheTimeoutValue" value="14400000" />
10. For Microsoft SharePoint Server Enterprise Installations, add the following
entry after the <configuration> element:
Maintaining IBM FileNet Connector for Microsoft SharePoint Web Parts
23
<appSettings>
value="CredentialStore" />
<add key="FileNetMetaDataCacheTimeoutValue"
value="14400000" />
</appSettings>
11.
Add the following entry to the <configuration>/<system.webServer>/

<modules> element:
<add name="Session" type="System.Web.SessionState.SessionStateModule" />
12.
Add the following entry to the <configuration>/<system.web> element:

<sessionState mode="SQLServer" timeout="60" allowCustomSqlDatabase="true"
sqlConnectionString="Data Source=database instance;Initial
Catalog=ASPState;Integrated Security=True;Enlist=False;Connect Timeout=15" />
Replace database instance with the name of the database instance you entered
when you installed IBM FileNet Connector for Microsoft SharePoint Web
Parts.
(Integrated Windows authentication) Updating the web.config

file
You can use this procedure to update the web.config file with the appropriate
entries.
Procedure
1. Add the following entry to the <configuration>/<system.web>/
<compilation>/<assemblies> section of the SharePoint web.config file. Replace
CE_.NET_API_version_number below with the correct version of FileNet .NET
API:
<add assembly="FileNet.Api, Version=CE_.NET_API_version_number,
add assembly="Microsoft.Web.Services3,
For example:
<add assembly="FileNet.Api, Version=4.0.0.0,
add assembly="Microsoft.Web.Services3,
2. Change the value of enableSessionState= attribute from false to true on the

<configuration>/<system.web>/<pages> element. For example:
<pages enableSessionState="true"
enableViewState="true" enableViewStateMac="true"
validateRequest="false"
pageParserFilterType=
"Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter,
Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" asyncTimeout="7">
3.
Add the following entry to the <configSections> section, ahead of the

<sectionGroup name="SharePoint"> section:
<section name="FileNetConfig"
type="System.Configuration.NameValueSectionHandler, System,
PublicKeyToken=b77a5c561934e089" />
4.
Add the following entry to the <system.web> / <security policy> section:

<trustLevel name="FileNetCustom"
policyFile="C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\12\config\filenetcustom.config" />
24
Note: The filenetcustom.config policy file was created when you ran the
IBM FileNet Connector for Microsoft SharePoint Web Parts installation
program.
5.
Add the following entry above the <webparts> section:

<trust level="FileNetCustom" originUrl="" />
6.
Add the following entries to the <authorization> section:

<authorization>
<allow users="*" />
<deny users="?" />
</authorization>
7.
For Microsoft SharePoint Server installations, add the following entry within
the <configuration><appsettings> element:
value="Kerberos" />
value="14400000" />
8. For Microsoft SharePoint Server Enterprise Installations, add the following

entry after the <configuration> element:
<appSettings>
value="Kerberos" />
value="14400000" />
</appSettings>
9.
Ensure the following two entries are in the <system.web> section:

<authentication mode="Windows" />
<identity impersonate="true" />
10.
Add the following entry to the <configuration>/<system.webServer>/

<modules> element:
<add name="Session" type="System.Web.SessionState.SessionStateModule" />
11.
Add the following entry to the <configuration>/<system.web> element:

<sessionState mode="SQLServer" timeout="60" allowCustomSqlDatabase="true"
sqlConnectionString="Data Source=database instance;Initial
Catalog=ASPState;Integrated Security=True;Enlist=False;Connect Timeout=15" />
Replace database instance with the name of the database instance you entered
when you installed IBM FileNet Connector for Microsoft SharePoint Web Parts
Updating .webparts files with IBM FileNet P8 URLs

Update the .webparts files with the IBM FileNet P8 URLs in order to pre-populate
Web Parts with the URLs by default when a user adds them to a page.
Before you begin

Back up your .webparts files before you make edits.
About this task

Important: Any edits to the .webparts files must be saved in UTF-8 format. For
example, make the edits using Notepad and use Save-As UTF-8.
To update .webparts files with the IBM FileNet P8 default web part URLs:
Maintaining IBM FileNet Connector for Microsoft SharePoint Web Parts
25
When you deploy the IBM FileNet web parts, new .webparts files are created
automatically in a new wpcatalog directory within the virtualdirectories folder
of each web application to which you deploy the web parts. For example:
C:\Inetpub\wwwroot\wss\VirtualDirectories\80\wpcatalog\
Note: For non-English installations, an additional set of .webparts files is located

in a directory that matches the locale. You must edit the .webparts file within the
directory that's appropriate for the non-English installation. For example, if your
installation is localized for the French language, you would add the entries for this
task to the .webparts files located in:
C:\Inetpub\wwwroot\wss\VirtualDirectories\80\wpcatalog\fr\
One .webparts file is created for each IBM FileNet web part that is deployed. For
example:
ab39a08f-52d9-49c7-a608-f797f52fafb6_FnAdvancedSearch.webpart
For each .webparts file, add the following lines in the <properties> section and
enter the appropriate URL path:
<property name="ServerUrl"
type="string">P8_CE_URL</property>
<property name="AppEngineUrl" type="string">P8_AE_URL</property>
<property name="PEUrl" type="string">P8_PE_URL</property>
<property name="PEConnectionPoint" type="string">
P8_Connection_Point_URL
</property>
<property name="HelpUrl" type="string">P8_help_URL</property>
<property name="HelpMode" "type="string">modal</property>
For the P8_help_URL, enter the following URL which points to the online version
of the IBM information center on www.ibm.com:
Note: If you have a locally installed IBM FileNet P8 information center, enter the
appropriate URL for the P8_help_URL variable.
26
Removing IBM FileNet Connector for Microsoft SharePoint

Web Parts
You can remove IBM FileNet Connector for Microsoft SharePoint Web Parts either
interactively or silently, depending on the way in which it was installed.
Note: You must uninstall IBM FileNet Connector for Microsoft SharePoint Web
Parts in the same manner that it was installed. If the software was installed
silently, then you must uninstall silently. If the software was installed interactively,
then you must uninstall interactively.
Uninstalling IBM FileNet Connector for Microsoft SharePoint Web Parts

interactively
You can uninstall IBM FileNet Connector for Microsoft SharePoint Web Parts
uninstall program.
About this task

Access any pages that contain IBM FileNet Connector for Microsoft SharePoint
Web Parts and remove them as follows:
Procedure
1. Launch SharePoint in a browser and log in as an administrator.
2. Access the page that contains the Web Parts you want to remove.
3. Click the Web Part drop-down menu button and select Edit Web Part.
4. Click the Edit drop-down menu and select Delete.
5. Select OK to remove the Web Part.
6. Run the FileNet Connector for Microsoft SharePoint Web Parts uninstall
program:
a. From the Windows Control Panel, select Add or Remove Programs.
b. Select IBM FileNet Connector for Microsoft SharePoint Web Parts .
c. Click Change/Remove.
d. Select Complete Uninstall and click Next.
e. Click Done to complete the uninstall and exit.
Important: If the software was originally installed silently, then the
uninstall will run silently.
7. From Microsoft SQL Server, remove the user profile database and then remove
the NT AUTHORITY\NETWORK SERVICE user, or other application pool user,
that you added when you installed IBM FileNet Connector for Microsoft
SharePoint Web Parts from the Security\Logins node.
8. Remove the session state database (ASPState).
27
Uninstalling IBM FileNet Connector for Microsoft SharePoint Web Parts

silently
You can silently uninstall IBM FileNet Connector for Microsoft SharePoint Web
Parts only on implementations that were silently installed.
Procedure
1. Log on to the SharePoint machine using an account that has local administrator
privileges.
2. Access any pages that contain IBM FileNet Connector for Microsoft SharePoint
Web Parts and remove them as follows:
a. Access the SharePoint site in a browser and log in as an administrator.
b. Access the page that contains the Web Parts you want to remove.
c. Click the Web Part drop-down menu button and select Modify Shared Web
Part.
d. Click the Edit drop-down menu and select Delete.
e. Select OK to remove the Web Part.
3. Open a command prompt and navigate to the Uninstall IBM FileNet
Connector for SharePoint Web Parts subdirectory in the installation location
(default location is C:\Program Files\IBM\
FileNetConnectorForSharePointWebParts\Uninstall IBM FileNet Connector
for Microsoft SharePoint Web Parts).
4. Execute the following command:
Uninstall IBM FileNet Connector for SharePoint Web
Parts.exe -i silent
The IBM FileNet Connector for Microsoft SharePoint Web Parts silently
uninstalls.
5. From Microsoft SQL Server, remove the user profile database and then remove
the NT AUTHORITY\NETWORK SERVICE user (or comparable user) from the
Security\Logins node.
6. Remove the session state database (ASPState).
28
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
29
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
30
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol ( or ), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common
law trademarks in other countries. A current list of IBM trademarks is available on
the Web at http://www.ibm.com/legal/copytrade.shtml (www.ibm.com/legal/
copytrade.shtml).
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in
the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both. Other company, product, and service names may be trademarks
or service marks of others.
Notices
31
32
Index
A
Application Engine 1
authentication
IBM FileNet credential store
Windows integrated 7
Microsoft Windows SharePoint

Services 1
7, 10
O
operating system requirements
localized 6
C
certificate
SSL 2
components
manual deployment 21
configuration
SSL 2
configuration file
update, IBM FileNet credential
store 22
update, Windows authentication
Content Engine 1
requirements 6
P
planning
installation 1
populate URLs
Web Parts files
preparing
installation 2
24
database
user profile 9
deployment
manual 21
Web Parts 21
R
2
S
security
application pool user
SSL
configuration 2
H
host name
SSL 2
10
I
installation 1, 9
default location 1, 2
highly available 12, 14
interactive 9
localized 6
planning 1
preparing 2
silent 10
installation and upgrade worksheet
L
languages
supported 7
localized environment
25
remove
Web Parts software 27
roles
definition of installation
Web Parts file

update 25
Web Parts software
remove 27
Workplace XT 1
worksheet
autofiltering and sorting 5
running the customize macro 4
using the installation and upgrade
worksheet 3
uninstall
interactively 27
silently 27, 28
update
Web Parts file 25
update, IBM FileNet credential store
configuration file 22
update, Windows authentication
configuration file 24
updating, web.config file 22
upgrade
authentication database 17
interactive 18, 19
planning 17
SharePoint Server 2010 18
silent 18
user profile database 9
W
M
maintenance
Web Parts 21
Microsoft Office SharePoint Server
Microsoft SQL Server 1
Web Parts
adding 11
configuring 11
deployment 21
installation 9, 12
33
34

Product Number: 5724-R96
GC31-5528-04

Filenet Sharepoint Connector Guide

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Filenet Sharepoint Connector Guide

Загружено:

Авторское право:

Доступные форматы

IBM FileNet Connector for SharePoint Web Parts

Installation and Upgrade Guide

IBM FileNet Connector for SharePoint Web Parts

Installation and Upgrade Guide

Installing IBM FileNet Connector for

Copyright IBM Corp. 2001, 2011

Maintaining IBM FileNet Connector for

Upgrading IBM FileNet Connector for

Upgrading IBM FileNet Connector for Microsoft

Removing IBM FileNet Connector for

Installation and Upgrade

ibm.com and related resources

Support and assistance

Product Documentation for FileNet http://www.ibm.com/support/docview.wss?rs=3278

How to send your comments

Copyright IBM Corp. 2001, 2011

Installation and Upgrade

Installing IBM FileNet Connector for Microsoft SharePoint

Planning the Installation

Copyright IBM Corp. 2001, 2011

Preparing for installation

Definition of installation roles

Information technology administrator

Installation and Upgrade

Application server administrator

IBM FileNet P8 administrator

Using the installation and upgrade worksheet

Installation and Upgrade

Non-English environment installation

Installing IBM FileNet Connector for Microsoft SharePoint Web Parts

Operating System Requirements

Content Engine Requirements

Installation and Upgrade

Authentication and database requirements

Restriction: For this method of authentication, Application Engine /

Installation and Upgrade

(Optional) Creating a Microsoft SQL Server User Profile

About this task

4. Verify the database has been created.

Installing IBM FileNet Connector for Microsoft SharePoint Web

Installing IBM FileNet Connector for Microsoft SharePoint Web

About this task

Installing IBM FileNet Connector for Microsoft SharePoint Web Parts

Installing IBM FileNet Connector for Microsoft SharePoint Web

Specifying the Application Pool security account

Before you begin

About this task

Installation and Upgrade

Adding and configuring IBM FileNet Connector for Microsoft

Installing IBM FileNet Connector for Microsoft SharePoint Web Parts

Installing a highly available IBM FileNet Connector for Microsoft

Installing IBM FileNet Connector for Microsoft SharePoint Web

About this task

Installation and Upgrade

Verifying IBM FileNet Connector for Microsoft SharePoint Web

About this task

Installation and Upgrade

Installing IBM FileNet Connector for Microsoft SharePoint Web Parts

Installation and Upgrade

Upgrading IBM FileNet Connector for SharePoint Web Parts

Planing the upgrade

Copyright IBM Corp. 2001, 2011

Upgrading to SharePoint Server 2010