Averitt Express

Problem 1:

Encountering an issue while deploying client objects in the AIS after creating tables. Specifically, facing a problem with the deployment of one table: "Unable to restore database tables Reason: insert failed for table au_ftpevents: Index 52 out of bounds for length 52". Please refer to the attached screenshot for further details.

Open

Cause: This scenario arises when the data in the fields exceeds the specified(52) length.

Solution: We are required to extract the au_ftpevents individually and then create separate zip files for each one, followed by deploying them in AIS one at a time.

Problem 2:

Following deploying the corrected objects to Adeptia Connect, we conducted validation checks on the process flow, transactions, data mappings, and other activities. Unfortunately, we encountered issues with accessibility to the process flows and data mappings. Refer to the below image:

Open

Solution:

Follow the steps below:

Step 1: Replace the xmldbms-1.0.jar file in the specified path: …\AIS\AdeptiaSuite\AdeptiaSuite-6.9\AdeptiaServer\ServerKernel\dependency.

Step 2: Make sure to redeploy the accelerator in the AC before deploying the corrected objects.

Step 3: Deploy the corrected object in Adeptia Connect.

Problem 3:

While redeploying the corrected objects to Adeptia Connect after changing xmldbms.jar in the dependency folder, an error was encountered: Insert Failed for the table ac_company, Duplicate entry 'ECSTAR' for key 'ac_company.NAME'.

Cause: This situation arises because we previously deployed the objects in Adeptia Connect and are now re-deploying the corrected objects in Adeptia Connect after replacing the xmldbms.jar.

Solution:

Step 1: Execute the DBCleanup.jar utility to establish new tables in Adeptia Connect.

Step 2: Re-deploy the corrected object to Adeptia Connect.

Step 3: Launch Adeptia Connect and verify the activities, including process flows and data mappings.

Problem 4:

Once the migration is complete and the objects are deployed, it is essential to conduct testing on the test cases provided by the client. Upon modifying the source and target paths, updating the event details, and executing the transaction, an error was encountered and not executed as expected. Please refer to the attached screenshot for further details.

Solution: No Solution Yet.

TOPCOO

Problem 1:

Following the deployment of the object from AIS to AC 3.7.2.2. An issue arose where the kernel ceased functioning properly upon restart.

Error message:

Interactive boot failed: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.ExceptionInInitializerError: Illegal JCo archive "sapjco3-3.0.14.jar". It is not allowed to rename or repackage the original archive "sapjco3.jar".
javax.management.RuntimeErrorException: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.ExceptionInInitializerError: Illegal JCo archive "sapjco3-3.0.14.jar". It is not allowed to rename or repackage the original archive "sapjco3.jar".
        at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:836)
        at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:847)
        at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:816)
        at java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
        at com.adeptia.indigo.IndigoKernel.initializeMBeans(IndigoKernel.java:894)
        at com.adeptia.indigo.IndigoKernel.boot(IndigoKernel.java:545)
        at com.adeptia.indigo.IndigoKernel.main(IndigoKernel.java:329)
Caused by: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.ExceptionInInitializerError: Illegal JCo archive "sapjco3-3.0.14.jar". It is not allowed to rename or repackage the original archive "sapjco3.jar".

Solution:

The steps to resolve the issue are:

Step 1: Renaming both the sapjco3-3.0.14.jar and sapidoc3-3.0.12.jar to sapjco3.jar and sapidoc3.jar.

Also, make the same changes in the KernelClasspath and Webrunner classpath.txt files.

Step 2:Added the -Djava.library.path="path till the etc\native folder in JVM parameters(webrunner and Kernel in launcer.properties)

QTS

Problem 1:

The customer has created several custom tables in the Adeptia Backend schema, which failed in the object import process.

Solution:

In such a situation, It is necessary to exclude the tables during the import process.

Problem 2:

Attempting to roll back the changes.
Unable to restore selected database tables.Reason: Insert failed for table AU_FTPEVENT. Activity ID: 010070001022154644474095902310
Index 52 out of bounds for length 52
Reason:java.lang.ArrayIndexOutOfBoundsException: Index 52 out of bounds for length 52

Solution: No Solution Yet.

Problem 3:

Following the deployment of the object to AC, it has been observed that the process flow activity is missing, resulting in certain flows not being opened as expected.

Solution:

Step 1: Deploy the XMLDBMS 1.0 jar file into AIS ....AdeptiaSuite-6.9\AdeptiaServer\ServerKernel\dependency (replace existing one)

Step 2: Extract the object from AIS

Step 3: Deploy the object to AC

Step 4: Deploy connector

Don't run the aistoacmigration.properties file after object deployment to Adeptia Connect.

Problem 4:

The stored procedure is causing the page to become unresponsive when attempting to open it.

Solution:

It is necessary to consult with the product team.

MGIC

Problem 1: During the Installation when we configured the backend and Log Database in AIS, an error occurred during the database connection process with a message stating "error while making a connection to the database." Please refer to the screenshot below for details on this error.

Solution:

Step 1: Go to the directory where you extracted the zip file.

Step 2: Type the command install.exe -DConfigureDBviaURL=true

Step 3: Click Next to view the Configure Backend Database screen.

Step 4: Enter the JDBC URL: jdbc:oracle:thin:@database-1-charter.ciodldmyslmz.us-east-1.rds.amazonaws.com:1521/ORCL

Step 5: Provide the Database credentials & proceed with installation.

Step 6: Follow the same steps from Step 3 onwards for Log Database configuration.