...
- First open the c:\inetpub\wwwroot\FiMServer\web.config XML file in notepad or text editor of your choice. If you renamed the folder or placed the application in a different web root, substitute that here.
Look for a section called <connectionStrings>. There will already be a connection string stub there called "formsserver" with a placeholder value of !!CONNECTIONSTRING!! . Update the connectionString here to match the one in your environment. Refer to http://www.connectionstrings.com/sql-server/ for guidance on correct connection string for your environment or check with your database administrator.
As a basic sample, I typically use the following to connect on our servers:Code Block language xml title Sample connection string Data Source=sqlservernamehere;Initial Catalog=databasenamehere;User Id=useridhere;Password=passwordhere;Info title connectionStrings in server web.config The application will always look for a connectionString node called "formsserver". Do not rename "name" attribute on this connection string or the application will not see your connection string value.
Also, it is possible to use this web.config file for configuring other connections for use with the Query API. It is not necessary to configure those at this time. For more information on using the Query API with your custom forms, check out the Creating Custom HTML Forms article.
- Save your Web.config file changes.
- Now open your browser to the location of the webservice you created above. In my example, this is http://<YOUR SERVER>/FIMServer/FormsServiceJSON.asmx
- Click on getEnvironmentVaribles and then click Invoke on the next window. This will run the getEnvironmentVariables function and display the results.
- At this point you should see something like this
{"ResponseTime":"1/15/2015 1:51:44 PM","Authentication":"Application"}This indicates that the server is responding to requests and is able to lookup the client version locations in the database, but it can't verify the license.
...