Adeptia FAQs

This video shows how easy it is to create and manage your inbound relationships to process incoming HIPAA EDI files from your B2B trading partners using Adeptia.

Steps described in the video are documented here: https://docs.adeptia.com/display/AS/Creating+Inbound+Relationship+for+EDI+Data

HIPAA Integration Tutorial - Defining Inbound Relationships from Adeptia, Inc..

This video shows how easy it is to create and manage your outbound relationships to send HIPAA EDI files to your B2B trading partners using Adeptia.

Steps described in this video are documented here:

https://docs.adeptia.com/display/AS/Configuring+an+Outbound+Message+Processing

HIPAA Integration Tutorial - Defining Outbound Relationships from Adeptia, Inc.

This video shows how easy it is to create and manage your ISA Outbound Envelopes for your HIPAA EDI transactions that you are sending to your B2B trading partners using Adeptia.

Steps described in this video are documented here:

https://docs.adeptia.com/display/AS/Creating+ISA+Outbound+Envelope

HIPAA Integration Tutorial - Creating ISA Outbound Envelope from Adeptia, Inc.

This video shows how easy it is to create and manage your target configurations for your HIPAA EDI transactions that you are exchanging with your B2B trading partners using Adeptia.

Steps described in this video are documented here:

https://docs.adeptia.com/display/AS/Creating+an+Outbound+Target

HIPAA Integration Tutorial - Target Configurations from Adeptia, Inc.

In this example we will check if the source records in the incoming CSV file contains any errors such as missing critical fields. If the critical fields are missing, Mapper will create an error file that will contain those errored out records and the valid records will be mapped to a target XML format.Please refer to the video on how to apply exception handling rules in Mapper and then how to route the exception file in the process flow.

For more videos visit: https://adeptia.com/products/touranddemo.html

Situation:

I have approximately 65,000 records (a single string field) that i am creating into a CSV file. I have tested this by having the file dropped to a local folder via File Target. Now I am using the FTP Target to drop the same file on a third party companies SFTP folder. I am receiving a Java error after about 3800 or so records and only those get dropped into the SFTP folder.

Error: com.jscape.inet.sftp.SftpException: com.jscape.inet.sftp.FileService$OperationException: com.jscape.util.l.a.d

Cause:

The Connector type used by the FTP Target is incompatible with the FTP Server

Solution:

In the FTP Target advanced properties, select the connector type J2SSH

This video shows how easy it is to create and manage all of your HIPAA EDI Schemas to use in your conversions. Adeptia allows you to select a specific HIPAA Standard for a message type such as 837P and create a schema out of it which can then be used in reading or generating HIPAA messages.

Steps outlined in the video are documented here: Creating EDI Schema

Learn more about Adeptia's Healthcare Integration Solution. Here are additional useful links on HIPAA integration:

- Automating HIPAA Enrollments 834 with Payers

- Automating HIPAA data onboarding and processing

- Automating HIPAA 837 Claims clearance

For more informationcontact us at [email protected]

This video shows how easy it is to automate your HIPAA EDI transactions with your B2B trading partners via Events in Adeptia. You can setup Events to trigger inbound or outbound HIPAA transactions with your Payers or Providers. Dashboard provides full visibility on the status of the transactions, shows if there are errors in delivering the files.

Steps outlined in this video are documented here:

Configuring an inbound event

Configuring an outbound event

For more information about our solution, refer to Adeptia's Healthcare Integration Solution page.

This video shows how easy it is to create and manage your HIPAA EDI Data Standards in Adeptia for all of your HIPAA messages. Adeptia provides all the HIPAA data standards to its clients such as 834, 835, 837 etc.

Steps outlined in the video are also documented here: C reating and Managing EDI HIPAA Data Dictionaries.

Visit Adeptia's Healthcare Integration Solution page for more information.

This video shows how easy it is to create and manage your data mappings for your HIPAA EDI transactions that you are exchanging with your B2B using Adeptia.

Learn more about Adeptia's Healthcare Integration Solution. Here are additional useful links on HIPAA integration:

- Automating HIPAA Enrollments 834 with Payers

