Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
tutorial:dev:creating_a_development_environment [2019/07/30 12:51] – link to external frontend build instructions poulmtutorial:dev:creating_a_development_environment [2025/04/11 09:10] (current) – [Working-around IdM rebuild when developing backend module] fiserp
Line 1: Line 1:
 ====== Creating a development environment ====== ====== Creating a development environment ======
  
-This text is intended as a tutorial for CzechIdM developers with the goal to set up IDE, build CzechIdM in it and run the system. If you prefer quick glance at the code or need to start quickly, you can use [[tutorial:dev:quick_start_with_devstack|]].+This text is intended as a tutorial for CzechIdM developers with the goal to set up IDE, build CzechIdM in it and run the system. If you prefer quick glance at the code or need to start quickly, you can use [[.:quick_start_with_devstack|]].
  
 ====== 1. Install Java and Maven ====== ====== 1. Install Java and Maven ======
Line 7: Line 7:
 First install JDK and Maven: First install JDK and Maven:
  
-Download Java 1.8 Oracle JDK (or OpenJDK), minor version **at least 101** (it's necessary due to the certificate of Nexus repository, which uses Let's encrypt and its support was added in version 101). The guide was tested for jdk1.8.0_131.+Download and install Java 11 OpenJDK (Java 21 OpenJDK for CzechIdM 13.1.0+).
  
 Install Maven from your system packages, at least version 3.1 is required. Install Maven from your system packages, at least version 3.1 is required.
 +
 <code bash> <code bash>
 yum install maven yum install maven
 mvn -v mvn -v
 +
 +
 </code> </code>
  
 Note: If you installed Java separately from your system libraries, you should set the correct Java home for Maven in the file ".mavenrc", which you will create in your home directory. You put there the full path to your JDK: Note: If you installed Java separately from your system libraries, you should set the correct Java home for Maven in the file ".mavenrc", which you will create in your home directory. You put there the full path to your JDK:
 <code> <code>
 +
 export JAVA_HOME=/path/to/installed/jdk/ export JAVA_HOME=/path/to/installed/jdk/
 +
 </code> </code>
 +
 This way Maven will always use this JDK. This way Maven will always use this JDK.
  
Line 27: Line 33:
 <code bash> <code bash>
 git clone https://github.com/bcvsolutions/CzechIdMng.git git clone https://github.com/bcvsolutions/CzechIdMng.git
 +
 +
 </code> </code>
  
-Check branch: +Check branch:
  
 <code bash> <code bash>
 git branch git branch
 +
 +
 </code> </code>
  
Line 39: Line 49:
 <code bash> <code bash>
 git checkout -b develop origin/develop git checkout -b develop origin/develop
 +
 +
 </code> </code>
  
Line 45: Line 57:
 <code bash> <code bash>
 git checkout -b personal/YourName/feature_or_bugfix-name_of_your_branch git checkout -b personal/YourName/feature_or_bugfix-name_of_your_branch
 +
 +
 </code> </code>
  
Line 51: Line 65:
 ====== 3. Install PostgreSQL ====== ====== 3. Install PostgreSQL ======
  
-CzechIdM in "dev" profile uses PostgreSQL as the repository. You have to install it at least in basic configuration:+CzechIdM in "dev" profile uses PostgreSQL as the repository. 
 + 
 +You have to folow one of these next steps. Choose one which fits you more. 
 + 
 +  - PostgreSQL to computer 3.1. 
 +  - Run docker image with postgres part 3.2. 
 + 
 +===== 3.1 Install PostgreSQL to computer =====
  
 Install necessary packages: Install necessary packages:
 +
 <code bash> <code bash>
 yum install postgresql postgresql-server postgresql-init yum install postgresql postgresql-server postgresql-init
 +
 +
 </code> </code>
  
 Fedora 25 packages: Fedora 25 packages:
 +
 <code bash> <code bash>
 dnf install postgresql-server postgresql-contrib dnf install postgresql-server postgresql-contrib
 +
 +
 +</code>
 +
 +Ubuntu 22.04 LTS packages:
 +
 +<code bash>
 +apt install postgresql postgresql-contrib
 +
 +
 </code> </code>
  
 First run of the service: First run of the service:
 +
 <code bash> <code bash>
 systemctl start postgresql.service systemctl start postgresql.service
 +
 +
 </code> </code>
  
