Page Comparison

Sets the list of feedtypes that will utilize streaming extracts, if such exist. Default value: all feedtypes (the list may vary for different EagleML versions). Please note, that this parameter was introduced in June 2016 EagleML Release. Its alternative obsolete version is w_eagleml_streaming_t which is strongly not recommended for newer environments

If you create a custom streaming transformation step using IWS, the generated code will contain a link to core EJM file (/eagle_ml-2-0_cm/streaming_task_getinfo.inc). After publish if you drop any file into this process, the code inside core include file will overwrite the original incoming file name by simple CorrId value and cause errors.
This parameter by default has Y (or empty) value – in this case original file name will be kept in the TSR. If set to N – then only CorrID value will be in the processed file name in TSR.

Generates an empty extraction file in case you get NO_DATA. Its task parameter version for RTR is ForceExtractFileCreation

Toggle extract file compression (zip/gz archive). 

Extraction with 'compress' parameter. 

Entity Accounting Periods extract option. If W_AUTOADDBASIS = Y the extract will contain <autoAddBasis>Y</autoAddBasis> node. If such extracted file is sent for load afterwards, the inbound rule will load a new Accounting Basis (a row in RULESDBO.ENTITY_ACCT_BASIS) if it cannot find the Account Basis set in the inbound rule for the Portfolio Acct (Entity Id) in DB.
This option is especially useful for ETL processes in which the extract is sent for load at once. 

A setting for extracts with Entity fields (such as Entity Id, Name, Xref etc).
N: The following fileds are extracted: Entity Id, Entity Name, Entity Type, Xref Account Id, Xref Account Id Type, Xref Class Code
Y: These fields are extracted along with ones above: Long Entity Name, Legal Entity Name, Total Count Share Class, Partition Number
ALL: Physical Partition fields are extracted along with all fields above: PPTRADES, PPHOLDING, PPCASH, PPPERFORM, PPLEDGER
See a more detailed description of these fields. 

• Prior NAV (NAV for the previous Valuation Date), 
• Mkt Value Cash (elements from the Position Detail table in case Base Currency = Local Currency or sum of elements in case Base Currency != Local Currency), 
• Share Class Level (elements of ARCH_CTRLCTR.NAV_DETAILS table linked with main table via Valuation Date, Entity Id, Share Class), 
• Total Fund Level (elements of  ARCH_CTRLCTR.NAV_DETAILS сtable linked with main table via Valuation Date, Entity Id for Share Class = 'TF')
• Distribution Log Level

Works only with WRHSNAVMONTHENDEXTRACT feedtype

Alternative for a single extract event is the RTR parameter includeReportDetails

• Prior NAV (NAV for the previous Valuation Date), 
• Mkt Value Cash (elements from the Position Detail table in case Base Currency = Local Currency or sum of elements in case Base Currency != Local Currency), 
• Share Class Level (elements of ARCH_CTRLCTR.NAV_DETAILS table linked with main table via Valuation Date, Entity Id, Share Class), 

• Total Fund Level (elements of  ARCH_CTRLCTR.NAV_DETAILS сtable linked with main table via Valuation Date, Entity Id for Share Class = 'TF')

• Distribution Log Level

Works only with WRHSNAVMULTIEXTRACT feedtype

Alternative for a single extract event is the RTR parameter includeCustomReportDetails

If set to Y, the Asset Properties model is added to the extract. 

Enables date rules for extracts. One of the parameters is the username you use in the environment. 

Example before encryption:

<COL TAG="wa_DateRulePass" EXPRESSION="'eaglepassword'"/>

Example after encryption:

<COL TAG="wa_DateRulePass" EXPRESSION="'base64aes~esC4Vn7jf6jjf0/SXstfjdw46mufgl0k/t'" ENCRYPTED="YES"/>

The password for the user name in the environment you specified in wa_DateRule parameter. Encryption is mandatory. 

