Question

In Client Automation Enterprise (CAE), when running a dmabatch to sync the core with satellites, sometimes some changes are reflected for the PRIMARY.SECURITY Domain in the sync.log, even this domain is not in use.

Example:

ADD PRIMARY.SECURITY.FILE.AXXX

ADD PRIMARY.SECURITY.FILE.AXXX

ADD PRIMARY.SECURITY.FILE.AXXX

REP PRIMARY.SECURITY.PACKAGE.XXX

REP PRIMARY.SECURITY.PACKAGE.XXX

REP PRIMARY.SECURITY.PACKAGE.XXX

Answer

Everytime  the core server/ tomcat server is restarted, the default packages(SCAP, Vulnerability)  gets published into CSDB even though they already been published.

And  if this is done the first time dmasync just after the restart ,these logs gets generated though there is no usage or change of the security domain.

 This can be verify with below steps.

1) On core machine stop all the services except the Configuration Server and DCS service.

2) Run a dmabatch sync from satellite, and check logs. The logs will not contain any of primary.security domain changes as no default package data is published to core CSDB.

3) Start the core service/tomcat service and than do the dmabatch. the logs will have primary.security domain changes.

 This process is part of the design and this a expected behavior.

To avoid these repeated logs ,the promotion of the default paakcges should be stopped.

This can be achceived by:

1)Once these packages gets published into CSDB, If these packages gets removed from the priming folder, these promote will not happen again and again.

2) Stop tomcat server -2) Take backup of the <CA-installed dir>\VulnerabilityServer\content\priming\services

3) Remove the content from the <CA-installed dir>\VulnerabilityServer\content\priming\services folder.

4) Start tomcat server