Migrating Java Libraries

Note: When the policy is set up on the AI Team Edition, ensure that the same data elements added for the AI Developer Edition are used. For more information about the data elements policy, refer to Policy Definition.
If you use different data elements while creating the policy, then modify the data elements used in the AI Developer Edition accordingly before running the modules.

1. Install and set up the New Foundational Architecture (NFA) and AI Team Edition using the steps from the NFA documentation and the respective feature documentation.

2. Install Application Protector Java libraries using the steps from the Application Protector Java documentation.

   Note: When prompted for the ESA IP address, enter the IP address of the NFA ESA. Similarly, when prompted for the ESA listening port number, enter 25400. This IP address and the port number enables the protector to integrate with the NFA ESA.

3. Include the ApplicationProtectorJava.jar in the classpath of your applications.

4. Navigate to the location where the AI Developer Edition is cloned.

5. Go to the protegrity-developer-edition/samples/java directory.

   a. Update the pom.xml and the application-protector-java dependency.

   ```
   <dependency>
       <groupId>com.protegrity</groupId>
       <artifactId>application-protector-java</artifactId>
       <version>1.0.1</version>
       <scope>system</scope>
       <systemPath>/opt/protegrity/sdk/java/lib/ApplicationProtectorJava.jar</systemPath>
   </dependency>
   ```
   

   Note: The AP Java libraries are expected to be in the default path /opt/protegrity/sdk/java/lib/. If the installation uses a different directory, update the environment or configuration so the system can locate the correct JAR files.

   b. Run the following command.

   ```
   ./mvnw clean package
   ```
   

   c. Update the sample shell script to include ApplicationProtectorJava.jar in the classpath.

   d. Run the samples.