These prompts are used to manage INFOR OS settings.
General tab
1. Tenant ID
Specify the Tenant ID that identifies this system to Infor OS. The tenant is a container for accounting entities and locations and is required in each BOD. The value of the tenant must be the same in all of the applications that exchange BODs. Data is not shared or accessible between tenants.
2. OAGIS Release
Specify the base AOGIS release number.
3. Infor BOD Version
Specify the BOD version number for Infor.
4. Connection Method
Select a connection method for Infor OS: 0 - N/A, 1 - Inbox/Outbox, 2 - REST/API. Specify the N/A to prevent any communication with Infor OS. When modifying the connection method from Inbox/Outbox, a warning is displayed if there are any unprocessed records remaining in any database set up for use with Infor OS. Documents may be orphaned.
5. Retry Interval
Specify the number of minutes to wait before retrying when the connection to Infor OS fails.
FACTS Outbound Locker
Use these fields to specify FACTS outbound locker information, such as the text directory, the required file name preset order, and when/whether text files in that directory are removed or renamed under conditions specified by the I5/BKC205 background process. The File Name Preset is always ended by an “_” (underscore) and then followed by the user’s entered file name. The user’s entered file name should ideally be under approximately twenty characters keeping the standard preset + user’s entered file name total length at or under 50 characters.
6. Text File Directory
Specify the directory path for the outbound locker location. The directory path must end without a backslash. The directory path must exist prior to entry; any change or removal of directory will alert user.
Click Copy to indicate a program name and select text file(s) to copy into the FOL directory. Note that this button is enabled regardless of System Control FM background process disabled setting.
7. File Name Preset for FOL
Specify File Name Preset for FOL directory file names field. Use any arrangement of: DTCUP (dateYYYYMMDD, timeHHMMSS, company, user, "-"+program+"-"). Any change of order will alert user.
Use these check boxes to manage how appended files are retain in the Outbound Locker. The checked are unchecked, by default. Changing check box settings will not ‘clean up’ existing files having appended characters in the FOL; existing files would need manual removal or wait for system clean up, if set in System Clean Up FM (SMF993), to remove them.
8. Keep Files ‘name.n’:
Check this box to keep files that would be appended with ".n". These are files whose SMSBOD tie to DOSBOD fails or have no corresponding DOSBOD record.
9. Keep Files ‘name.w’:
Check this box to keep files that would be appended with ".w". These are files that have partially processed the SMSBOD ties to SMXOUH/SXMOUL, some successfully, some failed.
10. Keep Files ‘name.c’:
Check this box to keep files that would be appended with ".c". These are files that have completed/successfully written to SMXOUH/SXMOUL.
11. Keep Files ‘name.x’:
Check this box to keep files that would remain appended with ".x". These are files that fail in some way to create SMXOUH/SMXOUL records.
Inbox/Outbox tab
1. Logical ID (LID)
Specify the logical ID that identifies the Infor OS connection point. The first two sections of the lid are “infor” and “facts”, if that is the what will be assigned to FACTS as the root of the LID.
2. Database ID
Specify the database ID that identifies the ION database. If you change the database ID, a message is displayed, indicating if there are any unprocessed records remaining in any other database used for Infor OS.
3. Inbox XML Destination
Specify the ION Inbox XML delivery destination: T-TCP/IP, D-Polling Directory, N-N/A.
IMS tab
1. Logical ID
Specify the logical ID that identifies the Infor OS connection point. The first two sections of the lid are “infor” and “facts”, if that is the what will be assigned to FACTS as the root of the LID.
2. Version
Specify the version of the multipartMessage API calls of the IMS Messaging Service: V2 or V3
Use the “versions” of the api calls to determine and set the expected version and message method of the object.
The IMS versions, v2/test or v3/acceptedDocuments are used to connect/send the appropriate REST/API IMS call to Infor OS CE. This includes retrieving Auth Tokens, verifying the tenant is valid, verifying the connection point is active, and so on, before processing/removing SMXOUH/SMXOUL records.
3. Enable IMS Logging
Indicate whether to enable logging for IMS: Yes, No, or Off. When enabling IMS logging, it is important to understand the impact of the different settings. When the I2 process is first started, and IMS is being used for communication to Infor OS, the “Enable IMS logging” value is evaluated. If it is set to ‘Yes’ or ‘No’, the value of this setting is checked each time a message is sent to IMS. If it is ‘Yes’, then a log entry is created. If it is ‘No’, then no log entry will be created. If it is set to ‘Off’, then there will be no logs, and there will be no further checking to see if logging is enabled until the I2 process is cycled. These options provide the ability to control logging “on the fly” while debugging or troubleshooting. When finished, the setting should always be turned ‘Off’ to avoid the unnecessary reading and checking of the logging setting each time a message is being sent, causing a small hit on performance. After turning IMS logging 'Off', the I2 background process will need to be cycled for the system to recognize a change back to 'Yes' or 'No'.
4. Number of logs
Specify the number of log files to keep for IMS debugging. You must keep at least 2 log files.
5. IMS Parameters
Click Import to populate the IMS credentials file information in an .ionapi file. These parameters can only be imported from a *.ionapi file that is generated when Infor OS is provisioned. You cannot modify parameter information. Optionally click Clear to remove all of the settings or Test IMS to determine if the current .ionapi file works correctly.