Configure Servers

Servers can be managed in Setup IFS Connect window. This is located in Solution Manger / Integration / IFS Connect.

Contents

• Configure Servers
• Configure J2EE Server

Configure Servers

Currently there is one server available in IFS Connect setup. This is a J2EE Server.

J2EE Server configures behavior of the IFS Connect framework running within the actual Middleware Server, i.e. Message Router, Batch Processor and Reader Framework. This is only possible to have one instance of this type.

Configure J2EE Server

• USE_CACHE
  Controls using of internal caches. Enabled by default.
• CBR_ON_ERROR
  Tick to enable Content Based Routing on Error. If enabled a new Application Message will be created on failure during background processing of messages. This message will contain detailed information about the failed message and also the message itself, if its size in kB is not greater then defined by the CBR_ON_ERROR_MAX_SIZE parameter.
  This functionality can be very useful for monitoring purpose. It is necessary to create suitable Outbound Routing Rule(s) from APPLICATION_MESSAGE that will route such messages. MESSAGE_TYPE has to be defined to be equal APPLICATION_ERROR.
  An example of such message:
  
• CBR_ON_ERROR_MAX_SIZE
  Defines the maximum size in kB of the original message to attach to error message. If actual message size is greater than the maximum size the message will not be included.
• DEFAULT_WORK_TIMEOUT
  Default work timeout in seconds for execution of native code or BizAPIs. Read more about work managers.
• BIZAPI_WORK_TIMEOUT
  Work timeouts for BizAPIs, service handler operations and PL/SQL methods. Read more about work managers.
• BIZAPI_MAX_RETRIES
  For some none-fatal Oracle errors during execution of Inbound BizAPI (or Handler:Operation) or PL/SQL method, Batch Processor can make some more attempts after some time before placing the message in state FAILED. This parameter defines maximum number of such attempts.
  Following Oracle errors can cause Batch Processor to retry the operation:
  ORA-00054 - resource busy and acquire with NOWAIT specified or timeout expired
  ORA-00060 - deadlock detected while waiting for resource
  ORA-04021 - timeout occurred while waiting to lock object
  ORA-04061 - existing state of package has been invalidated
  ORA-04065 - not executed, altered or dropped package
  ORA-04068 - existing state of package has been discarded
  ORA-20113 - raised from Error_SYS.Record_Locked and Error_SYS.Fnd_Record_Locked
  
• BIZAPI_RETRY_INTERVAL
  The number of seconds between each attempt.
• PROPERTIES
  Some properties used by IFS Connect that in IFS Applications 9 and earlier versions have been read from file ifs.properties can now be defined here,
  Some of the most important properties that are currently supported by this feature:
  
  • ifs.persistSynchronousMessages - force Batch Processor to always save synchronous messages; default false.
  • ifs.plsqlapInvokeTimeout - timeout in seconds used by the new way of invoking outbound messages from PLSQL Access Provider; default 1200.
  • ifs.plsqlapInvokeUseHttp - if set to true, the PLSQL Access Provider will use the HTTP protocol when invoking outbound messages. Default false.
  • ifs.enableApplicationMessageStat - enables statistics that can help to find out proper values for constraints controlling behavior of Oracle AQ based invocation flows in PLSQL Access Provider. Default false.
  • ifs.httpClientConnectTimeout - HTTP client connection timeout in seconds; default 500.
  • ifs.httpClientReadTimeout - HTTP client read timeout in seconds; default 500.
  • ifs.ftpClientTimeout - FTP connection timeout in seconds; default 500.
  • ifs.sftpClientTimeout - SFTP connection timeout in seconds; default 500.
  • fnd.restrictedQueueSendDelay - delay in seconds before additional JMS messages requesting checking of an restricted queue is sent; default 30.
    
  • fnd.restrictedQueueMaxProcessTime - restricted queue timeout in seconds; default 300.
    
  • fnd.restrictedQueueChunk - maximum number of messages processed in the same chunk by a restricted queue; default 10000.
    
  • fnd.restrictedQueueStopCheck - number of processed messages before Batch Processor will check if the actual queue is stopped; default 1.
    
  • fnd.useConnectReaderWorkManager - if true IFS Connect will not use thread isolation (work managers) for processing of native connect reader code; default false.
    
  • fnd.useRouteRuleCache - if false legacy routing rules will not be cached; default true.
  • fnd.soapServiceGatewayPort - port SOAP Gateway (integration cluster) is listening on, if not the same as main cluster (Client Gateway).
  • fnd.connectReaderQueueMaxReadAttempts - max number of attempts to read a listed reader message from database; default 3.
  • fnd.connectReaderQueueReadAttemptWaitTime - time in seconds between attempts to read listed reader messages from database; default 3 sec.
  • fnd.routerImplementation - decides which implementation of Router to use; possible values are new, legacy and both; default is new.
    
  Read more about how to work with grid parameters.