Information
We are currently investigating an issue with the editor of some pages. Please save your work and avoid to create new pages until this banner is gone.
The first thing required is to prepare the environment for the compilation and execution of ACS and the project being developed.
Code Block | ||||
---|---|---|---|---|
| ||||
source /alma/ACS-2019DEC2021APR/ACSSW/config/.acs/.bash_profile.acs getTemplateForDirectory MODROOT_WS <NameOfYourModule> export INTROOT=~/introot getTemplateForDirectory INTROOT $INTROOT |
Code Block |
---|
#This could be added to the .bash_profile or .bashrc files
export INTROOT=~/introot
source /alma/ACS-2021APR/ACSSW/config/.acs/.bash_profile.acs |
As part of what is delivered, there is a directory called ICD, where all the base definitions are given (ICD/idl) in IDL format (CORBA Interface Definition Language). These will generate code for the different languages supported by ACS (C++, Python and Java).
Code Block | ||||
---|---|---|---|---|
| ||||
#Assuming the environment is correctly prepared cd $REPO_PATH/ICD/src make all install |
This will generate the required libraries (.so and .jar) and source code (.h and .py) for the client stubs (definitions and communication) and skeleton infrastructure (server implementation base).
Another part of the project that is given, is the configuration of the system. In production this configuration is retrieved from an Oracle DB, however for these projects we're using a file system database based in XML files.
Code Block | ||||
---|---|---|---|---|
| ||||
#Either execute the following in every console or add to your .bash_profile or .bashrc files
export ACS_CDB=$REPO_PATH/ITS/config |
This will be used at run-time to deploy components in the running containers.