05-25-2012 04:32 AM
we are on PPMC 8.0 version.
I am trying to update the values from Table component to other and the values are not getting refreshed untill i clear the cache through "sh kRunCacheManager.sh". Did any one had same issue in 8.0 version.
05-25-2012 04:37 AM
If you are making updates directly to the database, you are not seeing an issue, but how the product works. PPM keeps a local cache of database information and if you make a change directly to the database, that cache needs to be cleared, hence the need to run kRunCacheManager.sh.
05-25-2012 06:14 AM
Are you updating the values in the Table Component using some sql mechanism within the workflow? You can include additional command line to clear cache with option to clear Table Component cache. This was on page load after the execution step, the table component will show updated values.
05-25-2012 06:38 AM
Please do the configuration per attached screenshots,
Screenshot 1 shows how to define the execution step. The command to execute is sh kRunCacheManager.sh A, The option A refers to All. I do not remember on top of my head what is the option for Table Component but I think it is 10 or 11, you can verify that if you have access to the shell prompt by executing only sh kRunCacheManager.sh and it shows all the options and the description of what they do.
Screenshot 2 provides the information about defining the source environment where the clear cache command needs to be executed.
Let me know if you have any further questions.
05-30-2012 07:16 AM
I see that you are using SOURCE_ENV="[AS.PPM_TEST]"
Please use this : SOURCE_ENV="[AS.SERVER_ENV_NAME]" & on the properties of the execution step mention PPM_TEST as your source environment.
Refer to Vamsee_2.JPG attachment from my previous posting
05-30-2012 07:20 AM
We use the following command to clear a cache. It does not require an ssh connection so it is much quicker. Also, we try to clear just the caches that hold data we have modified. The command is:
ksc_local_exec sh "cd bin;./kRunCacheManager.sh [CACHE_ID]"
The cache that holds table entries is the Table Field Entries cache. In 9.14, this is cache id 8. The cache ids can and do change with versions so check the value for the version you are running.
05-30-2012 07:32 AM
Can you please provide me with the error log, screenshot of the execution step source and the workflow step properties? Do you have this execution set as immediate?
05-30-2012 07:45 AM
Do you have error log when this execution step is getting executed? I am interested to see if the folder structure is different for your bin folder.
Also, can you VERIFY the environment PPM_TEST. This execution step picks up the environment definition to login to the server before executing the sh command. Share the screenshot if it is failing.
05-30-2012 08:02 AM
Are you saying that the execution step is failing with no error? What do you mean when you say it is not working?
Share the graphical view and request status to help me understand if the request is stuck at this execution step.
05-30-2012 08:17 AM
Try removing the spaces around the = on the ksc_connect_source_server command:
Also, specify a path for the script in case the current working directory is not in the path variable:
sh ./kRunCacheManager.sh A
05-31-2012 04:19 AM
I checked in the log it says that Refused to connect. Attached is the log file error message.
And when try to use the command ksc_local_exec "cd bin;sh ./kRunCacheManager.sh A" itsthrowing an error "cannot find the file specified". Attached is log.
05-31-2012 07:34 AM
The error message in the log is:
Cannot run program "sh": CreateProcess error=2, The system cannot find the file specified
If the sh command cannot be found, there are some serious basic configuration problems in your environment. Try executing the following command before this commands to see what the PATH variable contains and what the default working directory is:
ksc_local_exec echo $PATH
The connection refused messages appear to be related to the smtp server, probably for sending notifications. They should not be related to the problems with executing these commands.
05-31-2012 07:40 AM
Can you share the screenshot of the sh kCacheManager.sh A command execution from your shell prompt? You have mentioned in this posting that you have to do that each time the table component is updated. I would like to see how you do that? the screeshot should help us see the directory that you go to. Also execute pwd before executing the sh kRunCacheManager.sh command.
05-31-2012 10:45 AM
05-31-2012 12:35 PM
Often you can avoid the stale cache issues by including values for LAST_UPDATE_DATE AND LAST_UPDATED_BY on whatever entities you are updating. It's been a while since I've worked with table components, but you might try updating these values for kcrt_table_entries and also kcrt_request_details and kcrt_requests for that same request_id. Usually, that forces a refresh of the request in the front end without having to run the cache manager shell script...