The sil-sa-app program will run the SIL-SA service and allow distributed edit and retrieval operations.

Each subsystem needs its own unique name.  The default name is "subsys1".


The make_sil_sa_dir script will generate SIL-SA code stubs for a module


The sil-sa-app will not try to register any callbacks unless it actually finds

SIL-SA libraries.


The example below will use 2 subsystems, named sub1 and sub2



1)  create the SIL-SA library for module1


    > make_sil_sa_dir module1 --sil-get2
    > cd module1
    > make
    > sudo make install


The library will be installed in the yumapro lib dir (/usr/lib/yumapro/libmodule1_sa.so


2)  create the SIL-SA library for module2


    > make_sil_sa_dir module2
    > cd module2
    > make
    > sudo make install


The library will be installed in the yumapro lib dir (/usr/lib/yumapro/libmodule2_sa.so

 

At this time the auto-generated code and example application (sil-sa-app) will register

all the foo_sa libraries it finds, so SA1 will mirror SA2 by default if the subsystems are running on the same system


In order to have each subsystem register different modules, the SIL-SA libraries located in the /usr/lib/yumapro

directory need to be setup correctly to match the desired modules or bundles. Only the SIL-SA libraries

found in the /usr/lib/yumapro directory will be loaded by sil-sa-app.

 

3) start the server

 

   > netconfd-pro --module=module1 --module=module2  ...


4) start SIL-SA sub1

 

  > sil-sa-app --subsys-id=sub1 --log-level=debug4


5) start SIL-SA sub2

 

  > sil-sa-app --subsys-id=sub2 --log-level=debug4


6) edit something in the module. The SIL-SA callbacks will be invoked as needed