Enables/disables extraction of duplicate entities for entityselectiontype = ENTITYID filter. You do not get duplicate entities if set to 'Y'.

Switch to Y, if you want to use XREF and LEI tables to filter records by update_date. E.g., you have an entity with update date 1/1/2012 with a linked XREF of 1/1/2014. Using update date filter by 1/1/2013 with W_ENTITY_UPDATE_DEEP option will return. 

This parameter works only with delta-based extracts. 
 
ALWAYS - always rewrite the last run date value after delta-based extraction
NEVER - switches off rewriting last run date
ONLY_DATA_EXTRACTED - change last run date only if some data has been extracted

This parameter works only with ReportDictionary extracts. If this parameter is set to Y, then whenever we do a delta based dictionary extract, we should only look at SECURITY_DICTIONARY_LINK.SECURITY_DATE to determine the linked assets (and their corresponding dict detail) records to extract. There is no need to check dict detail update_date for delta based dictionary extracts in the selection criteria if that flag is set to Y. Available as an RTR task parameter.

Sets the amount of records per batch.

Task parameter version is MicroBatchKeyRecordCount

Works only with WRHSTRADEEXTRACT

Setting to Y enables S2P remaping for the following fields:
'secFee' is mapped into 'otherFee'
'secFeesBase' is mapped into 'otherFeeBase'
'exchangeFee' is mapped into 'secFee'
'exchangeFeeBase' is mapped into 'secFeeBase'
'otherFee' is mapped into 'exchangeFee'
'otherFeeBase' is mapped into 'exchangeFeeBase'.

RTR parameter is EnableS2PReMappingFlag

Setting to N disables the rollback in xmldbapi format.

Works with WRHSOPENLOTEXTRACT and WRHSPOSITIONEXTRACT.

Setting to N removes the Batch key added to Warehouse extracts in delta mode. 

RTR analog is BatchMode = N

Please refer to Configure Delivery Method Options page for a complete guide.

A number of objects to be purged or archived and the parameters of the process in the appropriate format. 

Toggle Purge and Archive logging. Available as an RTR task parameter - loggingEnabled.

File path for purge and archive log file.

List of ftp folders to be cleaned up and purge intervals for them.

The folder used in the ftp cleanup process.

List of app folders for cleanup and purge intervals for them. 

Cleanup mode: either MOVE or DELETE. If set to MOVE the W_CONFIG_APP_CLEANUP_MOVE_FOLDER variable must be specified.

The folder used in the app cleanup process.

Works with IWS workflows

• N or OFF - TSR/ASK messages are named by default.
• Y or ON - TSR/ASK messages are named as defined in the IWS solution.
• ONonlyForIWS - If the solution was created via IWS, the TSR/ASK messages are named as defined in the solution. If not defined - default names are assigned.
• ONuseExactFileName - excludes correlationID prefix from the file name when you use ACKStrictPattern or TSRStrictPattern parameters. Read more in EJM Job Notification Overview
  Please note, that this option should be handled with care, because in case different processes get the same file patterns, files will be rewritten by the latter process.

You will find more details in the Setting Custom TSR/ACK Names tutorial on IWS wiki.

Works with IWS workflows

• Y or ON – TSR messages will be saved in ../cmw/reply/workflowname and ACK messages in ../cmw/ack/workflowname. 
• N or OFF – TSR and ACK use default folders as their location.
• ONonlyForIWS – Only IWS created solutions will use custom folders as their location.

CustomReplyLocation and CustomAckLocation parameters override this parameter.

Read more in the Setting Custom TSR/ACK Locations tutorial on IWS wiki.

Toggle moving result ZIP file to FTP. 

Toggle using an additional subprocess (dp_log insert) within Generic Load.

Defines the format of Warehouse Position and Warehouse Open Lot extracts.

N (default), Y

workflow name

time in seconds

These three parameters allow to enable and control CacheValidation sub-process prior to the extract step. 

