The following table lists the Oracle One-to-One Fulfillment profile options.
| Name | Category | Seeded Description | Description | Example |
| JTO: Debug: Enable UI Debug | Debug | When true, write debug output directly to the generated JSP page. | Print debug statements on JSP pages. | <blank> |
| JTO: Email: Tracking URL | Setup | URL to embed in email messages used to register when a recipient opens a received email. See the Implementation Guide for this value. | - | <img src="http://<host>:<port>/OA_HTML/jtffmImageTracker.jsp?PAGE.OBJ.requestId=&PAGE.OBJECT.objId=&file_name=jtfutrpx.gif" height="0" width="0" alt=""> |
| JTO: Email: Unsubscribe email footer for TEXT emails | Setup | This profile stores the text and the URL that will be added to the end of text format email body; this portion points the user to the Unsubscribe page in the application. | - | - |
| JTO: Email: Unsubscribe URL | Setup | The unsubscribe text at the end of the email message and the URL link to allow recipients to add their email addresses to a Do Not Contact list. | - | "To unsubscribe, please click <a href="http://jtotest.us.oracle.com/OA_HTML/amsContactPreferencesMain.jsp?PAGE.OBJ.requestId=&PAGE.OBJ.objId=">here<a/> |
| JTO: Integration: OSO Create Page JSP | Integration | The JSP filename of the page invoked from the Fulfillment Status page Create button. | Destination of the Create page button. | <blank> |
| JTO: Integration: OSO Done Page JSP | Integration | The JSP filename of the page to return to after submitting a request. | Destination of the Create page button. | jtffmast.jsp |
| JTO: Interaction History: Result ID Failure | Interaction History | Interaction History result ID assigned to failed requests. | Set the Interaction History result ID of failed dispatches of the Fulfillment Server. | 9 |
| JTO: Interaction History: Outcome ID | Interaction History | Interaction History outcome ID assigned to requests. | Set the Outcome code of Interactions logged by the Fulfillment Server. | 10 |
| JTO: Interaction History: Result ID Success | Interaction History | Interaction History result ID assigned to successful requests. | Set the Interaction History result id of successful dispatches of the Fulfillment Server. | 8 |
| JTO: Merge Delimiter: Left | Setup | Merge field left delimiter. | Designate the left delimiter of merge fields. | << or {( |
| JTO: Merge Delimiter: Left Encrypted | Setup | Used to designate the left delimiter of encrypted merge fields. | Designate the left delimiter of encrypted merge fields. | << or {( |
| JTO: Merge Delimiter: Right | Setup | Merge field right delimiter. | Designate the right delimiter of merge fields. | >> or )} |
| JTO: Merge Delimiter: Right: Encrypted | Setup | Designate the right delimiter of encrypted merge fields. | Designate the right delimiter of encrypted merge fields. | >> or )} |
| JTO: Security: IMAP Password Encryption Key | Setup | The value to encrypt the bounceback account password. | Key used to encrypt and decrypt bounceback password. | changeme |
| JTO: Security: Merge Field Encryption Key | Setup | The value to encrypt and decrypt merge fields. | Key used to encrypt and decrypt encrypted merge fields. | changeme |
| JTO: Server: Batch Size | Setup | Used in the multithreaded design for the server, this profile specifies the number of request lines that are picked up by the server in one database call during the request fulfillment process. Server needs to be restarted for the change in this profile to take effect. | - | - |
| JTO: Server: Default Server ID | Setup | The default server to use when the user is not associated with any server. | Used by the APIs. The default server is assumed as the Rapid Install server (serverId - 5000). Groups can set up their own default server in this profile. | 5000 |
| JTO: Server: Error Log Filename | Setup | The server error log filename. | Default Fulfillment Server Error Log name. | Errors.log |
| JTO: Server: Event Log Filename | Setup | Events log file name. | Default Fulfillment Server Event Log name. | Events.log |
| JTO: Server: Log Level | Debug | Level of logging. | Level of logging used by the Fulfillment Server. | 2 |
| JTO: Server: Preload Contact Preferences | Setup | Used in the multithreaded design for the server, this profile specifies if the server should check the TCA contact preference for the TCA party in the request lines. | - | - |
| JTO: Server: Record success for Mass request at Batch level only | Setup | Used in the multithreaded design for the server, this profile specifies if the server should make a database update for every request line. Such updates slow down the request completion time. Please note that with this profile set to "Y", the database update is only done for failed lines. This means that if for some reason the fulfillment server Java process is killed the server will have no recollection of the emails sent successfully. When the server is brought up subsequently there is a chance that the server will send some emails again. | - | - |
| JTO: Server: Refresh Idle Milliseconds | Setup | The time, in milliseconds, during which the Fulfillment Server rests between self-diagnostic inspections. | Time, in milliseconds, during which the Fulfillment Server rests between self-diagnostic inspections. | 20000 |
| JTO: Server: Temp Directory | Setup | Fulfillment temp directory. | Default location for creating Fulfillment Server temporary files. | tmp |
| JTO: Server: Use Multithreaded Fulfillment | Setup | Specifies if the fulfillment server should use the multithreaded design for mass email requests. This profile option does not impact the processing for single & test requests. Also this design is not used for requests of type other than the email media type. Server needs to be restarted for the change in this profile to take effect. | - | - |