- Automating HIPAA data onboarding and processing

- Automating HIPAA 837 Claims clearance

HIPAA Integration Tutorial - Data Mapping from Adeptia, Inc. on Vimeo.

Error:

TestRequest_ProcessFlow is triggered as a WS Provider. The request is mapped and submitted to Test_DMS_WSConsumer where it fails with the below error:

Error in execution for activity WsMessageCall:Test_DMS_WSConsumer:172020200100134157815840200027 [The server sent HTTP status code 415: Cannot process the message because the content type 'application/soap+xml; charset=utf-8;action="test.org/IRequestProcessorServiceContract/ProcessRequest""' was not the expected type 'text/xml; charset=utf-8'.]

Cause:

The error is thrown when you try to hit a SOAP 1.1 service from a SOAP 1.2 WS activity.

Resolution:

The WSDL that you are using i.e. "DMS.wsdl" is a SOAP 1.2 service, but the end point (qaservices.test.com/DMS_Services/RequestProcessor.svc ) that service is trying to hit is SOAP 1.1 that results in this issue. To resolve this, try creating the WS consumer activity using URl option and provide the following WSDL URl qaservices.test.com/DMS_Services/RequestProcessor.svc?wsdl and after saving this try to hit the consumer again.

Refer to this short video on how to create a Web Service Consumer object and use it in the process flow. Example is here related to using Web Services with SAP IDoc.

For more videos visit: https://adeptia.com/products/touranddemo.html

Please refer to the attached document on steps of calling a WS Consumer in a process flow.

Here the scenario is that a source file is mapped to SOAP Input request and then the request is sent to a WS Consumer. The response of the Web Service is placed into a target folder.

A business process can be treated as service and can be made available to any application. The most interoperable way is to make it available as web service. Adeptia provides WsProvider to publish any business process as web service.Objective

This post describes the method of publishing a business process as a web service.

Tasks

1. Creating a process flow2. Creating a security policy (optional)3. Creating a WsProvider

Example Case:

You have a business process that takes the Auto Insurance Policy application and returns back the Policy Quote. You want to publish this process as a web service.

Solution

To publish the process as a web service, you need to design a process from perspective that it is similar to a function that takes input, processes it, and generates output. While designing, you need to remember:

- A Web service always takes input as XML data- A Web service always generates output as XML data

You need to define both XML data formats, the one that the web service will take as input and the format that the web service will generate as output. You can do this using the Adeptia XML schema activity. You need to define input and output XML schemas.

Creating process flow

Based on function analogy a process flow will have four parts:

1. Defining input and output XML schemas2. Getting input data from client request3. Data processing logic4. Sending output back as response to client

Defining Input and Output XML schemaYou need to use Adeptia XML schema activity to define XML schemas for input and output. To do that you need to define:

- The XSD for the input XML. For example, in given scenario you have an Auto Insurance Policy application as an input whose XML schema is defined in Appendix A.- The XSD for the output XML. For example, in given scenario the output generated is the Policy Quote.

Getting Input Data from Client RequestIn the process flow you need to use ContextSource as activity. You need to define a parameterName in the ContextSource property. Web service client input data will be assigned to this parameter. The context source will read it from this parameterName and pass the data to any further activity for data processing. This is displayed in the Figure below.

Data Processing logicThe input data is then processed to generate a required output. The data processing logic can include data transformation activity and other Adeptia activity or group of activities. To process the input data, it will use input XML schema activity. It will use output XML schema activity to generate output data in XML format. The output generated after processing the input data is set in the Process flow context through contextTarget.Sending Output back as response to clientIn the process flow, you need to use ContextTarget as activity. You need to define a parameterName. Web service client output data will be assigned to this parameterName. The ContextTarget will take data from the data processing activity and assign to the parameterName defined above. This is displayed in the Figure below.

In this example we will implement a QuoteGenerator web service that will be called by a web service client to obtain an insurance quote based on a request message.Thus a client will call this web service, send a quote request and in return get a quote from this web service.Step 1: Now let's make a process flow which will be published as a web service:

This flow will have three objects:

A. Context Source which will receive a request from a web service consumer