-If the following error occurs: "Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details." +If the following error occurs: "Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details." Try initializing the PostgreSQL first and start the database again:
-Try initializing the PostgreSQL first and start the database again:+
  
 <code bash> <code bash>
 postgresql-setup --initdb --unit postgresql postgresql-setup --initdb --unit postgresql
 +
 +
 </code> </code>
  
 Set automatic start of the service when starting OS: Set automatic start of the service when starting OS:
 +
 <code bash> <code bash>
 systemctl enable postgresql.service systemctl enable postgresql.service
 +
 +
 </code> </code>
  
 Set the configuration file for the database to accept login and password (change METHOD from ident to md5) Set the configuration file for the database to accept login and password (change METHOD from ident to md5)
 +
 <code> <code>
 vim /var/lib/pgsql/data/pg_hba.conf vim /var/lib/pgsql/data/pg_hba.conf
 +
 +in Ubuntu it is:
 +vim /etc/postgresql/14/main/pg_hba.conf
 +
 +in Windows it is:
 +<Postgress Install Dir>/Data/pg_hba.conf
  
 # TYPE  DATABASE        USER            ADDRESS                 METHOD # TYPE  DATABASE        USER            ADDRESS                 METHOD
Line 92: Line 141:
 # IPv6 local connections: # IPv6 local connections:
 host         all                  all                ::1/128                     md5 host         all                  all                ::1/128                     md5
 +
 </code> </code>
  
 Restart the service to load the changes: Restart the service to load the changes:
 +
 <code> <code>
 systemctl restart postgresql.service systemctl restart postgresql.service
 +
 </code> </code>
  
-Create the database: +Create the database with name: 
-(Make sure you have installed and allowed en_US locale in your OS)+ 
 +  * Version 13 is for IdM 13 and develop (IdM 14) - bcv\_idm\_13 
 +  * Version 10 is for IdM 12 - 10 - bcv\_idm\_10 
 +  * Below version 10 - bcv\_idm\_storage 
 +  * (Make sure you have installed and allowed en_US locale in your OS)
  
 <code> <code>
 su postgres -c psql postgres su postgres -c psql postgres
 CREATE USER idmadmin PASSWORD 'idmadmin'; CREATE USER idmadmin PASSWORD 'idmadmin';
