Re: Deploy MVN Syncope with Workflow
Apparently is working: we modified the pom.xml in common/core/console/enduser removing the references to the test, we modified the core/src/test/resources file replacing the one present into the "main". We redeployed and for now it looks ok. Thank you On 02/02/2017 14:33, Francesco Chicchiriccò wrote: > On 02/02/2017 14:27, Tech wrote: >> The point is that we create a brand new database (empty), we >> deploying using "-P all" and for some reason the database is already >> filled with some test data. >> >> We see that there are already some connectors configured, some roles >> and moreover some users like "*Verdi*", "*Rossini*" and "*Vivaldi*" >> that we don't understand where they are coming from. > > This is the test content coming from > > core/src/test/resources/domains/MasterContent.xml > > which is normally only loaded when starting in embedded mode; in > production mode (e.g. with plain build) the content from > > core/src/main/resources/domains/MasterContent.xml > > is loaded instead. > > You should identify which MasterContent.xml is actually loaded when > starting with an empty database, and possibly why. > > Normally, the test content is expected to be loaded exclusively in the > in-memory H2 instance used by embedded mode. > > Regards. > >> On 02/02/2017 12:25, Francesco Chicchiriccò wrote: >>> On 02/02/2017 12:21, Tech wrote: Dear experts, we would like to deploy syncope 2.0.2 using the workflows. We are using this command: * mvn -P all clean verify -Dconf.directory=/opt/syncope/conf -Dbundles.directory=/opt/syncope/bundles -Dlog.directory=/opt/syncope/log In the * core/src/main/resources/all/provisioning.properties and * core/src/main/resources/provisioning.properties we configured * quartz.sql=tables_mariadb.sql and in the * core/src/main/resources/domain/Master.properties we configured our MariaDB, but we are still pointing to the H2, while deploying without the option "-P all" we can correctly point to our MariaDB. Is there any other parameter that we should configure? >>> >>> If you want to use, in the application deployed into the external >>> Java EE container (for example) >>> >>> core/src/main/resources/all/provisioning.properties >>> core/src/main/resources/all/workflow.properties >>> >>> instead of >>> >>> core/src/main/resources/provisioning.properties >>> core/src/main/resources/workflow.properties >>> >>> you will need to copy >>> >>> core/src/main/resources/all/provisioning.properties >>> core/src/main/resources/all/workflow.properties >>> >>> to /opt/syncope/conf, as you have configured such directory to be >>> the source for configuration. >>> >>> HTH >>> Regards. > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/
Re: Deploy MVN Syncope with Workflow
On 02/02/2017 14:27, Tech wrote: The point is that we create a brand new database (empty), we deploying using "-P all" and for some reason the database is already filled with some test data. We see that there are already some connectors configured, some roles and moreover some users like "*Verdi*", "*Rossini*" and "*Vivaldi*" that we don't understand where they are coming from. This is the test content coming from core/src/test/resources/domains/MasterContent.xml which is normally only loaded when starting in embedded mode; in production mode (e.g. with plain build) the content from core/src/main/resources/domains/MasterContent.xml is loaded instead. You should identify which MasterContent.xml is actually loaded when starting with an empty database, and possibly why. Normally, the test content is expected to be loaded exclusively in the in-memory H2 instance used by embedded mode. Regards. On 02/02/2017 12:25, Francesco Chicchiriccò wrote: On 02/02/2017 12:21, Tech wrote: Dear experts, we would like to deploy syncope 2.0.2 using the workflows. We are using this command: * mvn -P all clean verify -Dconf.directory=/opt/syncope/conf -Dbundles.directory=/opt/syncope/bundles -Dlog.directory=/opt/syncope/log In the * core/src/main/resources/all/provisioning.properties and * core/src/main/resources/provisioning.properties we configured * quartz.sql=tables_mariadb.sql and in the * core/src/main/resources/domain/Master.properties we configured our MariaDB, but we are still pointing to the H2, while deploying without the option "-P all" we can correctly point to our MariaDB. Is there any other parameter that we should configure? If you want to use, in the application deployed into the external Java EE container (for example) core/src/main/resources/all/provisioning.properties core/src/main/resources/all/workflow.properties instead of core/src/main/resources/provisioning.properties core/src/main/resources/workflow.properties you will need to copy core/src/main/resources/all/provisioning.properties core/src/main/resources/all/workflow.properties to /opt/syncope/conf, as you have configured such directory to be the source for configuration. HTH Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Deploy MVN Syncope with Workflow
The point is that we create a brand new database (empty), we deploying using "-P all" and for some reason the database is already filled with some test data. We see that there are already some connectors configured, some roles and moreover some users like "*Verdi*", "*Rossini*" and "*Vivaldi*" that we don't understand where they are coming from. We don't think that this is the expected behavior, could you please advise? Thanks On 02/02/2017 12:25, Francesco Chicchiriccò wrote: > On 02/02/2017 12:21, Tech wrote: >> >> Dear experts, >> >> we would like to deploy syncope 2.0.2 using the workflows. >> >> We are using this command: >> >> * mvn -P all clean verify -Dconf.directory=/opt/syncope/conf >> -Dbundles.directory=/opt/syncope/bundles >> -Dlog.directory=/opt/syncope/log >> >> In the >> >> * core/src/main/resources/all/provisioning.properties and >> * core/src/main/resources/provisioning.properties >> >> we configured >> >> * quartz.sql=tables_mariadb.sql >> >> and in the >> >> * core/src/main/resources/domain/Master.properties >> >> we configured our MariaDB, but we are still pointing to the H2, while >> deploying without the option "-P all" we can correctly point to our >> MariaDB. >> >> Is there any other parameter that we should configure? > > If you want to use, in the application deployed into the external Java > EE container (for example) > > core/src/main/resources/all/provisioning.properties > core/src/main/resources/all/workflow.properties > > instead of > > core/src/main/resources/provisioning.properties > core/src/main/resources/workflow.properties > > you will need to copy > > core/src/main/resources/all/provisioning.properties > core/src/main/resources/all/workflow.properties > > to /opt/syncope/conf, as you have configured such directory to be the > source for configuration. > > HTH > Regards. > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/
Re: Admin user interface - custom fields order
Hi, In addition to what said yesterday starting from version 2.0.3 (currently SNAPSHOT) you can refer to [5] to add, remove, edit USER attributes sorting strategies. Best regards, Andrea [5] https://github.com/apache/syncope/blob/2_0_X/client/enduser/src/main/resources/META-INF/resources/app/js/app.js#L392 Il 01/02/2017 16:22, andrea ha scritto: Il 01/02/2017 15:13, Tech ha scritto: Dear all, Good evening, please see my response inline. we created some custom fields, like fname and lname. We added to the BaseUser class and we have in the order: * email * fname * lname We log as user to the interface to register a new user, and this order is respected. We go back to the Console and using the interface "Edit AnyTypeClass BaseUser" we change the order as: * lname * fname * email We log with the old user, but the order is still the old one. We create a new user and also in this case the order of the fields is still the old one. Are we missing any step here? No, but you have to consider that ordering of attributes on the Enduser Console is forced to be *alphabetical*. So the result will ever be: * email * fname * lname moreover the order defined during "Edit AnyTypeClass BaseUser" does not matter. The order defined in that form is not applied to other forms, consider the case in which an user or any type has two auxiliary classes (one of the AnyTypeClasses available), which sorting will be taken? On the *administration console* the ordering of the attributes into the edit form is alphabetical, too; though it can be customized through advanced techniques. To force another kind of schema sorting in the *Enduser Console* you should edit UserController.js (see [1]) by sorting schemas variable or schemaService.js (see [2] and [3]) by sorting response.data (you may extract it into a new variable). We created just now a new issue about a better sorting customization; please take a look at [4]. Thanks HTH regards, Andrea [1] https://github.com/apache/syncope/blob/2_0_X/client/enduser/src/main/resources/META-INF/resources/app/js/controllers/UserController.js#L71 [2] https://github.com/apache/syncope/blob/2_0_X/client/enduser/src/main/resources/META-INF/resources/app/js/services/schemaService.js#L33 [3] https://github.com/apache/syncope/blob/2_0_X/client/enduser/src/main/resources/META-INF/resources/app/js/services/schemaService.js#L45 [4] https://issues.apache.org/jira/browse/SYNCOPE-1005 -- Andrea Patricelli Tirasa - Open Source Excellence http://www.tirasa.net/ PMC member at The Apache Software Foundation Syncope -- Andrea Patricelli Tirasa - Open Source Excellence http://www.tirasa.net/ PMC member at The Apache Software Foundation Syncope
Re: Deploy MVN Syncope with Workflow
On 02/02/2017 12:21, Tech wrote: Dear experts, we would like to deploy syncope 2.0.2 using the workflows. We are using this command: * mvn -P all clean verify -Dconf.directory=/opt/syncope/conf -Dbundles.directory=/opt/syncope/bundles -Dlog.directory=/opt/syncope/log In the * core/src/main/resources/all/provisioning.properties and * core/src/main/resources/provisioning.properties we configured * quartz.sql=tables_mariadb.sql and in the * core/src/main/resources/domain/Master.properties we configured our MariaDB, but we are still pointing to the H2, while deploying without the option "-P all" we can correctly point to our MariaDB. Is there any other parameter that we should configure? If you want to use, in the application deployed into the external Java EE container (for example) core/src/main/resources/all/provisioning.properties core/src/main/resources/all/workflow.properties instead of core/src/main/resources/provisioning.properties core/src/main/resources/workflow.properties you will need to copy core/src/main/resources/all/provisioning.properties core/src/main/resources/all/workflow.properties to /opt/syncope/conf, as you have configured such directory to be the source for configuration. HTH Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Deploy MVN Syncope with Workflow
Dear experts, we would like to deploy syncope 2.0.2 using the workflows. We are using this command: * mvn -P all clean verify -Dconf.directory=/opt/syncope/conf -Dbundles.directory=/opt/syncope/bundles -Dlog.directory=/opt/syncope/log In the * core/src/main/resources/all/provisioning.properties and * core/src/main/resources/provisioning.properties we configured * quartz.sql=tables_mariadb.sql and in the * core/src/main/resources/domain/Master.properties we configured our MariaDB, but we are still pointing to the H2, while deploying without the option "-P all" we can correctly point to our MariaDB. Is there any other parameter that we should configure? Thanks
