For full profiling
A full profile of an application by CodeLogic will seek to understand the structure of binaries as well as relationships to other applications (API calls) and databases. In this case we recommend installing a Java or .NET agent on a machine the service(s) run on in a test environment. From there, an agent can scan multiple services that run on the same machine.
Running in a “live” instance allows access to configuration information that supplies hints to the CodeLogic engine about which databases are being served, and provides a proper environment runtime profiling.
In the pipeline
To trigger regular rescans from your continuous delivery pipeline, there are two options:
- Binary profiling at build time: An agent installed on the build machine can profile new builds in place. This will provide structural updates quickly. A single Java or .NET agent can process the builds of many projects.
- Full profiling in a test stage: Runtime scans benefit from the software being broadly exercised. Profiling during a stage of the pipeline where comprehensive functional regression tests are executed is ideal.
CodeLogic database agents connect to databases on other servers. They do not need to be installed on the database server – just a machine that can reach them. A single database agent can profile many servers.
Agents for AWS infrastructure and profiling of ServiceNow are similar.
- Server A has Service1, Service2, Service3 (all Java)
- Server B has Service1, Service2, Service3 (all Java)
- Server A and B are identical and behind a load balancer.
- Server C has Service 4 (.NET)
- Server D has Service 5 (.NET)
- DB Server X has DB1
- DB Server Y has DB2
In this case, install the Java agent on Server A or B, but there’s no need to install on both. Install the .NET agent on Server C and Server D. Install the SQL agent on any server with network access to both databases (A, B, C, X, or Y) and have it connect to both databases remotely.