B. Data Mapping which will calculate a quote

C. Context Target which will store the quote response which will be sent to the web service client

Step 2:Once the Flow is created, go to Web Service > Provider > new. Refer to the image below related to Web Service Provider > Quote Provider Service. After saving this will generate WSDL file.

How to handle a web service response that uses pagination to divide the number of records in its result set.In the initial response you get from the web service, save the values of the fields that have TotalPages and the PageIndex in global variables. You need to do this in mapping. 1. In this example the web service response on the left has fields such as totalPages and pageIndex.

We create global variables where we set these two values in the context by using the set-context function. See example below. Refer to Help on how to create Global variables in mapper.

2. In the Process design, build a flow that has a decision node and activities as shown in the attached image.

3. Double click on the arrow labeled No and click on Edit button in the properties panel and use this logic in Java condition.

4. Now in the Get the next page result step you need to set the request where you get the data from next page.

StringBuffer buffer = new StringBuffer(); int index=Integer.parseInt(context.get("pageIndex")); >>>> this page index is pageindex+1 as done in the global variable of the previous map. buffer.append(""); buffer.append("<platformMsgs:searchMore

5. Rest of the steps are same as the flow before the decision node.

Attached is the document to use Web Services in Clustered Mode.

1) When defining a Web Service Provider (WSP), specifying a Security Provider simply indicates that Adeptia authentication is required to execute this WSP. Also, at this point, the user/pwd in the Security Provider are irrelevant.

Yes

2) The userid/pwd of the Security Policy are only used when the WSP is called by an Adeptia Web Service Consumer (WSC) activity.

Yes. Because attaching security policy to consumer is same as sending request message with security header

3) If a WSP specifies that a Security Policy is required, when a request is made to this WSP, the security credentials included in the SOAP Header are validated against the Adeptia User Database.

Yes

a. If the provided user credentials have Execute permission to the WSP, then the request will be executed

- Yes

b. If the provided user credentials do NOT have Execute permission to the WSP, a SOAP Fault message of java.lang.NullPointerException is returned.

- Yes. In future release we will generate user friendly message in this case.

c. If the provided user credentials are NOT a valid Adeptia user, a SOAP Fault message java.lang.Exception: Not a valid user is returned.

- Yes

Please refer to the attached PDF document to use Rest Service as provider.Note: Restart Kernel and Webrunner after placing the class file in the Custom classes folder.

To consume an external Web Service such as: http://www.restfulwebservices.net/wcf/WeatherForecastService.svc?wsdl Create a Web Service > ConsumerGive a Name of the activity, click URI and then select HTTP and paste the above URL.Click Next and then select the method names, service and port. Enter $Input and Output and click next and Save.

Also create a File Source and use the sample request as input:< ?xml version="1.0" encoding="utf-8"?>

<

ns:GetCitiesByCountry xmlns:ns="http://www.restfulwebservices.net/ServiceContracts/2008/01">

< ns:Country>Germany < /ns:Country>

< /ns:GetCitiesByCountry>Similarly create A File Target which will contain the response from the Web Service.Now open the Process Designer and create a flow as:Start > File Source > Web Service Consumer > File Target > End.

Go to Design > Process Flow and from the Manage page select the flow and click on Execute. You can view the output file for the response.

When upgrading from Adeptia v5.2 to Adeptia v5.3 using the patch, the default web service configuration is Axis. If you would like to change this to Metro, change the values in the web service configuration menu to false (screenshot).After the any change to this configuration, you will need to clear the browser cache to the ensure the change is reflected.

- Usually this change will need to be made when attempting to use SOAP 1.2- When using the full installation of v5.3, the default configuration is Metro

Situation: When using SOAP UI, there is a HTTP authentication property entitled "Authenticate Preemptively"

Authenticate Preemptively

Send Authentication headers with each request without first receiving an authentication challenge. This is a potential security hazard but will improve performance since only one request will be required for authenticated endpoints instead of two

If this property is unchecked then a property SMCHALLENGE=YES is set in the HTTP header cookie otherwise it is equal to NO .

