Basic introduction into establishing a connection with a data source can be found here:To find our more about establishing connection to data source, please check How to connect to Content Data-source?
EpiServer MS SQL Connection
This connection is a primary one and is used connection to export/import content. iLangL Cloud uses Cloud is using 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 -The process requires connection between Ms SQL server, where EpiServer database is hosted, and iLangl Cloud server.
To find our more about connection to SQL server over the Internet, please read a dedicated article: Connecting to SQL Server over the Internet
And watch a video:
| Widget Connector | ||||
|---|---|---|---|---|
|
Parameters:
- Server(Required) - a name or a network address of an SQL Server instance you are connecting to;
- Port(Optional) - a server port , that 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 the SQL Server account;
- Database(Required) - a database name;
- Table prefix(Optional) - a the database table prefix for your CMS installation (usually empty for EpiServer);
| Note | ||
|---|---|---|
| ||
In case of using Integrated security on customer's side, it is possible to establish connection without password can be established using via Local connection |
| Info |
|---|
Here is how a what the final connection string generated to a Generic Content Provider might will 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 therefore, keeps an old content cached.
In order to refresh this cache, you have to setup an set up 'EpiServer HTTP Connection' , using an EpiServer user account which that has permissions to install plugins.
After Once system finishes target content import, it logs in using with the account specified in 'EpiServer HTTP Connection' and resets cache.
Only with this feature you will be able to see This will ensure that content changes are visible 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.
...