-CREATE DATABASE "bcv_idm_storage" WITH OWNER idmadmin ENCODING 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8' template template0;+CREATE DATABASE "bcv_idm_13" WITH OWNER idmadmin ENCODING 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8' template template0; 
 +CREATE DATABASE "bcv_idm_10" WITH OWNER idmadmin ENCODING 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8' template template0; 
 + 
 +</code> 
 + 
 +===== 3.2 Run postgreSQL in docker container ===== 
 + 
 +Installation instructions for **Docker**  **only**  or **Docker desktop**  are here: [[http://docs.docker.com/engine/install/|docker engine installation]]. 
 + 
 +After installation of docker. Use next command which will create postgres container with user and password which is used for development. 
 +<code> 
 + 
 +docker run --name postgresql -e POSTGRES_USER=idmadmin -e POSTGRES_PASSWORD=idmadmin -p 5432:5432 postgres:14.5 
 + 
 +</code> 
 + 
 +Connect to docker container and create the databases with names: 
 + 
 +  * Version 13 is for IdM 13 and develop (IdM 14) - bcv\_idm\_13 
 +  * Version 10 is for IdM 12 - 10 - bcv\_idm\_10 
 +  * Below version 10 - bcv\_idm\_storage 
 +  * (Make sure you have installed and allowed en_US locale in your OS) 
 +  * \l command will return list of databases make sure you have properly set owner of databases! 
 + 
 +<code> 
 +docker exec -it postgresql /bin/bash 
 +psql -U idmadmin 
 + 
 +CREATE DATABASE "bcv_idm_13" WITH OWNER idmadmin ENCODING 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8' template template0; 
 +CREATE DATABASE "bcv_idm_10" WITH OWNER idmadmin ENCODING 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8' template template0; 
 + 
 +\l 
 + 
 +</code> 
 + 
 +After running command "\l" you should see this: 
 +<code> 
 +                                       List of databases 
 +         Name          |  Owner   | Encoding |  Collate   |   Ctype    |   Acces 
 +s privileges    
 +-----------------------+----------+----------+------------+------------+-------- 
 +--------------- 
 + bcv_idm_10            | idmadmin | UTF8     | en_US.utf8 | en_US.utf8 |  
 + bcv_idm_13            | idmadmin | UTF8     | en_US.utf8 | en_US.utf8 |  
 +</code> 
 + 
 +Database will be available on address: 
 + 
 +<code> 
 + postgresql://localhost:5432/postgres 
 </code> </code>
  
Line 112: Line 218:
 The tutorial is different for each IDE. Select one and continue with a certain tutorial below: The tutorial is different for each IDE. Select one and continue with a certain tutorial below:
  
-  * [[devel:documentation:quickstart:dev:ide:eclipse|Eclipse]] +  * [[:devel:documentation:quickstart:dev:ide:eclipse|]] 
-  * [[devel:documentation:quickstart:dev:ide:idea|IDEA]]+  * [[:devel:documentation:quickstart:dev:ide:idea|]]
  
 In the IDE start the Tomcat server with CzechIdM deployed. In the IDE start the Tomcat server with CzechIdM deployed.
Line 119: Line 225:
 In browser access [[http://localhost:8080/idm-backend/api/v1/status|http://localhost:8080/idm-backend/api/v1/status]] to check whether the backend is running. Following text should be displayed: In browser access [[http://localhost:8080/idm-backend/api/v1/status|http://localhost:8080/idm-backend/api/v1/status]] to check whether the backend is running. Following text should be displayed:
  
-> CzechIdM API is running +> CzechIdM API is running > > If you can see this message, API is running
-> +
-> If you can see this message, API is running +
  
 ====== 5. Frontend development environment ====== ====== 5. Frontend development environment ======
  
-<note important>**BEWARE!!!** Please use these [[https://github.com/bcvsolutions/CzechIdMng/tree/develop/Realization/frontend|instructions]]</note>+<note important>**BEWARE!!!**  Please use these [[https://github.com/bcvsolutions/CzechIdMng/tree/develop/Realization/frontend|instructions]]</note> 
 + 
 +===== Select IDE for frontend environment ===== 
 + 
 +You can use any text editor or JavaScript IDE. We recommend to use ATOM 
 + 
 +  * See [[:devel:documentation:quickstart:dev:ide:atom|ATOM tutorial]]
  
 ====== 6. Run backend and frontend together ====== ====== 6. Run backend and frontend together ======
Line 139: Line 248:
 cd CzechIdM/Realization/frontend/czechidm-app cd CzechIdM/Realization/frontend/czechidm-app
 gulp gulp
 +
 +
 </code> </code>
  
-A new browser window or tab will open with [[https://localhost:3000]] automatically (this could take some time).+A new browser window or tab will open with [[https://localhost:3000|https://localhost:3000]] automatically (this could take some time).
  
 The frontend is fully started after you see in following line in log: The frontend is fully started after you see in following line in log:
Line 147: Line 258:
 <code bash> <code bash>
 [BS] 1 file changed (app.js) [BS] 1 file changed (app.js)
 +
 +
 </code> </code>
  
 After the application is running, log in: After the application is running, log in:
 +
   * username: admin   * username: admin
   * password: admin   * password: admin
  
-<note tip>If the app shows error with permission, log out</note> +<note tip>If the app shows error with permission, log out</note> <note tip>To use CzechIdM in more windows or tabs for development purposes go to [[http://localhost:3001/|http://localhost:3001/]] to **BrowserSync**  administration and then go to **SyncOptions**  and disable everything except **CodeSync**</note>
-<note tip>To use CzechIdM in more windows or tabs for development purposes go to [[http://localhost:3001/]] to **BrowserSync** administration and then go to **SyncOptions** and disable everything except **CodeSync**</note>+
  
 Congratulations! Your CzechIdM development environment is ready to use. Congratulations! Your CzechIdM development environment is ready to use.
- 
  
 ====== Common development errors & tips ====== ====== Common development errors & tips ======
Line 164: Line 276:
  
 If Tomcat server fails to start, try following: If Tomcat server fails to start, try following:
-  * Increase the timeout for Tomcat server Start (see [[devel:dev:quickstart:ide:eclipse#install_tomcat|Install Tomcat]])+ 
 +  * Increase the timeout for Tomcat server Start (see [[https://tomcat.apache.org/download-90.cgi|Install Tomcat]])
   * Check that PostgreSQL server is running.   * Check that PostgreSQL server is running.
 +
 <code bash> <code bash>
 systemctl status postgresql.service systemctl status postgresql.service
 +
 +
 </code> </code>
-  * Check that PostgreSQL database exists and the user can connect: Use the credentials filled in ''idm-app/src/main/resources/application-dev.properties'' and try to connect to the PostgreSQL database written in the datasource URL. E.g. for this setup:+ 
 +  * Check that PostgreSQL database exists and the user can connect: Use the credentials filled in ''idm-app/src/main/resources/application-dev.properties''  and try to connect to the PostgreSQL database written in the datasource URL. E.g. for this setup:
 <code> <code>
 +
 spring.datasource.url=jdbc:postgresql://localhost:5432/bcv_idm_storage spring.datasource.url=jdbc:postgresql://localhost:5432/bcv_idm_storage
 spring.datasource.username=idmadmin spring.datasource.username=idmadmin
 spring.datasource.password=idmadmin spring.datasource.password=idmadmin
 +
 </code> </code>
 +
 use the following command and type the password when asked for it. use the following command and type the password when asked for it.
 +
 <code bash> <code bash>
 psql -h 127.0.0.1 -U idmadmin bcv_idm_storage psql -h 127.0.0.1 -U idmadmin bcv_idm_storage
 +
 +
 </code> </code>
 +
   * Check that you can read from the tables of the database. As in the previous point, connect to the PostgreSQL database and try to select data from any of the IdM tables. If you have insufficient access rights, check the owner and grants for the schema "public". If the user idmadmin is not an owner, there must be GRANT on schema public to the user idmadmin or to "public".   * Check that you can read from the tables of the database. As in the previous point, connect to the PostgreSQL database and try to select data from any of the IdM tables. If you have insufficient access rights, check the owner and grants for the schema "public". If the user idmadmin is not an owner, there must be GRANT on schema public to the user idmadmin or to "public".
   * Check the error message in the server output console.   * Check the error message in the server output console.
Line 184: Line 308:
 ==== Common error messages ==== ==== Common error messages ====
  
-''Initialization of bean failed; nested exception is org.flywaydb.core.api.FlywayException: Validate failed: Migration checksum mismatch for migration 7.07.004'' means that your database was already used for some other version of CzechIdM (you can check used Flyway versions in the tables idm\_schema\_version\_xxx). This can happen if you switch to some older development branch. The easiest solution for the **developer** (you will lose all your prepared data in IdM!) is to drop the database (''DROP DATABASE bcv\_idm\_storage'') and create it again (see the part ''CREATE DATABASE'' of [[#install_postgresql|Install PostgreSQL]]). Or you can create a different database and set its name to the ''application-dev.properties'' temporarily.+''Initialization of bean failed; nested exception is org.flywaydb.core.api.FlywayException: Validate failed: Migration checksum mismatch for migration 7.07.004''  means that your database was already used for some other version of CzechIdM (you can check used Flyway versions in the tables idm\_schema\_version\_xxx). This can happen if you switch to some older development branch. The easiest solution for the **developer**  (you will lose all your prepared data in IdM!) is to drop the database (''DROP DATABASE bcv\_idm\_storage'') and create it again (see the part ''CREATE DATABASE''  of [[#install_postgresql|Install PostgreSQL]]). Or you can create a different database and set its name to the ''application-dev.properties''  temporarily.
  
-''Initialization of bean failed; nested exception is org.flywaydb.core.api.FlywayException: Found more than one migration with version 7.07.004'' means literally that there is a duplicity in Flyway scripts versions. This has to be fixed by the authors of the scripts by renaming one of the script that use the same version. The log will tell you where to find the duplicity:+''Initialization of bean failed; nested exception is org.flywaydb.core.api.FlywayException: Found more than one migration with version 7.07.004''  means literally that there is a duplicity in Flyway scripts versions. This has to be fixed by the authors of the scripts by renaming one of the script that use the same version. The log will tell you where to find the duplicity:
 <code> <code>
 +
 Offenders: Offenders:
 -> ... idm-core-impl-7.7.0-SNAPSHOT.jar!/eu/bcvsolutions/idm/core/sql/postgresql/V7_07_004__automatic-role.sql (SQL) -> ... idm-core-impl-7.7.0-SNAPSHOT.jar!/eu/bcvsolutions/idm/core/sql/postgresql/V7_07_004__automatic-role.sql (SQL)
 -> ... idm-core-impl-7.7.0-SNAPSHOT.jar!/eu/bcvsolutions/idm/core/sql/postgresql/V7_07_004__add-index-template-name.sql (SQL) -> ... idm-core-impl-7.7.0-SNAPSHOT.jar!/eu/bcvsolutions/idm/core/sql/postgresql/V7_07_004__add-index-template-name.sql (SQL)
 +
 </code> </code>
 +
 Just increase the version in the name of one of the scripts, clean & build the project again. Just increase the version in the name of one of the scripts, clean & build the project again.
- 
  
 === Could not create Vfs.Dir from url === === Could not create Vfs.Dir from url ===
 +
 **This isn't error just warning**. You may don't interest about this warning. Warning is only when you start local development environment and you configuration for ic connectors path isn't correctly setup. Dont worry about this warning. **This isn't error just warning**. You may don't interest about this warning. Warning is only when you start local development environment and you configuration for ic connectors path isn't correctly setup. Dont worry about this warning.
  
Line 203: Line 330:
 org.reflections.ReflectionsException: could not create Vfs.Dir from url, no matching UrlType was found [file:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/libatk-wrapper.so] org.reflections.ReflectionsException: could not create Vfs.Dir from url, no matching UrlType was found [file:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/libatk-wrapper.so]
 either use fromURL(final URL url, final List<UrlType> urlTypes) or use the static setDefaultURLTypes(final List<UrlType> urlTypes) or addDefaultURLTypes(UrlType urlType) with your specialized UrlType. either use fromURL(final URL url, final List<UrlType> urlTypes) or use the static setDefaultURLTypes(final List<UrlType> urlTypes) or addDefaultURLTypes(UrlType urlType) with your specialized UrlType.
 +
 </code> </code>
 +
 +===== Frontend build fails =====
 +
 +==== Out of memory ====
 +
 +If your gulp build fails with the following error:
 +
 +<code>
 +[INFO] [18:43:00] Starting 'browserify'...
 +[INFO] [18:45:30] Finished 'browserify' after 2.5 min
 +[INFO] [18:45:30] Finished 'build' after 3.12 min
 +[INFO]
 +[INFO] <--- Last few GCs --->
 +[INFO]
 +[INFO] 192087 ms: Scavenge 1282.6 (1434.8) -> 1282.1 (1434.8) MB, 3.8 / 0 ms (+ 3.8 ms in 9 steps since last GC) [allocation failure].
 +[INFO] 192095 ms: Scavenge 1282.6 (1434.8) -> 1282.2 (1434.8) MB, 3.6 / 0 ms (+ 3.3 ms in 8 steps since last GC) [allocation failure].
 +[INFO] 192102 ms: Scavenge 1282.6 (1434.8) -> 1282.1 (1434.8) MB, 3.7 / 0 ms (+ 2.9 ms in 7 steps since last GC) [allocation failure].
 +[INFO]
 +[INFO]
 +[INFO] <--- JS stacktrace --->
 +[INFO] Cannot get stack trace in GC.
 +[ERROR] FATAL ERROR: Scavenger: semi-space copy
 +[ERROR] Allocation failed - process out of memory
 +[ERROR] 1: node::Abort() [gulp]
 +
 +</code>
 +
 +Try following:
 +
 +  * Go to ''Realization/frontend/czechidm-app/''  and delete ''node\_modules''. Then start the build again (''npm install''  etc.)
 +  * If you build BE+FE of a project together, check the ''pom.xml''  of the app module - the configuration properties ''nodeVersion''  and ''npmVersion''. They should be the same as the product currently supports (check the [[https://github.com/bcvsolutions/CzechIdMng/blob/develop/Realization/backend/app/pom.xml|app module of the product]]):
 +<code>
 +
 +                        <execution>
 +                                <id>install node and npm</id>
 +                                <goals>
 +                                    <goal>install-node-and-npm</goal>
 +                                </goals>
 +                                <phase>generate-resources</phase>
 +                                <configuration>
 +                                    <nodeVersion>v10.15.3</nodeVersion>
 +                                    <npmVersion>6.4.1</npmVersion>
 +                                </configuration>
 +                        </execution>
 +
 +</code>
 +
 +  * try adding ''\–max\_old\_space\_size=4096''  to the ''gulp''  command. Or if you build BE+FE together by app module, try adding it in the pom.xml of the app:
 +
 +<code>
 +                                                         <execution>
 +                                                                <id>gulp build</id>
 +                                                                <goals>
 +                                                                        <goal>gulp</goal>
 +                                                                </goals>
 +                                                                <phase>generate-resources</phase>
 +                                                                <configuration>
 +                                                                        <arguments>build -p ${frontend.profile} -s ${frontend.stage} --max_old_space_size=4096</arguments>
 +                                                                        <workingDirectory>../../frontend/czechidm-app</workingDirectory>
 +                                                                        <installDirectory>target</installDirectory>
 +                                                                </configuration>
 +                                                        </execution>
 +
 +</code>
 +
 +==== Wrong layout and NPM version ====
 +
 +If your frontend looks like this: [[https://redmine.czechidm.com/issues/1752|https://redmine.czechidm.com/issues/1752]], check following:
 +
 +  * there is package-lock.json file in the frontend app module and it looks like this: [[https://github.com/bcvsolutions/CzechIdMng/blob/develop/Realization/frontend/czechidm-app/package-lock.json|https://github.com/bcvsolutions/CzechIdMng/blob/develop/Realization/frontend/czechidm-app/package-lock.json]]
 +  * NPM version which you use when building frontend (or FE+BE) is at least 6.
 +<code>
 +
 +npm -v
 +6.4.1
 +
 +</code>
 +
 +====== Developing on Appliance ======
 +
 +This section contains howtos and hacks for more effective development on IAM Appliance.
 +
 +===== Working-around IdM rebuild when developing backend module =====
 +
 +When you are developing a backend module and need to debug it directly on the Appliance, each ''iam-czechidm'' service restart forces the application to relink... which can take significant amount of time.
 +To speed things up you can, technically, edit the content of existing container without the need for relink.
 +
 +<note warning>This is really nonstandard hack and exercising special care is absolutely necessary.</note>
 +
 +**Remarks**
 +  * If you are debugging a frontend module, this howto **will not work** because the frontend rebuild will be skipped.
 +  * If you forget to properly persist your changes (see steps below) you are creating rather nasty surprise for anybody who re-creates the ''czechidm'' docker container. And as the original container gets deleted in the process, you will have no way to find out what happenned. Always clean up after yourself.
 +
 +**Steps**
 +  - (you start developing, add all your modules into proper folders in the appliance, restart the ''iam-czechidm'' service, let the build process finish)
 +  - At this point, you have a basis of the application you are going to develop further. You can even have some custom frontend parts put in.
 +  - Suppose you want to put another JAR into you application or replace one that is already here. (here we work with ''ssh-connector-1.0.1.jar'' as an example)
 +    - Copy new / modified files directly into the container. <code>[root@appliance70 ~]# docker cp ssh-connector-1.0.1.jar czechidm:/opt/tomcat/current/webapps/idm/WEB-INF/lib/
 +Successfully copied 28.2kB to czechidm:/opt/tomcat/current/webapps/idm/WEB-INF/lib/</code>
 +    - In case you need to delete something, remove it directly from the container. **This is the way you now have to handle conflicting libraries, by the way.**<code>[root@appliance70 ~]# docker exec czechidm ls -l /opt/tomcat/current/webapps/idm/WEB-INF/lib | grep ssh
 +-rw-r--r--. 1 root root    26277 Apr 10 13:05 ssh-connector-1.0.1.jar
 +
 +[root@appliance70 ~]# docker exec czechidm rm -fv /opt/tomcat/current/webapps/idm/WEB-INF/lib/ssh-connector-1.0.1.jar
 +removed '/opt/tomcat/current/webapps/idm/WEB-INF/lib/ssh-connector-1.0.1.jar'
 +
 +[root@appliance70 ~]# docker exec czechidm ls -l /opt/tomcat/current/webapps/idm/WEB-INF/lib | grep ssh
 +(empty listing)</code>
 +    - Restart the IdM container. <code>
 +[root@appliance70 ~]# systemctl restart iam-czechidm</code>
 +    - Let the IdM start as usual. Because you did not change anything in the appliance directories (under ''/data/volumes/czechidm/...'') the relink mechanism will not kick in.
 +  - Repeat the previous step as long as you need to develop / debug your backend module.
 +  - Persist the changes.
 +    - Once you are done working, you need to persist all changes you made. Gather all modules you were working on and put them into directories under ''/data/volumes/czechidm/...'' where they should be located.
 +    - Stop, drop and start the IdM container. <code>[root@appliance70 ~]# systemctl stop iam-czechidm
 +[root@appliance70 ~]# docker rm czechidm
 +[root@appliance70 ~]# systemctl start iam-czechidm</code>
 +    - Let the rebuild finish and wait for IdM to start.
 +    - Test that changes you made are really there.
  • by poulm