Production Scheduler installation procedure
The Production scheduler includes:
- An application server
To make the distinction with the Sage X3 web server (Syracuse), we refer to it as the Scheduler server.
Hardware-wise, this server is the machine where the Production Scheduler is actually installed and running, and where the planning data is located and processed.
Software-wise, the planning server is a Windows service.
- A Web server
This server hosts the Production Scheduler application front-end. This Web application is deployed on a IIS Web site, if necessary with HTTPS.
When users connect to their planning application, they access it through the IIS Web site on this server.
Note that the planning server and its Web server must be on the same machine.
Prerequisites
Before launching the Production Scheduler installation, make sure that all the requirements that are mentioned in the prerequisites section are met. This is especially the case for the Windows Management Framework which is mandatory in order to be able to execute the setup.
- Authentication between the Sage X3 web server and the Scheduler server.
Choose one of the two options :
- Basic authentication. A Sage X3 web server user will be used for the connection. For this purpose, it is recommended to define a dedicated user consuming the ERPTRAN badge (defined in the Role). This Sage X3 web server user must be able to connect to the X3 endpoint containing the datas to be linked with the Production Scheduler.
- Client certificate authentication.
In this case, you will have first to enable the Client certificate authentication mode
- Connection to the IIS web server
If you want to have a https connection on the IIS server (recommended), you will have to generate first the SSL certificate or obtain it from a trusted certificate authority in order to place it in the personal store of the IIS server.
Launching the Production Scheduler installation
The DVD-ROM includes a folder named SafeX3ProductionScheduler containing the setup program.
To launch the installation, execute the '.jar' file located in the SafeX3ProductionScheduler directory.
First steps
Select the language for the installation procedure and the installation path.
Sage X3 parameters
- X3 web server name :
Name of the machine where the Web "Syracuse" server is installed.
- X3 web server port number :
The number of the communication port uses by the Web "Syracuse" server
- For a basic authentication, it's the port used for the connection to the Web "Syracuse" server (often 8124)
- For a Client certificate authentication
It's the port defined in the Host entity during the steps for enabling the
Client certificate authentication mode
- X3 endpoint : name of the endpoint containing the datas to be linked with the Production Scheduler
PlannerOne configuration
- Tenant identifier : It's set by default with the X3 endpoint. You can set another custom name instead.
- Port numbers :
- The port numbers you can use.
The default ports are:
- 9010 for the Web site in IIS.
- 9011 for the port used by the planning server to expose its Web services.
- 9012 for communications between the planning server and its Web server.
- Web App Name :
Name of the planning Web application deployed with the current tenant, i.e. the name this Web application will have in IIS: By default, the name is based on the name of the tenant you are creating (PlannerOne+TenantName). You can set another custom name instead.
Settings for Sage X3 application server access
Select the authentication method you want to put in place.
- Basic authentication
Sage X3 web server user : Credentials which will be used for the connection to the Sage X3 web server
- Certificate mode
- Client pfx certificate full path
- Client pfx certificate password
- X3 server CA full path
- Issued by one of the official trusted certificate authority (Y or N ) ?
Those settings have been defined during the steps for enabling the Client certificate authentication mode.
SSL Support
If you want to use the HTTPS mode for the IIS Web site (recommended), you will have to place the certificate in the personnal store of the local machine and to set :
- Server pfx certificate friendly name
- Port number
Default value 443
Finalizing the connection between the Sage X3 web server and the Scheduler server
The goal is to link the endpoint with the Web APP on the IIS server.
A connected application has to be defined for the Web APP. The connected application to be used for the folder is defined in the paramter values.
From a Sage X3 web server connection (as an administrator):
Connected Application
Go to All > Administration > Administration > Connected Application and create a new Connected application for the Scheduler server.
- URL
The URL is composed with the name of the server where the Production Scheduler is installed, the port of the Web site in IIS (often 9010) and the name of the Web App Name defined the Production Scheduler install setup:
http(s)://server_name:IIS_website_port/Web_App_Name
- Client ID
It defines the UUID of the connected application. It is a read only property which will be initialized when saving a new instance. This UUID will be used in the next step (in Edit mode, you will be able to copy the content of this field).
Parameter values (ADPVAL function)
Go to All > Setup > General parameters > Parameter values and set the parameter PSCLIENTID of the chapter EXAPP (for the X3 folder) with the UUID defined in the previous step (paste the content of the field previously copied).
Implement Planner One
To implement Planner One, and at least to initialize the X3 folder Sites, please refer to the How to Guide Implement Production Scheduler in the online help center.