The situation occurs when the client service doesnt require Preemptive Authentication (which means it requires SMCHALLENGE=YES in the cookie header), because Adeptia enforces Preemptive Authentication by default . Therefore you may receive a 403 Forbidden error (In other words, the server can be reached, but the server declined to allow access to the page) .

Solution:

1. Attach the security policy with Authentication credentials in WsConsumer activity 2. Turn on the Maintain Session property of the WsConsumer .

3. Create a custom plugin activity with following line of code :

import java.util.ArrayList;

ArrayList cookieList=new ArrayList ();

cookieList.add("SMCHALLENGE=YES");

context.put("Cookie",cookieList);

Place this custom plugin (Consume stream=false, Generate stream=false) as the first activity in the process flow .

In some cases, you may have to change the IP address of the Web Service Trigger.

Follow the steps below to set the Web Service trigger with correct IP:

1. Stop Adeptia Suite Services. 2. Go to /mnt/adeptiaData/AdeptiaSuite_5.2/AdeptiaServer-5.2/ServerKernel/wsdl directory. (Linux system, similar path for Windows)3. Open WsTrigger.wsdl file 4. Replace existing IP with the server IP and save the file. 5. Start Adeptia Suite Services.

Please find the attached pdf file that would guide you through usage and implementation of MTOM (Message Transmission Optimization Mechanism) by the help of which you can transmit attachments such as Images, X-Rays, Design Documents and Business Contracts using SOAP messages.

Situation: Promoting a web service from development to production.

Process: When creating a web service in Adeptia, the activity that is generated will have a target namespace and address that is associated with the environment that the activity. After migrating the web service from one environment to another, you'll have to allow the activity recognize the new environment and update the target namespace and address. To do this, all you have to do is:

1) Log into Adeptia with permissions to edit the web service

2) Configure > Services > Web Services > Provider

3) Select the migrated Web Service Provider and click edit

4) Without making any changes, click Save

5) Now your web service will have the correct target namespace and address

Question: I've set up the .xsd's for the web service but am unsure about how to generate a template xml to be submitted to the web service. Is there a tool in Adeptia that will do that?

Answer:

This can be achieved by following a few steps that are described below:

1) After the creation of WSProvider, download the corresponding WSDL or copy the link of WSDL URL.

To download the WSDL, go to Design->Web Services->Provider, a manage page will open. View and Download links will be display against the name of the Web Service Provider.

Use Download link to download the WSDL and View link to copy the WSDL URL.

3) Load the WSDL in any third party Web Service tool like SOAPUI and It will generate a Template XML for web service request.

While using WS Provider if you want to set the value for SOAPFaultStringandSOAPFaultDetailvariable. Then you can create the PutContext variable for these variables in the Process Flow designer of the Provider and can further use these .

Create a Put Context Var activity in which we will store the value for variable SOAPFaultStringandSOAPFaultDetail. The value for SOAPFaultStringcontains the error message and itshould be string and value forSOAPFaultDetailvariable should be a valid XML containing the code and message tags inside the root tag.

Structure of XML should be like below:

<root>

<code>Test Code</code>

<message>Test Message</message>

</root>

To configure PKCS12 type keyStore or trustStore in jetty, you need to modify jetty.xml file present inside \AdeptiaServer\ServerKernel\etc\jettyfolder. In jetty.xml, you have to define keyStore/trustStore type for sslContextFactory. Please refer the below example more details:

<New id="sslContextFactory" class="org.eclipse.jetty.http.ssl.SslContextFactory">

<Set name="KeyStore"><Property name="jetty.home" default="." />/etc/jetty/SSL_Keystore.jks</Set>

<Set name="KeyStorePassword">password</Set>

<Set name="KeyManagerPassword">password</Set>

<Set name="KeyStoreType">pkcs12</Set>

<Set name="trustStore"><Property name="jetty.home" default="." />/etc/jetty/SSL_Keystore.jks</Set>

<Set name="trustStorePassword">password</Set>

<Set name="TrustStoreType">pkcs12</Set>

</New>

Attached document explain how to extract the Base64encoded content from a file that you can use into request xml of a Web Service Consumer activity. To extract Base64encoded content from a file, you need to use a custom plugin. This document explains how to use the custom plugin for extracting the Base64encoded content from a file.