• EnableValidateCache (RTR) and global parameter W_ENABLE_VALIDATE_CACHE to enable the step prior to extract

• CacheValidationWorkflow (RTR) and global parameter W_CACHE_VALIDATION_WORKFLOW which specifies the Name of the workflow which will be triggered via the sub-process

• CacheReloadPeriod (RTR) and global parameter W_CACHE_RELOAD_PERIOD which controls how often cache validation will run. The established setup time is in seconds.

Set a custom batting order for all extracts in the environment.

Set a custom xref map for all extracts in the environment.

Set a custom security resolution option for all extracts in the environment.

Available for Warehouse Position and Warehouse Open Lot. Provides an option to force custom primaryAssetIdType in the extract.

Toggles using specific SWAP security resolution logic.

Setting this parameter to ALLOW_DUPL_XREF turns off the logic excluding xref duplicates.

Can be used for a single message by adding the following element to it: 

<assetResolutionOption>ALLOW_DUPL_XREF</assetResolutionOption>

For Accounting CA only.

By default the message is not failed if tag 302 is not resolved and throws only a WARNING.

If tag 302 is not resolved, you can choose to fail such messages by setting either:

• global variable W_GENERICCA_IGNORE_EDITCHECK302 with the value ‘N’ or
• element referenceTransaction/header/processingOptions with the value ‘USE_TOASSET_CHECK’ 

For IssuePrice, ExchangePrice and IssuePcPrice.

By default SWAP resolution for prices has specific logic based on Processing Security Type and only one leg could be priced.

The flag allows to switch on SWAP resolution based on xreferences, ignoring PST.

This mode can be enabled for a single message by setting element referenceTransaction/header/processingOptions with the value 'PRICE_RESOLVE_SW_BY_XREF'_RESOLVE_SW_BY_XREF'

W_SKIP_DELISTED_SECURITY

Indicates that delisted security will be skipped or not.

W_DELISTED_SECURITY_IDENTIFIER_TYPES

Xreference identifier types separated by comma or 'ALL’ (which indicates that all xref identifier types will be checked).

W_DELISTED_SECURITY_TOKENS

Tokens are used to indicate that a security is delisted. List of tokens separated by comma.

Setting to Y makes the interface use not only the first entity cross reference in the incoming data, but all xrefs instead to resolve the entity.

Can be especially useful for Warehouse and Accounting interfaces which have full entity resolution switched off for compatibility reasons.

Entity Batting Order determines which entity xreference identifiers are used in the security resolution and their order for matching.

entity resolution option:

RESOLVE_ENTITY_BY_XREFS,
SKIP_INCOMING_ENTITY_ID 

RESOLVE_ENTITY_BY_XREFS switches on entity xref resolution even if the entity id is defined. This mode can be enabled for a single message by setting <entityResolutionOption>RESOLVE_ENTITY_BY_XREFS</entityResolutionOption> in the incoming message.

SKIP_INCOMING_ENTITY_ID allows to skip incoming entity id value and to generate entity id if it was not resolved. This mode can be enabled for a single message by setting <entityResolutionOption>SKIP_INCOMING_ENTITY_ID </entityResolutionOption> in the incoming message.

Sets a custom entity xref map for all loads in the environment.

Set to Y to ignore identifiers with empty id values specified in the <xrefIdentifiers> section. Read more on this page.

Task reported checks the size of received files,
- for FILE - once in 5 seconds
- for FTP/SFTP - once in 20 seconds

By default, if file size remains the same between two checks, the file is taken into further processing.

You can make the process perform size checks for an extended time to make sure the file was fully delivered. Default value is 300 seconds. Read more

The folder where workflow profiles will be stored (default value is ../estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm_profiles).

Client information added to alerts. Can be used to identify the environment sending alerts and to provide more details about it.

Add emails to the default list (:W_EAS_MAIL_LIST: in w_config.inc) to receive EAS alerts.

