Building and deploying the Solution

​

Building the project

​

Set up Artifactory access

<settings>
    <profiles>
        <profile>
            <id>default</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>

            <repositories>
                <repository>
                    <id>ActiveViamMvn</id>
                    <name>ActiveViam Maven Repository</name>
                    <url>https://activeviam.jfrog.io/artifactory/mvn/</url>
                </repository>
                <repository>
                    <id>ActiveViamGeneric</id>
                    <name>ActiveViam Generic Repository</name>
                    <url>https://activeviam.jfrog.io/artifactory/generic/</url>
                </repository>
            </repositories>
        </profile>
    </profiles>

    <servers>
        <server>
            <id>ActiveViamMvn</id>
            <username>username</username>
            <password>password</password>
        </server>
        <server>
            <id>ActiveViamGeneric</id>
            <username>username</username>
            <password>password</password>
        </server>
    </servers>
</settings>

​

Source

​

Build

--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.base/java.nio=ALL-UNNAMED

1. Once you have added all the maven repositories and extracted the source code, run mvn install on the parent pom file to build the entire project. This will build the Atoti Server executable JAR file (simm-starter/target/simm-starter-exec.jar), ActiveMonitor executable JAR file (simm-activemonitor/target/simm-activemonitor-2.0.2-exec.jar) .
2. When the build is complete, you must deploy it. See Deployment.
3. Build the standalone UI application using npm or yarn.
4. Deploy the UI application.

​

Configuration

​

Alternatives

1. If you only want to use the sample data embedded in the project along with the Jetty server, then you don’t need to configure the data directory.
2. You can copy the sample data (simm-starter/src/test/resources/data-samples/data/) into simm-starter/src/main/resources/ then the sample data will be included in the .jar file and you won’t need to set the data directory.

​

Deployment

​

Atoti Server and ActiveMonitor

java -jar simm-starter-exec.jar

java -jar simm-activemonitor-2.0.2-exec.jar

• Use the argument server.port. For example:
  java --add-opens java.base/java.util.concurrent=ALL-UNNAMED -jar simm-starter-exec.jar --server.port=<port>
  
• Externalize the properties files (see Externalizing Properties Files )

​

[Eclipse / IntelliJ]

• Use maven to run an initial build of the Solution $ mvn clean install.
• Start the server by running SimmWebApplication.java in simm-starter/src/java/com/activeviam/simm/starter.
• The server will run at https://localhost:12000/simm-starter
• You will need to compile and serve up the ui from the ui source code, as described in the Atoti UI section below.

​

Atoti UI

1. Build the standalone application:
   1. Set up artifactory access for node dependencies
   2. Download the ui source code from artifactory.
   3. Copy the lockfile for the build tool you use (i.e. package-lock.json for npm, yarn.lock for yarn) into the project’s main directory.
   4. Run npm ci if using npm, or yarn install --frozen-lockfile if using yarn.
   5. Run npm run build if using npm, or yarn build if using yarn.
2. Place the deployment in the webapps folder of your Tomcat:
   1. Find where the webapps folder is for your Tomcat.
   2. Create a folder called simm-activeui in the Tomcat webapps folder.
   3. Copy the contents from the build folder into your new folder webapps/simm-activeui/.
3. Start the Tomcat server. You can now access the UI on the address http://<your hostname>:<port>/simm-activeui/.

​

How to run all tests

​

Externalizing Properties Files

• OPTION 1: Command line arguments, e.g.<span class="measure"> --csvSource.dataset=/path/to/folder</span> .

• OPTION 2: Create a properties file (e.g. <span class="measure">application.properties</span>) and add your property overrides. Then pass it to the main using the command line argument <span class="measure">--spring.config.additional-location=/&lt;path&gt; application.properties</span>
• OPTION 3: Change the path to the default properties file using the appropriate variable specified below:

  File	Variable Name
  simm.properties	app.env.properties.file.path
  hibernate.properties	hibernate.env.properties.file.path

  If any of the above variables are not set, the default properties files will be used. Example values for these properties files include:
  • classpath:<filename>
  • file:/home/etc/<filename>; - Unix Environment
  • file:///C:/Users/john/config/<filename> - Windows environment