Siebel Collaboration Guide > Getting Started with Siebel Collaboration >
Installing Configuration Files for Siebel-SharePoint Integration
This procedure describes copying and editing these files and importing the registry files:
- WebParts.reg and IntegrationWebService.reg. These are registry key files used by the Siebel Web Part and the Siebel-SharePoint Integration Web Service.
- siebelSR.xsl and siebelOpp.xsl. These are XSL stylesheets used to control layout and formatting properties of the Siebel Web Part for service request and opportunity objects.
- Config.xml. This file contains configuration and customization settings used by the Siebel-SharePoint Integration Web Service and the Siebel Web Part.
Installing and configuring the configuration files
- Copy the directory
\config :
- Edit the file WebParts.reg that is in the
\config directory that you copied in Step 1:
|
|
Integration Web Service URI |
http://sharepoint_server:port/siebelsharepointintegration.asmx
|
Service Request XSL File |
C:\\Siebel\\SharePointIntegration\\config\\siebelSR.xsl
|
Opportunity XSL File |
C:\\Siebel\\SharePointIntegration\\config\\siebelOpp.xsl
|
EnableEventLogging |
Log level for the Siebel Web Part:
- 1 (to enable log) This is the recommended value.
- 0 (to disable log)
You can view log entries in the Event Viewer (Application log). |
- Edit the file IntegrationWebService.reg that is in the
\config directory that you copied in Step 1:
|
|
Configuration File |
C:\\Siebel\\SharePointIntegration \\config\\config.xml
|
EnableWebServiceEventLogging |
Log level for the Siebel Web Service:
- 1 (to enable log)
- 0 (to disable log) This is the recommended value.
You can view log entries in the Event Viewer (Application log). |
- Import the two registry files into the registry.
This setting can be verified at HKEY_LOCAL_MACHINE\SOFTWARE\Siebel Systems, Inc.\Collaboration\Sharepoint .
- Edit the config.xml file that is in the
\config directory that you copied in Step 1:
- In the SiebelConnectInfo element, edit these attributes:
|
Suggested Value and Comments |
WebServiceURI |
Specify the URI for the Siebel inbound Web Service. The format for this URI is http://siebel_web_server/CustAppSvcs_enu/start.swe?SWEExtSource=CustomUI&SWEExtCmd=Execute&WSSOAP=1
NOTE: This is the same URI that you enter when Setting Up Inbound and Outbound Web Services for Siebel Collaboration.
|
Username |
Specify Siebel user credentials to access the Siebel application. |
Password |
MaxSessions |
Session tokens are used by the Siebel Web Part to improve response time when communicating with the Siebel application. The MaxSessions attribute sets the maximum number of session tokens that can be stored. Typically, set this number a little higher than the expected average user load. |
For example,
<SiebelConnectInfo WebServiceURI="http://siebel_web_server/CustAppSvcs_enu/start.swe?SWEExtSource=CustomUI&SWEExtCmd=Execute&WSSOAP=1" Username="CHANGE_ME" Password="CHANGE_ME" MaxSessions="10" />
- In the SharepointConfigInfo element, edit these attributes:
|
Suggested Value and Comments |
WebServerURI |
SharePoint portal site |
AdminUsername |
The user entered here must be a SharePoint Administrator. TIP: A SharePoint Administrator is either a member of the Administrators group on the SharePoint host machine or a member of the SharePoint Administration group.
You can specify the name with or without the domain. If you do not specify a domain name, specify it in the Domain attribute. For example, AdminUsername="domain\Administrator" or AdminUsername="Administrator" Domain="domain" |
AdminPassword |
Password for the AdminUsername user. |
SecurityToken |
Enter the same string that you entered for the SecurityToken in your Siebel CFG file. (See Editing the Siebel Application CFG File for Siebel Collaboration.) |
Domain |
Use this attribute to specify the domain name. If you did not specify a domain name with the AdminUsername attribute, this domain is used. NOTE: The domain name is case sensitive.
|
AddSiteToPortalSiteList |
Determines if the team space appears in the site list on the SharePoint portal site. Set to TRUE or FALSE. |
MaxConnections |
This attribute determines the maximum number of connections between the Siebel-SharePoint Integration Web Service and SharePoint. Increasing this value increases memory usage but can improve speed of integration. Set and adjust the value according to expected load. |
For example,
<SharepointConfigInfo WebServerURI=http://PortalServer:88 AdminUsername="domain\Administrator" AdminPassword="sample" SecurityToken="l5t42j6d9w73" Domain="domain" AddSiteToPortalSiteList="TRUE" MaxConnections="50"/>
- Edit the UserGroups elements.
The UserGroups identify which users are added as members of a team space and what rights they are given. You can specify users to be added to all team spaces and users to be added to those team spaces associated with a particular object. Rights assigned to a user are specified using SharePoint role identifiers. Users are identified by an ADSI group name or a user login account on the SharePoint host machine.
- Locate the first UserGroups element. This element identifies the users who are added to all team spaces.
- Add a UserGroup element for each user group that you want to have access to all team spaces. Role is the SharePoint Role identifier, and Login is the login account for the user on the SharePoint host machine.
<SiebelCollaborationConfig> .... <UserGroups> <UserGroup Role="Administrator"> <User Login=" CHANGE_ME" /> </UserGroup> <UserGroup Role="Contributor"> <User Login=" CHANGE_ME" /> </UserGroup> </UserGroups> .... </SiebelCollaborationConfig>
- Locate the UserGroups element contained in the ObjectType elements. This element identifies the users who are added to team spaces for that object. For example, the following text shows the UserGroups element for the team spaces associated with service request objects:
<ObjectTypes> <ObjectType Type="Service Request" SitePrefix="SR" SiteTemplate="SIEBEL#0" SiteTheme="SIEBEL" ActiveDays="30" ActiveNewDays="1" UserRole="Contributor"> . . . <UserGroups> <UserGroup Role="Administrator"> <User Login=" CHANGE_ME" /> </UserGroup> </UserGroups> <UserGroup Role="Contributor"> <User Login=" CHANGE_ME" /> </UserGroup> </UserGroups> . . . </ObjectType>
- Add a UserGroup element for each user group you want to have access to the team spaces for the object.
- Restart Internet Information Services (IIS).
|