Removing Agent Builder application support data from the TEPS database
SandraWeiss 060000BCJJ Visits (9852)
There may be times when you need to modify or replace an Agent Builder agent and after running the installation for the "modifed" agent, child navigator items are not displaying properly in the TEP GUI. The workaround is to create SQL DELETE statements which are run against the TEPS database and then to re-run the installation of application support for the Agent Builder agent.
So how do you know what the DELETE statements should be? Start with a saveexport from the TEPS.
Generating a saveexport:
From there you will find all entries that have the K + the agent code. For example if the agent code is 25, you would look for all entries with K25 and k25.
Use the following rules when creating the DELETE statements making sure to take into account case (lower k, upper K):
The order of the delete statements is very important since there are dependencies within the tables. Make sure to put your delete statements into a file using the order above where any KFWWORKSPACELINK entries would be first and KFWQUERY would be last.
Then you want to run the sql against the TEPS database. It is recommended to keep an original copy of the saveexport.sql file in case anything does not work as expected. This will allow you to restore the TEPS database. To run the sql, KfwSQLClient is very handy. KfwSQLClient ? will display help. Examples on how to use KfwSQLClient follow:
On WINDOWS is it located in the ITM $CANDLEHOME\CNPS.
set SQLLIB=PATH WHERE SQL_FILE_NAME RESIDES
KfwSQLClient /d DSN /f SQL_FILE_NAME (DSN is usually TEPS2)
On UNIX go to $CANDLEHOME/bin and run the following commands:
export SQLLIB=PATH WHERE SQL_FILE_NAME RESI
./KfwSQLClient /d KFW_DSN /f SQL_FILE_NAME (KFW_DSN should not be changed... it is KFW_DSN)