As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Search for &&KILL_RPC in this forum. You will find more discussions on this topic.
At highlevel, You need to use same logic used in task1 in pre-process and assign 'Y' to &&KILL_RPC variable if the logic fails. Default &&KILL_RPC to 'N'.
This is a good idea. For my client I had to create a log table that has this information and more. We use this data to display reports and graphs on the portal to the business partners in real time (refresh every 10 mins).
dksib DC Tech Services Inc WF 8.2.1M
Posts: 117 | Location: US | Registered: February 09, 2004