A filter for EAS alerts. Alerts matching a pattern will be delivered, others will be ignored.

This parameter is usually resolved automatically in the get_enviroment_name.inc include. But you can set it manually.

This parameter contains delivery methods, separated by “!”. For each delivery method you can (optionally) specify methods for Control Messages. The attempt to send Control Message(s) will take place after trying to write and read a file using the specified method.

Delivery method is separated from optional parameters by “:”. Optional parameters are separated by “,”. At least one method for Control Messages should be specified for each Delivery method.

The example gives the following instructions: read/write through FILE method, then try to send EXTRACT and WORKFLOW Control Messages, then check read/write for FTP and FTP_CURL. If there is an instruction to send Control Messages, the results will be checked after a timeout. In case the Control Message returns an error or does not return any results, alert will be generated and sent according to the configuration. 

Available delivery methods:
•       FILE
•       FTP 
•       FTP_CURL
•       SFTP_CURL

Available commands for them:
•       EXTRACT
•       WORKFLOW
•       PACE_EVENT
•       STAR_EVENT
•       LOAD 

Settings for an RTR job.

Defines the timeout between steps since the last message processed (or queued if W_LAST_SEQUENCE is empty).

Sets the processing folder for Sequencer. Default is out/TAGVALUE/eagle_ml-2-0_default_cm_sequencer/incoming/ 

Toggle skipping the load step (generic_load) within generic_load_enrichment workflow.

Toggle skipping RDC call (PACE job) within generic_load_enrichment workflow. 

Toggle monitoring stream usage.

Toggle monitoring sch stream usage - monitoring_sch stream is used to launch monitoring for a separate process.

Name of the monitoring stream.

Process id for your monitoring stream. 

New application id for your monitoring stream.

Old application id for your monitoring stream. W_MONITOR_CUR_APP_ID will be replaced with W_MONITOR_APP_ID in the system.

List of streams and folders to be monitored.

CM_EA_FTP_READER is an alternative for the FTP stream, its main feature is that it takes the list of files from DB sitesee instead of calling FTP
It is commonly used to avoid the FTP plugin issue - too frequent FTP pulling.

Set custom XSD validation file location. 

Set custom schema location. 

Defines if an environment is set as Spoke in an I2I process.

Defines if an environment is set as Hub in an I2I process.

Toggle loading SMF into the history table (equal to forcing <historyOnlyFlag>=Y) within an I2I process, when the data is extracted from the composite table of Hub and then loaded into the history table of Spoke. 

This parameter affects Warehouse Performance - Delta Mode only. Allows to load Warehouse Performance even in case STATUS_FLAG is already set as F(FINAL). 

When set to N, extracts in delta mode do not use orchestration. 

Configure the FTP for I2I

Configure the Web Service for I2I

Some parameters are noted as Required - this is only in case you want to use Web Service delivery method

I2I Filters

I2I workflow parameters

Available since May 2016 EagleML Release. Toggles displaying details for successful substeps. Switched off ("Y") by default. Read more... 

Setting to Y enables Event Entity Details for STAR events and for DataMart Model Manager steps in the final TSR for PACE jobs - these are available since May 2016 EagleML Release for PACE and since September 2016 EagleML Release for STAR. In addition, includes execution details for STAR (available since October 2016 EagleML Release). Read more... 

Enable security-level details for failed TSR for RDC Composites. 

Data delivery stream for TBA workflow. 

If value is set to Y the last step of each relevant workflow will start the next one automatically. 

Defines the number of retry attempts. 

Defines the timeout between attempts. Read more.. 

Defines the number of retry attempts. 

Defines the timeout between attempts. Read more.. 

Custom NG schema name. Default value is core schema name

Custom NG package name. Default value is core package name + _NG

Custom NG SP name. Default value is core SP name + _NG

Ignore POS_FLAG field in POSITION flag during load. Available since February 2017 EagleML release.