Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Basic introduction into establishing a connection with a data source can be found here: How to connect to Content Data-source?

EpiServer MS SQL Connection

This connection is a primary one and is used to export/import content. iLangL Cloud uses this string to connect directly to Microsoft SQL Server database. 

To make this connection work there should be an opened connection between an MS SQL server (EpiServer database is hosted at) and iLangL's Cloud Server.

Here is a reference to how to connect to an SQL Server over the Internet - Connecting to SQL Server over the Internet

And video:

Parameters:

  • Server(Required) - a name or a network address of an SQL Server instance you are connecting to;
  • Port(Optional) - a server port, will be added to a server name 'Server':'Port';
  • User Id(Required) - an SQL Server login account;
  • Password(not always required *) - a password for an SQL Server account;
  • Database(Required) - a database name;
  • Table prefix(Optional) - a database table prefix for your CMS installation (usually empty for EpiServer);

*

In case of using Integrated security on customer's side, connection without password can be established using Local connection


Here is how a final connection string to a Generic Content Provider might look like:

Server=[Server]:[Port];Database=[Database];Uid=[User Id];Pwd=[Password];

EpiServer HTTP Connection

iLangL Cloud imports content to an EpiServer CMS via MS SQL database connection. EpiServer uses a content cache to optimize server workload and increase performance.

When content is imported directly to a database, EpiServer web application doesn't know about this operation and it keeps an old content cached.

In order to refresh this cache you have to setup an 'EpiServer HTTP Connection', using an EpiServer user account which has permissions to install plugins.

After system finishes target content import it logs in using account specified in 'EpiServer HTTP Connection' and resets cache.

Only with this feature you will be able to see content changes right after import operation.

Parameters:

  • Server(Required) - web URL of a website (for example company.com);
  • Port(Optional) - website port (for example: if Port = 80, requests will be sent to http://company.com:80);
  • User Id(Required) -  EpiServer account name;
  • Password(Required) - EpiServer account password.

All other parameters will be ignored for an 'EpiServer HTTP Connection'.

  • No labels