Oracle NCA correlation
I am trying to correlate the icx_ticket value below:
nca_connect_server("184.108.40.206", "10513", "module=/tthyki/applmgr/11510/fnd/11.5.0/forms/US/FNDSCSGN fndnam=APPS config='tthyki' icx_ticket='.J8tLby3gHAuLsxwcNEFc9g..' resp='CSS/TKE^US^DEBRIEFING' secgrp='STANDARD' start_func='TKEU_TP_CUS_CD_14_ENTRY'::NLS_LANG='AM ERICAN_AMERICA.UTF8' FORMS60_USER_DATE_FORMAT='DD-MON-RRRR' FORMS60_USER_DATETIME_FORMAT='DD-MON-RRRR HH24:MI:SS' NLS_DATE_LANGUAGE='AMERICAN' NLS_SORT='BINARY' NLS_NUMERIC_CHARACTERS='.,' FORMS60_TZFILE='timezlrg.dat' FORMS60_DATETIME_SERVER_TZ='America/Chicago' FORMS60_DATETIME_LOCAL_TZ='America/Chicago'");
I recorded the script 3 times and noticed the value that was dynamic is the string between . and ..
Here is the correlation function that I am using:
web_reg_save_param("icx_ticket", "LB=ticket='.", "RB=..'", LAST);
I keep getting the following error:
Action.c(135): Registering web_custom_request("fndutil.jar") was successful [MsgId: MMSG-26390]
Action.c(144): web_concurrent_end started [MsgId: MMSG-26355]
Action.c(144): Error -26377: No match found for the requested parameter "icx_ticket". Check whether the requested boundaries exist in the response data. Also, if the data you want to save exceeds 10000 bytes, use web_set_max_html_param_len to increase the parameter size [MsgId: MERR-26377]
Action.c(144): web_concurrent_end highest severity level was "ERROR", 454957 body bytes, 819 header bytes [MsgId: MMSG-26388]
Abort was called from an action.
Starting action vuser_end.
Ending action vuser_end.
Am I setting the boundaries correctly ?
This looks like your understanding of LR is not great - I would suggest very strongly either training or a mentor - however
the code that you have posted, the nca_connect_server() is a request - ie what is sent to the server and not a response - what is returned from the server.
correlation involves taking values from responses and inserting them into the correct place in a subsequent request
therefore it would seem that you are looking (ie the web_reg_save_param() function) in the wrong place and that undoubtedly the left and right boundaries are incorrect
look for the values prior to their use in a request, the web_save_param() goes before the request that the response that the required value is first found in
the boundaries should be taken from the response
almost definitely the web_set_max_html_length instruction is superfluous - the default size is 256 characters