Web Server
IIS must be installed, and ASP .NET version 4.6 configured. Create an ASP.NET web application at the root directory of the Jef website.
Happen Business recommends that the web server be separated from all back end services by firewall at least. It is highly recommended that a demilitarised zone (DMZ) be used or, if this is not practical, have the website hosted by a third party provider (internet service provider).
To install Jef FTP or direct file access to the website's root directory is required.
SQL Server
Jef requires Microsoft SQL Server. This can be installed on the same machine as the web server or on another server, depending on the infrastructure availability. If the website is to be hosted by a third party provider, the SQL Server will usually be installed on a separate machine. If a licence for Microsoft SQL Server is not readily available, then install Microsoft SQL Express (2012 R2 or higher) on the web server.
Create a database for JEF. The Jef installation will set up the database as required.
|
It is not recommended to install Jef on the same machine as Jim2 Server, mainly for security reasons. The web server should be in a demilitarised zone, and should not be a member of the company domain. However, to have Jef on the same machine as Jim2 Server, do not name the Jef database beginning Jim2_. It is recommended that all Jim2 eBusiness Framework databases be prefixed with JEF_, for example JEF_Happen. |
Jes to Jef Connectivity
For online functionality such as eBusiness Server, Jef needs to communicate with Jes via a TCP/IP connection.
The network must be configured in such a way to allow Jef on the web server to establish a TCP/IP connection with Jes.
Jes is usually set up to accept a connection on port 5740 but this is configuration (see the TCP module for more information).
Jes needs HTTP access to Jef in order to publish web logon details etc. to the website.
Further information