The Worker process manager component maintains the pool of workerprocess executables to run the jobs. It is responsible for starting a job and stopping workerprocess executable, recycling the process once the process executes set number of jobs, count of process to run, count of concurrent jobs to execute per process. The default configuration is as follows, but you can overwrite it by changing the values in DPS service configuration file:
This section provides information on Application server service startup and its main components.
Application server service startup
The activities that are given below occur in a sequence. If you want to track the progress, you can also track these activities by setting the Application Server log in the verbose mode.
1.Enter startup sequence
Log: Server.Start: Appserver remoting server starting
2.Establish connection to ADAM
Log: Server.Start: Checking for ADAM
Service reads the ADAM server name from the configuration file and tries to connect to the Symantec CCS ADAM instance. If the connection is successful, it builds the CCS object schema cache. If ADAM server is unreachable then service initiates a service shutdown event.
3.Create a Role Based Access Control instance (RBAC)
Log: Server.Start: Loading RBAC
Creates an RBAC instance. This instance is used for all the access control requests.
4.Check for valid core license
Log: Server.Start: Checking Core License
Checks if the CCS core license is valid and creates a timer object that checks the validity for core licenses periodically.
5.Validate server certificate
Log: Server.Start: Validating APS certificate
Validates the Application Server certificate.
6.Establish DPS session manager
Log: Server.Start: Starting Blade Session Manager
Loads the MOS and SCAP schema and sets up the job management infrastructure to facilitate operations such as submit job, collect job results, terminate job, job status, shutdown, and so on.
7.Start WCF service host
Log: Server.Start: Starting up WCF service hosts
Starts to .Net WCF object that allows communication from remote computers or clients to the Application Server.
Log: Server.Start: Generating Symmetric key
Generates key for symmetric cryptography. This must happen before using the secure storage.
Log: Server.Start: Checking local storage for credentials
Application Server service maintains a local secure storage, which is a local credential cache. During installation, the credentials are stored in local cache. When service starts, it checks for this cache and if required reads and updates the secure store cache in ADAM.
10.Start workflow job manager
Log: Server.Start: Starting workflow singleton
Creates objects of job management. Reads database and ADAM, schedules jobs that are required to be scheduled, and schedules a quick health and status job.
Loads the integration bridge manager. The sub system allows consumers of this system to load the Application Server service and also helps the users to call the IB APIs. The clients can be of Symantec workflow components and Powershell script.
12.Triggers system jobs
Log: Server.Start: Running the system jobs
The following predefined jobs are triggered:
·DPS Configuration push
·Full Health and status
·Custom role permissions sync
·Automatic Live update installation job.
Log: Server.Start: Finished starting Application Server
Application server main components
The main components of an Application server service startup are as follows:
The Job Manager executes the jobs in the Application Server. These jobs are implemented using the Windows Workflow Foundation and are in the form of .Net workflows. The Job management component reads these XOML and executes the workflow by loading appropriate binaries.
Licenses are stored in ADAM. The License manager does the following:
Monitor license metering
Check for license expiry
The Application Server creates Job Manager and Schedule Job Manager Thread. The Job Manager is responsible for executing jobs and the Schedule Job Manager is responsible for scheduling jobs and calling the Job Manager to execute the scheduled jobs.
Communication between CCS components
The diagram demonstrates how different components in CCS communicate with each other. The focus is on how console, web console, web services communicates with ADAM and the Application Server.
CCS Console uses the WCF TCP/IP to connect to the Application Server. For faster reads, the CCS Console connects to ADAM directly authenticating the user by Application Server.
Figure 2: Communication between CCS components
Imported Document ID: HOWTO74876
Subscribing will provide email updates when this Article is updated. Login is required.