On the vApp r14.3cp2 we see the error message often in server.log
ERROR [ims.tmt.persistence] (default task-92) PersistenceProvider: default task-92: searchTasks: Exception searching for tasks: com.netegrity.ims.exception.IMSException:
Invalid Task Id/Task Number.
: com.netegrity.ims.exception.IMSException:
Invalid Task Id/Task Number.
With debug enabled for im=DEBUG ims=DEBUG, we see a query for "task.tag=test".
When we review the vApp solution, we see there is a query within the vApp scripts:
/opt/CA/VirtualAppliance/scripts/.monitoring_scripts/test-im-connectivity.sh
HTTP_CODE_ENV=$(timeout ${HTTP_CONN_TIMEOUT} curl --connect-timeout ${HTTP_CONN_TIMEOUT} --silent --write-out %{http_code} http://$IM_HOST:$IM_PORT/iam/im/$PUB_IM_ENV/ui7/index.jsp?task.tag=test --output /dev/null)
The "test-im-connectivity.sh" script is called by
/opt/CA/VirtualAppliance/scripts/.monitoring_scripts/check_IDM_and_router_status.sh
It appears this testing process has been in place since 2018.
But there is no documented process to have an IM Admin Task named "test" to fully use this embedded testing process.
Request: Documentation on using "task.tag=test" to fully use the testing process or patch to adjust this process to remove the error message due to incorrect testing due to missing IM Admin Task.
Release : 14.3
Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)
Vapp uses tag name "test" just to test the IM server is up and running ex: "http://hostname:8080/iam/im/pubidentityEnv/ui7/index.jsp?task.tag=test" and IM server capture the log error message as "task.tag=test" is not there in DB when IM debug mode enabled.
We advise, to avoid this error in the log please create a "Test" task with tag name "test" and make this task as public