This document describes how to set up your Demand Plan Server, Client and/or Applets, and how to prepare your system to support a successful installation.
Note: When installing the Demand Plan Server and running it for the first time it can be easier to run it as an application the first time. When everything is configured and ready, you can set it to run as a service if you want, or it can continue to run as a application.
Note: When using remote access software such as Microsoft's Remote Desktop Client or Terminal Server Client to remotely access the desktop of the Demand Plan server PC multiple sessions will be started on the target PC. This may result in multiple running instances of the Demand Plan server, a condition that will render the Demand Plan server inoperative. If the server hosting Demand Planning is running the Windows 2003 Server or newer operating system, it is possible to use the "/console" option of Microsoft's Remote Desktop Client to avoid this situation. Other remote access programs such as VNC that display an image of the server console are also acceptable.
Certain systems and configurations must exist on your system prior to installation of IFS Demand Planning. Demand Planning Setup does not install or configure an IFS Applications database.
1. The database that Demand Planning will run against must already be set up and your site with data (transaction and inventory parts) must exist in the database.
2. Install Oracle Client software if this is not already installed. Configure a SQL*Net connection to the database you want to connect your Demand Planning Server. This must be done only on the computer where the Demand Plan Server is to be installed. On the APP9 version of DEMAND, OCI/Oracle Client 12 is used; the 64 bit version is needed.
3. You can run the Demand Plan Server with the Appowner user, or you can use the DEMANDSERVER user, it you use this make sure that its granted access to all tables and views needed. There exists scripts to do this that is included in DEMAND (POST_Demand_DemandServerUser.sql)
4.
There exists
installation files for both the Demand Plan Client (SetupForecastClient.msi/setup.exe)
and Demand Plan Server (SetupForecastServer64bit.msi/setuo.exe)
Note: English language translation procedures have changed in Apps 7.5. If upgrading from a previous release, manually delete all *en.xml translation files.
You can run a demo version of IFS Demand Planning without any IFS Application
database. This feature is very useful when your only purpose is to run a demo of
IFS Demand Planning. If you are installing only a demo version of demand
planning you do not need to follow steps 1, 2, and 3. If you do not have
SQL*Net installed on your computer and only want the demo version of demand
planning, you must run a batch file that is located in your demand plan server
target directory. Additional information is in the section “To
make a stand-alone demo” at the end of this document.
Demand Planning Server executable is installed directly via the setup.exe
installer, note that the applet files is also installed when installing the
Demand Plan Server so there’s no extra installation for the applet.ad
Launch the installer, setup.exe. After the system information screen, select Server Environment to install Demand Plan Server.
Note: From IFS APP 9 the Demand Plan Server will only be available in 64 bit version.
Note: With the default target directory setting, the server files will be installed to C:\Program Files\IFS Applications\Demand Server.
If the Demand Server is going to be
run without the use of the DB appowner, it will require an Oracle user with the
appropriate permissions granted to be able to access the database. Only one
DEMAND user per database is required. During the installation of IFS
Applications, a user for the DEMAND Server (DEMANDSERVER) containing the all of
the required permissions is created. Upon creation, this user is set to
"locked” with the password expired.
Before installing the DEMAND Server, using SQL*Plus or IFS Admin tool / SQL File
Executer log in to the database and unlock the user by running the
UpdateDemandUser.sql script.
You will be prompted for an appropriate password for the user.
The applet is now installed under the Demand Plan Server installation path \Web\Applet\ This happens when you install the Demand Plan Server. Everything should work without any need of changes to registry or anything. The only thing needed is to setup the outgoing mail tab on the Demand Plan Server, to able to send mails.
The applet and dictionary file(s) will be copied to the destination folder. The following default English language files are copied automatically by the installer:
| DemandAppletSTD.xml | Standard (default English) language file |
| DemandAppletUS.xml | United States (default English) language file |
| DemandAppletHelpSTD.xml | Standard (default English) applet help file |
The Applet, by default, will display in English. To support other languages, a translation file (DemandAppletXX.xml) and optional help file (DemandAppletHelpXX.xml) in the desired language are required. The suffix ‘XX’ denotes the Trolley Sending Language Code, which is not necessarily the same as the ISO language code used for client and server translation.
| Language | IFS Client/Server Language Code | Trolley Sending Language Code |
|---|---|---|
| Chinese | zh | CN |
| Danish | da | DK |
| Dutch | nl | NL |
| English (US) | en | US |
| Finnish | fi | FI |
| French (Canadian) | fr | FR |
| German | de | DE |
| Japanese | ja | JP |
| Norwegian | no | NO |
| Spanish | es | ES |
| Swedish | sv | SE |
A complete list of Trolley Sending Language Codes can be found by opening the Send Trolley dialog box in the Demand Plan Client.
Note: With the default target directory setting, the client files will be installed to C:\Program Files (x86)\IFS Applications\Demand Client.
When the server is started it automatically tries to find the latest version of data, it can be in Oracle or on a backup file. First it finds the latest backup file then it compares the date found on this file with the last time for a write-back to Oracle. The server selects the newest data and loads that data and starts the server. Searching for the latest backup file is done in the following way. The filename of latest backup file is written to registry. If this file exists it is selected, if not it searches the backup path and selects the newest file. The backup path is found in the Demand Planner\Demand Plan Server Setup in the scheduling tab, this is in IFS Applications Windows Client.
By adding command line parameters it is possible to force the server to start from Oracle or file or manually. Here are the commands.
| Command | Description |
|---|---|
| /r | Start the Server using the last restore file. |
| /r:filename | Start the Server using a specific restore file. |
| /o | Start Server using data found in Oracle. |
| /o:username/password@service | Start Server from oracle using username, password and service. |
| /m | Start the Server manually. Do not load from oracle or file. |
The Demand Plan Server can be started as an NT-Service as well as being started as a traditional program.
Using an NT-Service allows the server to be started automatically and restarted if it fails. The biggest problem with NT-Service is that network resources like disks are not available or accessible, when the service is started. Therefore SQL*Net has to be installed locally. All files needed by SQL*Net must exist on the local drive including TNSNAMES.ORA. Failure to locate any of the files locally results in the "ORA-1010" error message when the server is started.
WARNING: The server only keeps data in memory, if the power fails or the service is stopped accidentally, all changes done since last write back or backup will be lost. This makes it very difficult to do any manual actions against with the Demand Plan Server. Hence the usability / user options will be reduced.
One alternative to using an NT-Service is to start the server automatically by putting it in the startup folder found in the Windows start menu. Since the program is not started before the network disks are in place this eliminates the need for SQL*Net to be installed locally. The drawback is the server is not restarted automatically if it fails.
Note: If this menu shortcut is not available, just launch the Forecast Server from the Start -> Run menu or the command line with the /m parameter: (Drive:\path\ForecastServer.exe /m)
General Tab
Enable: Specify which parts of the server you want to activate.
Note: Do not change this without having installed the same database component. This parameter is set during installation and should not be changed after that.
Approve: When checked in a forecast part is automatically approved for
IPR calculations when you move to the next or close the DP client. For users
that do not have IPR leave this checked.
Client/Server Communication: Specify the port number used for Demand Plan
client and server communication. If this is changed be sure to use the same port
on the Client setup.
Note: Port 5000 is reserved on Windows XP for Microsoft Messenger. When running Demand Plan on XP, either choose a different port number or disable Microsoft Messenger.
Windows Service: Specify if you want the Demand Plan Server to run as an
application (recommended to begin with), a manual service (you need to log on to
the host machine before it start up) or if you want it to run as a normal
windows service.
Log Directory: Specify the location of the server’s log files.
Language File: Specify the translation file for the language the server GUI will show when the server is started.
Help File URL: Specify the address for the server help start page called SfrmServerGUI.htm, here you must write the address of that page. This is only necessary if you want help to be available when you push F1 in the Demand Plan Server GUI.
Web Server Name / Applet Path: Specify the URL where the applet files are installed. This is only important if you are going to use the Trolley / Collaborate forecasting functionality. The Demand Plan / IPR Server has now a internal web server installed the web files in installed in the installation path of the Server under /Web/Applet/
Note: If you run the Demand Plan Server with the appowner user, you can leave this filed empty.
Now it is time to load the server with some data. The easiest way of doing this is to load the test data set, which is distributed along with the installation. This data set can be useful for demo purposes and for testing that the server and client are setup correctly before you start to set up a demand plan server in IFS Applications (IFS Windows Client)
Now it is time to load the test data into the server, selecting File-Restore form the Server menu does this. Select the 4000ModelTest.bac file from the Open dialog and push the Open button.
Note: You will not be able to load data into the server when the test data is loaded
The Demand Plan Server can make forecasts for groups of parts. The predefined group fields are:
In addition to the predefined groups can be added by inserting records into
GROUP_FIELD_LIST_TAB. Group field list has the following fields:
| Field | Null | Type | Description |
|---|---|---|---|
| GROUP_ID | NOT NULL | VARCHAR2(3) | The group ID. Start with 100 to be sure not to crash with the new standard sets. |
| GROUP_NAME | NOT NULL | VARCHAR2(200) | Description of this group. |
| FIELD_NAME | NOT NULL | VARCHAR2(30) | The name of the field this group is take from. |
| FIELD_DESCRIPTION | NULL | VARCHAR2(200) | The name of the description of the group. |
| TABLE_NAME | NOT NULL | VARCHAR2(30) | The name of the table, this table must contain the fields CONTRACT, PART_NO and <field_name> |
| ROWVERSION | NOT NULL | DATE | Standard rowversion |
To clarify this, lets take an example: For some reason we want to group parts
by the unit code. We can use any GROUP_ID we want but to be sure we
do not crash with new standard ones we use 100. GROUP_NAME is the
name group it is displayed to the user. The unit code for each part is stored in
the table INVENTORY_PART_PUB. It is stored in the field
UNIT_MEAS. Description can be found by using the function
ISO_UNIT_API.Get_Description(UNIT_MEAS,NULL).
Unit measurement can be added by executing the statement:
INSERT INTO GROUP_FIELD_LIST_TAB( GROUP_ID, GROUP_NAME, FIELD_NAME, FIELD_DESCRIPTION, TABLE_NAME, ROWVERSION) VALUES ('100', 'Unit Measurement', 'UNIT_MEAS', 'ISO_UNIT_API.Get_Description (UNIT_MEAS,NULL) ', 'INVENTORY_PART_PUB', SYSDATE);
Start the Client for the first time, then this dialog appears
The Demand Plan Server Name is the machine name where the demand plan server is running.
Port Number: Specify the port number on which the server is listening. It must be the same port number specified in the setup for the Demand Planning Server.
Note: Port 5000 is reserved on Windows XP for Microsoft Messenger. When running Demand Plan on XP, either choose a different port number or disable Microsoft Messenger.
Log Directory: Specify the directory location for the log file.
Language File: Specify the language file to be used by the Forecast Client.
Helpfile (URL): Specify the web location for the client start help file. The start help file is called CfrmDemandPlanClient.htm. If help functionality on the client is not important then skip it. e.g. C:\Documentation\DemandClient\CfrmDemandPlanClient.htm
Send to: These parameters specify which attachment types will be included in the File/Send to functionality. Selecting Send Excel File and or Send HTML will result in an Excel file and or HTML version of the tables. If Send Bitmap is selected it will generate a bitmap image of the graphs. If Include Detail View is selected then the detail view will also be included in the mail.
Now you should be able to log on and look at the parts and their forecasts.
Demand Plan Main Client users need to have grants for
FORECAST_SERVER_SETUP view as a minimum requirement. For normal enterprise
explorer users, the set up and configuration is as usual.
To achieve the maximum amount of security it is recommended to put the server running Demand Plan Server and Applet Web Server in the DMZ (Demilitarized Zone). Then only 2 ports have to be opened into the DMZ, one for the applet download from the web server to the collaboration partner PC, default port number 80. The other port is for the communication between the applet and the Demand plan server, default port number 5000/5010. There also have to be opened 2 ports from the DMZ into the LAN. One port is for the communication between the Demand plan server and the Demand plan client, default port number 5000/5010. This port must be the same as the Applet port number. The other port from the DMZ and into the LAN is the port used to connect to the Oracle database.
Both the Demand Plan Client and the Demand Plan Server have different registry settings that can be set. Normally there should not be any need for changing these values, but in some installations there may be a need for such changes. For example, when the customer is using another period version than monthly then some best fit search parameters and season profile detection variables may be considered changed. For more information on how to change these parameters see the file SfrmRegistrySettings.htm.
When users
don't have read or write access to the HKEY_LOCAL_MACHINE
part of the registry then it is possible to set the Demand Plan Client to only
write to the HKEY_CURRENT_USER
portion of registry, avoiding this obstacle.
For details about these registry settings see the SfrmRegistrySettings.htm and the CfrmRegistrySettings.htm files in the demand documentation path, for the Demand Plan Server or the Demand Plan Client.
To make a stand-alone demo on a PC that does not have SQL*Net locally and is supposed to run the demo without access to the network, you must run the batch file MakeDemo.cmd. To remove this standalone demo you must run the remove file RemoveDemo.cmd. These files are located in the directory where you installed the demand plan server.