Installing Production Scheduler

Production Scheduler consists in:

• An application server we refer to as the Scheduler server to make the distinction with the Sage X3 web server (Syracuse). It is a Windows service.
  Production Scheduler is installed and runs on this server. This is also where the planning data is located and processed.
• A Web server which hosts the Production Scheduler application front-end. This application is deployed on an IIS Web site, with HTTPS, if necessary. Users connect to their planning application through the IIS Web site on this server.

Note that the application server and the Web server must be on the same machine.

Prerequisites

• Before attempting to install Production Scheduler, make sure the configuration requirements are met. This is especially important for the Windows Management Framework which is mandatory to execute the setup.
• Choose the authentication method between the Sage X3 web server and the Scheduler server:
  • Basic authentication: A Sage X3 web server user will be used for the connection. It is therefore recommended to define a dedicated user for the ERPTRAN badge in Administration > Users > Roles. The user must also be able to connect to the X3 endpoint that contains the data to link to the Production Scheduler.
  • Client certificate authentication: You first have to enable the client certificate authentication mode
• If you want to have a HTTPS connection on the IIS server (recommended), you first have to generate the SSL certificate or obtain it from a trusted certificate authority. You then have to place it in the IIS server personal store.
  Refer to Certificate Installation for more information on certificate management.

Launching the Production Scheduler installation

To launch the installation, execute the .jar file located in the ProductionScheduler directory of the DVD-ROM.

Select the language for the installation procedure and the installation path.

You then have to enter the following information.

Sage X3 parameters

• X3 web server name: Name of the machine on which the Syracuse server is installed.
• X3 web server port number: Number of the communication port used by the Syracuse server:
  • For Basic authentication: Port used for the connection to the "Syracuse" server (usually 8124)
  • For Client certificate authentication: Port defined in the Host entity when enabling the Client certificate authentication mode
• X3 endpoint: Name of the endpoint containing the data to link to the Production Scheduler

PlannerOne configuration

• Tenant identifier: X3 endpoint by default but you can set another custom name.
• Port numbers: Default ports are:
  • 9010 for the Web site in IIS.
  • 9011 for the port used by the Scheduler application server to expose its Web services.
  • 9012 for communications between the Scheduler application server and its Web server.
• Web App Name: Name of the Scheduler Web application deployed with the current tenant (the name the 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.

Settings for Sage X3 application server access

Select the authentication method you want:

• For Basic authentication:
  Sage X3 web server user: Credentials which will be used for the connection to the Sage X3 web server
• For Client certificate authentication:
  • 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)?
  These settings were defined when enabling the Client certificate authentication mode.

SSL Support

If you want to use the HTTPS mode for the IIS Web site (recommended), place the certificate in the personnal store of the local machine and set:

• Server pfx certificate friendly name
• Port number: Default value is 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. To do so, a connected application has to be defined for the Web APP in the parameter values.

Perform the following steps from a Sage X3 web server connection, as an administrator:

Connected Application

1. Go to Administration > Settings > Authentication > Connected applications.
2. Click Create connected application.
3. Fill in the information.
   • URL: The URL is composed of the name of the server where the Production Scheduler is installed, the port of the Web site in IIS (usually 9010), and the name of the Web App Name defined during the Production Scheduler installation: 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 is initialized when saving a new instance.
     Copy this UUID while in Edit mode.
4. Click Save.

Parameter values (ADPVAL function)

1. Go to Setup > General parameters > Parameter values.
2. Set parameter PSCLIENTID of chapter EXAPP (for the X3 folder) with the UUID defined in the previous step.

Implement Planner One

To implement Planner One, and at least initialize the X3 folder Sites, refer to the Implement Production Scheduler How to Guide in the online help center.