To deploy Jef to the web server file or FTP access to the root folder of the ASP.NET web application on the web server is required.
If the web server is local, copy the web application file to the web server via the network file system.
If the website is hosted by a third party, generally they will generally supply an FTP path and FTP logon details to use for copying files to the website. Enter these details into Jef Setup so it can copy the web application files to the web server.
|
The directory is the location where the website files are installed. Examples include /happen.biz/web or /httpdocs. |
Database Connection String
Enter the DB connection string for the web server database to be used by JEF. Clicking the ellipsis [...] allows entry of the parameters in a user friendly manner.
The details required for the connection string will either be supplied by the internet service provider if website is hosted, or the details should be known from setting up the SQL database in preparation for deploying JEF.
|
If a server instance name has been provided, enter this when asked. If this has not been provided, please leave blank. |
Jes Connectivity
Jef needs connectivity with Jes for certain tasks, such as retrieving a user's list of jobs. Jef connects to Jes using TCP/IP, so specify the address (either DNS Name or IP address).
|
This is the IP or DNS of the internal network. A port must be forwarded from the firewall to the machine with Jes (the default port is 5740). |
Website URL
This is the URL to the root of the Jef web application, ie. the web address of the website being deployed. This URL is used by Jef Setup to verify the deployment was successful at the end of the setup process.
For example:
▪If Jef is to be deployed to the root of the website as the main application, the URL would be like: http://yourcompany.com
▪If Jef is to be deployed to a subdirectory of the website as a secondary application the URL would be like: http://yourcompany.com/subdirectory