Please go through the attached Document for detailed instructions.

This document will provide you with information regarding how to read client certificate attributes in a process flow.

In this example we would show how to configure Web Service Consumer (REST) Service to call and get data from BambooHR.

BambooHR provides documentation on the various REST API operations available to get and post data into the cloud application. For example Get Table operation can be called to get a table of all the employees in your organization. Refer to http://www.bamboohr.com/api/documentation/tables.php#getTable

There are few parameters that need to addressed.

URL Endpint: For BambooHR the sample API endpoint ishttps://myCompany.bamboohr.com/api/gateway.php/myCompany/v1/employees/directory

This Endpoint (with getTable operation) when called would give us employee data

This is a Get operation

Security Policy to authenticate the request from Adeptia

So now let's get started on how to call a REST API by using Adeptia Integration Suite.

Step 1: If request authentication is required then Go to Develop > Services > Web Services > Security Policy and create a new security policy.

Security Policy may be a simple basic authentication where user has to provide a simple login and password or it may require an API KEY which is the case shown below. If authentication is not required then skip to Step 2.

Step 2: Configure a new Web Service Consumer activity by going to Develop > Services > Web Services > Consumer and click on create new.

Three main fields that need to be configured are

URL ishttps://myCompany.bamboohr.com/api/gateway.php/myCompany/v1/employees/directory

Method is "Get"

Security Policy created in the previous step is selected here

If any Key Value pairs are needed to be sent as the body of the call then you can add those parameters in the Parameter list.

Step 3: Configure an orchestration that would call and convert the REST API response into a CSV format.

Here I have created a process flow which has following steps (your process may be different based on your business needs).

Calls BambooHR web service and gets employee data

Maps the data into a CSV formatted report

Report is created by the specific text schema attached after the mapping step

Distribute the CSV file to end-users via Email target

After running the process you can view the logs and check the status as shown below.

Also refer to the attached deployable process flow to see how it is designed and configured. Use the Adeptia Migration Utility to deploy the flow into your local Adeptia instance.If you need help in designing a process flow please contact [email protected]

Adeptia repository files cleanup:Please find the attached custom plugin code and cleanup.sh file in order to clean the repository files.1. Copy the cleanup.sh file at any location on machine where the Adeptia Server is running.2. Change the following parameter in cleanup.sh file:

Give the path of repository folder in place of " /AdeptiaServer-4.9/ServerKernel/web/repository/".

Give the value of n in "-mtime +n -exec rm -rf". where n is the number of days for which you wants to retain the repository files.

3. Give the path of cleanup.sh file in Custom Plugin in p = rt.exec("/cleanup.sh");.4. Create and execute the Process Flow using this Custom Plugin. You may bind this flow with an event to delete the repository files on a regular interval.

Refer to the Attached PDF.

In some cases you may wish to customize which menu items are available per user type. You can control the menu link at user type level by editing the xml file \ServerKernel\etc\UserWorkspaceSpaceMenu.xml. In this example developers wouldnt see Administer/Connector. This would still allow the developers to use the DB connection info object in the DB schema provided they have read, execute rights. user type="developer" removemenu xpath="Administer/Connector" / /userUse the 'removemenu' property.

1. Go to Administer > Setup > Application Settings > Update System Properties>Systems>Applet Configuration >Data Mapper.2. Increase the value of property abpm.dataMapper.maxHeapSize to 1024M3. Save and click on Reload the configuration4. Restart the the Kernel and the Webrunner

Please find the attached document on how to setup J-Integra.As a prerequisite you need to purchase J-Integra Exchange license: http://j-integra.intrinsyc.com/download/default.aspx?ProductId=exchange

Follow the steps mentioned in the PDF attached.

Here are the changes that need to be done in jsl-Kernel.ini (present inside /ServerKernel/ folder) in order to allow Adeptia Kernel to pick up JVM arguments from launcher.properties in case Adeptia Server is running as window service:params = 4param00 = -cpparam01 = "/AdeptiaServer-4.9/ServerKernel/web\libs\BPMServer.jar;/AdeptiaServer-4.9/ServerKernel/etc/"param02 = com.adeptia.indigo.loader.ApplicationLauncherparam03 = KN 1The above parameters needs to be changed as:params = 5param00 = -cpparam01 = "/AdeptiaServer-4.9/ServerKernel/web\libs\BPMServer.jar;/AdeptiaServer-4.9/ServerKernel/etc/"param02 = com.adeptia.indigo.loader.ApplicationLauncherparam03 = KNparam04 = 1After making above changes in jsl-Kernel.ini and re-starting Adeptia Kernel as window service, JVM parameters are being picked up from launcher.properties.

Please follow the steps given below to allow System Monitor to be opened on a different IP address:1. Go to "Administer" > "Configure" > "Application Settings".2. At "Application Settings" page, click "Update System Properties" link.3. At "Update System Properties" page, expand "Web Server" section.4. Under Web Server section, there is a property: abpm.webserver.public.address. Give here the IP address of machine where the Adeptia Server is installed and save the properties. Now try to open the System Monitor applet.

To change the Logging level of event from INFO to DEBUG,please follow the steps below :1. Go to Administer > Setup > Application Settings > Update System Properties 2. Expand the Systems 3. Then in Systems expand Logging4. Update the property log4j.logger.Event 's value from INFO to DEBUG 5. Restart the Kernel and the Webrunner

Introduction

Using migration utility in Non Interactive Mode, you can export and import the objects from one environment to another environment, without any user intervention.

While exporting objects, the required parameters are parsed from the export.xml file. In export.xml you can define following parameters:

Adeptia Suite installation folder of the source environment

Location where you want to store the exported zip

Type of export. Process flow or activities or both

Projects whose objects you want to export

Groups whose objects you want to export

Solution database information.

List of activities that you want to export

List of process flows that you want to export

List of tables you want to export.

Folders and files that you want to export

Similarly while importing objects, the required parameters are parsed from import.xml file.

Adeptia Suite installation folder of the target environment.

Location of the exported zip.

Location of the retain xml file.

Id of the group, which will be the owner group of the imported objects in the target environment.

Id of the project, which will be the owner of the imported objects in the target environment.

Id of the user, which will be the owner of the imported objects in the target environment.

Solution tables connection parameter used to connect to solution database

In case any activity, which you are importing, already resides in the target environment, will be overridden from the activity being imported. You can define the type of activities (Service) that you want to be retained, in the retain.xml file. You can also retain a particular field of any service.

The full guide is available here - https://adeptia.com/migration-utility-non-interactive-mode-guide

This document explains how to point Adeptia Suite Kernel and Webrunner, which are running as windows service, to use 32 bit JRE instead of 64 bit JRE.

As a system "admin" you can change the owner of the activities by following these steps:

Log in as the Admin then expand the Administer category under the Administer and click on Setup > User.

In the Manage User screen, click the radio button against the user that you want to move and then click the Move link. Then "Select Activities" screen is displayed with the list of activities belongs to the user.

Select the required object(s) and their sub object(s) and click Move Objects button. The Change Ownership screen is displayed.

Select the user to whom the objects will be moved to, from the drop-down list and then click Get Group(s) button. The Select Group screen is displayed with Group(s), the selected User belongs.

Select the group the user belongs to and click Change Ownership button. A confirmation screen is displayed that the ownership of selected objects has been changed successfully.

Also refer to the Administrator Guide for more information.

Follow the attached document for instructions on migrating the default log database to PostGreSQL

The Adeptia application uses 21000 as the RMI port (not default 1099 port) and it is configurable through server-configure.properties.Port 1099 is used as default by Jetty JOTM and standard XA Data Source service. But if that port is already in use by any other application, then it automatically redirects to other port. Therefore to resolve the port binding issue, follow below steps:

Stop Adeptia Kernel and Web runner. Start another application that uses port 1099. Start Adeptia Kernel and Web runner. It will automatically redirect to another port as 1099 is already in use by another application. Please note that Adeptia Kernel and Web runner may take some time to get up as it needs to redirect to another port.

Adeptia uses the HSQL database for it's embedded back-end database. Within this database, all of the objects and activities you've created are stored. Since the HSQL database is java based, it is easily integrated with Adeptia and offers good performance at lower data volumes.

You can view the size of this database as the indigo.data file, located here: AdeptiaServer\ServerKernel\embeddedDb\db

In certain situations, your HSQL DB may grow fairly large. We have a couple recommendations for this situation:

Recommendation # 1:

The following property values can be changed in database property file to support large data file (for backend HSQL database, this change needs to be done in ServerKernel/embeddedDb/db/indigo.properties):

# initial value

hsqldb.cache_file_scale=2

# new value

hsqldb.cache_file_scale=8

Above change will allow storage of 8 GB in .data file. To apply the change to an existing database, database shall be shutdown first, then the property = value line above should be added to the .properties file before reopening the database.

Recommendation # 2:

Also you can DEFRAG the HSQL database periodically to reclaim any unused spaces in .data file, usually when the .data file has reached 250MB. For this, you need to use SQL statement SET CHECKPOINT DEFRAG <numeric value> in database script file (for backend HSQL database, this change needs to be done in ServerKernel/embeddedDb/db/indigo.script). The numeric value is the number of megabytes of recorded empty spaces in the .data file that would force a DEFRAG operation. Low values result in more frequent DEFRAG operations. A value of 0 indicates no automatic DEFRAG is performed. The default is 200 megabytes of lost space. For log size = 50 (set from property hsqldb.log_size in database property file, in our case this value is set to 50 in property file), the numeric value for checkpoint defrag shall be set to 10. So, here is the SQL statement that can be used:

SET CHECKPOINT DEFRAG 10

To apply the change to an existing database, database shall be shutdown first, then above SQL should be added to the .script file before reopening the database.

Steps to shrink any running HSQL database (to reclaim any unused spaces in .data file)::

1) Connect to the HSQL database through following url:

URL: jdbc:hsqldb:hsql://<<machine Name or machine IP>>:<<port number>>

User-id: sa

Password will be blank

Note:

- the default port for the HSQL backend database is 2476

- "Machine name or machine IP" is the name/IP where Adeptia Suite is running

2) Run the following command:

CHECKPOINT DEFRAG

This post explains how to enable the encryption of the SSL trust store and key store passwords, entered on the SSL Configuration page.

Follow these steps to encrypt the passwords:

1. Go to the folder AdeptiaServer/ServerKernel/etc.2. Open the server-configure.properties file in a text editor.3. Go to the SSL Configuration group and perform the following modification within the javax.net.ssl.trustStoreType property.

a. Add the attribute encrypt=y in the propertyb. Delete the password (see figure below)

4. Repeat the step above for the javax.net.ssl.keyStorePassword property.5. Now save the file6. Restart the Kernel and WebRunner.7. Log in into Adeptia Suite8. Go to Administer Setup Application Settings Update System Properties9. Now expand the Services SSL Configuration10. Give the value of password in TrustStore and Keystore

Note: Now the password will not be visible in this screen and will be stored in encrypted format.

11. Click Save and restart the Kernel and WebRunner to make the new password effective

Usually the Adeptia application logs, KernelApplication.log and WebrunnerApplication.log can be found here: \AdeptiaServer\ServerKernel\logs\applicationlogs.

In some cases, you may have directed the logs to be placed in a different location. To identify the location of these logs:

1) Please open \\AdeptiaServer\ServerKernel\etc\server-configure.properties file.

2) Search for "Kernel output file location" in the file and you will see the location where KernelApplication.log exists

3) Search for "Web Runner output file location" and you will see the location of WebrunnerApplication.log file.

This document describes the steps to create a new Keystore within Adeptia and configure the SSL signed certificate in Adeptia Suite V 5.2.

Adeptia Suite installation provides HSQL as the embedded log database. The HSQL database is recommended for evaluation purposes because it is lightweight. For development or production installations we strongly recommend having any other commercial database that is stable, scalable, and has its own features of database backup and restore.

This document provides steps to configure Adeptia HSQL log database to other supported database i.e. Sql Server/MySql/Oracle database.