This application is used to define various system options that are stored in the Windows Registry on the server. In order for the settings to take affect after modification they require restart of the related Windows Services.
- Connection Type: This field is used to specify the type of connection that APS will use to connect to the Database.
- Database: The name of the database that APS will import data from and the server name that the database is located on are defined here
- Database Login Credentials: The username and password that ASP will use to communicate with the database.
- ERP System Login Credentials for custom Export: In order for APS to be able to communicate with the ERP system, enter the ERP username and password here.
- Connection String: This defines the connection string that is used to connect to the database.
- SQL to run before ERP data: If specified, this query is executed when a Connection is opened for importing. This can be used to configure various database specific Connection settings. Leave blank to disable.
Main Services Computer Name or IP Address: This specifies the Computer Name or IP Address on which the System Service will be running. This is used by the Extra Services Service and Scheduling Agent Service when attempting to contact the System Service.
Interface Service Computer Name or IP Address: This specifies the Computer Name or IP Address on which the Interface Service will be running. This is usually the same computer on which the System Service is running but it is also possible to install the Interface Service on another computer (such as the computer hosting the target database). This is used by the System Service and Scheduling Agent Service when attempting to contact the Interface Service.
Port to run Windows Services on: Each Service “listens” to the specified Port for incoming communications. Each Port on your computer can only have one active Service using it so each Port below must be unique and must not already be in use. If a Port is in use when you try to start the Service it will fail to start and indicate the Port as the reason in its log file.
- System Port: Port for the main System Service. The Client config files must specify this Port so that they can communicate with the System Service.
- Interface Port: Port for the Interface Service.
- Scheduling Agent Port: The Port for the Scheduling Agent Service.
- Client Updater Port: The Port for the Client Updater Service. The ClientUpdater.exe.config file must specify this same Port so that the Client Updaters can communicate with the Client Updater Service.
- Extra Services Port: The Port for the Extra Services Service. The config files for the Shop Views clients must specify this same Port so that they can communicate with Extra Services.
Client Updater Service Version: Indicates the format version of the Client Updater UpdateFiles.config file.
Extra Services Contact Interval: The number of milliseconds between requests from Extra Services to get information from the System Service. The larger this value the longer the delay between when a change will occur in the System and when the Extra Services Service (and therefore Shop Views) will have access to that information. The smaller this value the more activity that will occur on computer as Extra Services contacts the System Service for updates. The recommended value is 1000 milliseconds (1 second).
System Service Priority: This sets the Priority for the System Service. This can be set to higher values to reduce the chance of other programs interfering with APS.net clients due to the System Service delaying its response to client requests because the computer processor busy with some other process. Valid values are: The default value is AboveNormal.
Working Data Folder where system data is stored: Specifies where all data created by all of the APS.net services will reside. This folder and the System Service subfolder in particular should be backed up frequently to prevent possible data loss. This folder must be writable by the APS.net Services.
Backup Diagnostic Recordings: Recordings are stored user and interface actions. They can be used for restoring from fatal errors, repeating errors for support of problem resolution, and new version testing. Recordings are stored in the “Recordings” directory. Each recording is stored in its own sub-folder named after the time when APS.net started.
- Record System: Set this value to true to record actions performed on the system. The recording can be used by APS support personnel to help identify problems you experience on your system and to recover from fatal errors. It is highly recommended that this be enabled.
- Max Number of System Sessions to Record: The maximum number of recordings folders that the system will make. The minimum and default values for this setting is 10. The larger this number the further back in time it is possible to go to retrieve old data and the more storage space is occupied on the computer.
- Max Number of System Backups to save per Session: The maximum number of “.dat” files that will be stored in a recording as “.dat” files are deleted so are preceding transmissions. The larger this number the further back in the current System Service sessions it is possible to go to retrieve old data and the more storage space is occupied on the computer. The minimum value for this setting is 10 and the default is 15.
- Minutes Between System Backups: Specifies how often backups are made (in minutes); how frequently “.dat” files are created within the current recording. “.dat” files are created at each backup interval in which a transmission occurred after the last backup. The larger this number the easier it will be to resolve any problems that occur in the system and the more storage space consumed on the computer. The minimum value for this setting is 1. The recommended value is 15.
Interface Service Login: These settings are used during the installation of the Interface Service to specify how it should login. By setting these values here instead of in the service itself (in Control Panel), the settings will be retained between upgrades.
- Logon as System Account: This is the default value and does not require any user name or password to be specified. The service will long as the computer’s Local System Account. This is sometimes in adequate however because the System Account may not have adequate access for importing from a source ERP database. In this case the User Account option can be used.
- Logon as User Account: This can be used to logon the service under a specific user’s account. This is often necessary when the source database requires logon credentials.
The Database stores time span in: You can define the unit of time used by the database here for accurate communication between APS and the database.
Import connection initialization SQL: If specified, this query is executed when a Connection is opened for importing. This can be used to configure various database specific Connection settings. Leave blank to disable.
Publish schedule Tab
Published Scheduled SQL server database: This controls how data is exported when the Export To SQL Server command is run.
- Connection String: Defines the Connection String to use for connecting to the SQL Server to be used for exporting a Scenario.
A sample Connection String is: “Data Source=(local);Integrated security=SSPI;Initial Catalog=APS.net”;
- Attach APS SQL Server Database: This button will attach the APS SQL Server Database to the database specified in the connection string above.
- Detach APS SQL Server Database: This button will detach the APS SQL server Database from the database specified in the connection string above.
Automatic Actions Tab
Settings below are used to trigger periodic actions in APS.net.
Run Automatically Every __ Seconds: The amount of time (in seconds) between broadcast of Transmissions to trigger Scheduler actions. These broadcasts will first occur when the SchedulingAgent service is started and then at the specified frequency. Warning: If this is too small a value then the system can become continuously busy and unusable for the users. Typically this value should be at least ten minutes (600 seconds).
Run Automatically at these times of the day: A comma-separated list of times of day to run the Tasks. For example: “8:00,9:30,14:00,22:00”. Leave blank to disable running by time of day.
Actions to Run: The options below determine which Tasks are run by the Scheduling Agent each time. They are run in the order listed below.
- Import: This specifies whether the Perform Import action should be included. This should only be set to true if the APS.net Interface Service is running and configured properly.
- Clock Advance: This specifies whether to advance the APS.net Clock to the current system time.
- Optimize: This specifies whether to perform an Optimization (using the Shared Optimization Settings).
- Export to SQL Server: This specifies whether the schedule will be exported to the SQL Server database.
- Export to XML: This specifies whether the schedule will be exported to the an XML file.
- Export to Custom Data Source: This specifies whether the schedule will be exported to a data source for which a Custom Interface has been defined.
Enable Scheduling Agent Diagnostics: If checked then various diagnostic files will be written to aid in troubleshooting.
Message File Processing Tab
Settings below are used for automated processing of message (text) files.
To use this functionality, a DLL named MessageProcessor.dll must be created and placed in the ProgramFiles folder. This dll implements an interface called IMessageProcessor and is used to interpret and respond to the particular Message File format in use.
Enable Message File Processing: This specifies whether to read and process the files in the messageDirectory.
Folder to monitor for Message Files: The folder containing files to be read and processed.
Log Message Files after processing them: Whether or not to log all messages in the processed files folder beneath the Message Files folder.
Delete log files older than  days: If logging messages, this indicates how long the log files should be kept. They are deleted once they are more than this number of days old.
Process files that match this filter: Indicates which files are processed (in order of increasing create date). Example: *.txt
Client contact intervals
- Master Scheduler: This defines how long (in milliseconds) should the server wait before timing out the master scheduler connection if it doesn’t hear from the master scheduler client.
- What-if: This defines how long should the server wait before timing out the what-if connection if it doesn’t hear from the what-if client.
- View Only: This defines how long should the server wait before timing out the View only connection if it doesn’t hear from the View only client.
Allow Password saving: Check this box to allow client machines to save login password.
Shop Views Tab
Folder to store temporary data on Shop Views client PCs: Defines the working directory on the Shop View clients where the system will store its temporary files. This folder must be a valid folder on all Shop View client PCs.
Extra Services Tab
Extra Services Login: These settings are used during the installation of the Extra Services service to specify how it should login. By setting these values here instead of in the service itself (in Control Panel), the settings will be retained between upgrades.
- Logon as System Account: This is the default value and does not require any user name or password to be specified. The service will long as the computer’s Local System Account. This is sometimes in adequate however because the System Account may not have adequate access for exporting to the target ERP database. In this case the User Account option can be used.
- Logon as User Account: This can be used to logon the service under a specific user’s account. This is often necessary when the target export database requires logon credentials.
Playback of Recordings:
- System Start Type: Specifies how the System Service should start and what data should be loaded. The possible values are:
Normal: This is the setting used in a live production environment. It causes the System Service to load the Scenarios.dat file in the Scenario directory. If it doesn’t exist a new empty system is created.
Empty System: Create a fresh system every time the system starts. This is only useful for testing purposes.
Absorb Customizations Folder: When running with this setting the files in the customizations folder are absorbed into the Scenarios.Dat file on the server. The customizations are used immediately, so you can also test your customizations while running in this mode. To use this setting first arrange the customizations folder the way you want. Drop in DLLs, data files etc. The customizations folder is a subdirectory of the working directory. Subdirectories of the customizations folder aren’t supported. Set this settings value to AbsorbCustomizationsFolder. Start APS.net. Stop APS.net and change the value of this setting back to “Normal”. When APS.net is restarted the files that were absorbed into the customizations folder will be used.
From Recording: Load the specified recording and playback the transmissions. This mode is useful for testing Recordings that contain the replication path of a problem.
From Recording (wait for Client start): Load the specified recording and playback the transmissions. This mode is useful for testing Recordings that contain the replication path of a problem. Replay of transmissions is delayed until a special message is received. The data generator has the ability to send this message.
Unit Test: This is used to test a set of Recordings against a base case to look for discrepancies using a new software version.
Unit Test Base Case: This is used to construct a test case to be tested against later.
- Folder from which Recordings should be loaded: When the Start Type is set to “From Recording”, at startup APS will load the recording specified in this folder. The time it takes to startup will depend on the quantity and types of transmissions that need to be replayed. Once playback has completed everything will proceed as normal and APS.net will operate out of the normal working directory. The contents of the specified recording directory will not be modified.
- Starting Scenario Number: When a recording is played back you may specify which recording to start the playback at. If the recording you specify doesn’t exist, then the first recording found will be used. The smallest usable value you may enter is 0.Example:If the following .dat files are in your recording and you wanted to use the middle one, you would
enter “99” for this setting.
- Non-sequenced Transmission Playback: Whether to make transmissions that are being replayed non-sequenced. If this field isn’t set then the value of the sequenced field in the transmissions is left alone.
Single-Threaded Transmission Processing: When running in debug mode this prevents transmissions from being dispatched on separate threads. This is useful to prevent the code in the debugger from jumping around. Multiple threads aren’t handled well by the debugger. It appears to switch between the threads as you step through code. This leads to symptoms such as needing to click on a line more than once to step
over it and the code jumping to strange locations and returning as you try to step over lines.
Show demo / Testing features: This is to enable features used for demonstration purposes only. If checked, an option in “Advance Clock Dialog” is shown called “Adjust demo data” (See below). The Adjust demo data checkbox adjusts the Job Need dates when a clock advance is performed so that the demo data is up to date.