Make sure you have IIS with .Net 4.5, ASP.Net and MSMQ installed. Stop the “Default website”.
Microsoft SQL SErver
The Microsoft SQL Server must be set up with support for Filestream (right-click on the server object, choose Properties->Advanced, and select “Full access enabled”).
You may let the inRiver PIM use three different dabases (highly advisable):
- DB for the inRiver PIM itself
- DB for resourcdes (images, PDFs, etc)
- DB for logging
You should set up these three databases before you start the inRiver PIM installation. For the resources database, remember to set up filestream in addition to the usual data- and log-files. First, add a filestream using “Add Filegroup”:
When this is set up, you can add the filestream you just created in the above step:
Unfortunately, the inRiver PIM installation does not create the logging table for the logging database automatically. Use the following script:
CREATE TABLE [dbo].[Message](
[Level] [nchar](10) NOT NULL,
[Component] [nchar](50) NOT NULL,
[Method] [nchar](50) NOT NULL,
[Message] [nvarchar](max) NOT NULL,
[EventTime] [datetime] NOT NULL,
[UserName] [nchar](50) NULL,
[SessionId] [nchar](128) NULL,
[Exception] [nvarchar](max) NULL
In case the inRiver PIM installation does not create a table for resources, the table can be created using this script:
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
CREATE TABLE [dbo].[ResourceFile](
[Id] [int] IDENTITY(1,1) NOT NULL,
[Data] [varbinary](max) FILESTREAM NULL,
[RowGuid] [uniqueidentifier] ROWGUIDCOL NOT NULL,
[Filename] [varchar](256) NULL,
[FileSize] [bigint] NULL,
[Extension] [varchar](16) NULL,
[DateCreated] [datetime] NOT NULL,
CONSTRAINT [PK_ResourceFile] PRIMARY KEY CLUSTERED
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] FILESTREAM_ON [InRiver_184.108.40.20683_filestream], UNIQUE NONCLUSTERED
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] FILESTREAM_ON [InRiver_220.127.116.1183_filestream]
ALTER TABLE [dbo].[ResourceFile] ADD CONSTRAINT [DF_ResourceFile_RowGuid] DEFAULT (newid()) FOR [RowGuid]
You can find the installation files at http://wiki.inriver.com (you need to register for access).
When you run the installation, make sure to select the “Advanced installation” option, so that you can set connectionstrings, select file locations, etc.
After the installation, you need to set up the config files for the inRiver Server and the inRiver Connect. There are files called config.sample that you can use, so just edit these files, and remove “sample” from their filenames. In the inRiver.Server.exe.config file, set ut the connectionstrings for the three databases, and also edit the logging option so that logging to database is selected. Similarly for the inRiver.Integration.exe.config file.
To set up dependencies for the windows services, run the following from a command prompt:
sc.exe config InRiverConnectWindowsService6 depend= InRiverServerWindowsService6
sc.exe config InRiverServerWindowsService6 depend= MSMQ
Now you can start the inRiver Connect service. This is depending on the inRiver Server service, so both will start up.
Default username/password for the inRiver PIM is pimuser1/pimuser1.
I struggled a bit with the Filestream setup in SQL Server, here are a couple of good articles: