Kony Quantum is now HCL Volt MX. See Revised Terminology. Current Quantum users, see the important note about API naming.
Release:
You are here: Hostname/Port changes for Tomcat Application Server
FAQs and Troubleshooting
This section lists the troubleshooting tips to resolve problems that you may encounter during installation.
Issue: If you have upgraded from Foundry V8.x or lower versions to V9 GA or higher versions, some of the services fail to work because of an internal authentication error. These services, such as the Foundry Admin Adapter, Email Adapter, and Workflow Email services, fail with the following error:
{
returned HTTP [400], Response Body [{"details":{"message":"Could not find trust security group for given envId","errcode":0,"errmsg":"Could not find trust security group for given envId"},"httpstatus":"Bad Request","requestid":"5e36d604-09ab-4fbb-9437-42c1d828140f;98","domain":"AUTH","code":-65,"mfcode":"Auth-65","message":"Some of the input parameters provided are invalid"}]
}
Workaround
To avoid the error, you must perform the following:
Log in to Foundry Console which you upgraded for V9.x.
In your Volt MX Foundry account, click Environments. The Environments page appears.
Click MODIFY for the environment. The Modify Environment page appears, shown below:
In the Modify Environment page, click SAVE.
Issue: While upgrading from Foundry 7.3 to Volt MX Foundry V9 and then upgrading to a version after V9, the upgrade fails due to the following error:”java.sql.SQLSyntaxErrorException: Table ‘prefixidglobaldbsuffix.schema_version’ doesn’t exist”.
Workaround
To avoid this issue, perform the following step:
Delete the idglobaldb schema before upgrading to the version later than V9.
Issue
The upgrade installation from v8.2.1.3 to v9.x rolls back.
Workaround
Before the upgrade, execute the following SQL statement from admin database:
For MySQL
-———–
delete from .schema\_version where script = 'V62.1\_\_voltmxadmin-mysql-8.2.0.0.sql';
For SQLServer
-————–
delete from .schema\_version where script = 'V62.1\_\_voltmxadmin-sqlserver-8.2.0.0.sql';
For Oracle
-———
delete from .schema\_version where script = 'V62.1\_\_voltmxadmin-oracle-8.2.0.0.sql';
Issue
If you upgrade the integration service or install on new server using the existing database but with a different server details like fully qualified URL port, and when you publish an app, the app publish fails.
Workaround
You must update management server details in the server_configuration table in admin database.
How to change the Hostname/IP address and port details of the existing Volt MX Foundry Server.
After the installation of Volt MX Foundry, if you want to change the existing Hostname/IP address that was used during the installation of Volt MX Foundry, follow these steps:
Go to your Volt MX Foundry install folder.
Go to scripts folder - for example, <MFinstallfolder>/scripts. The scripts folder contains a .sql file for the database type that you selected while installing Volt MX Foundry.
Open the .sql file in a text editor.
Important: If you want to access Volt MX Foundry Console with a new port, change the value for the NEW_PORT with the new value. Otherwise, assign the value of the OLD_PORT to the NEW_PORT variable.
Important: If you want to access Volt MX Foundry Console with a hostname/IP address, change the value for the NEW_HOST with the new value. Otherwise, assign the value of the OLD_HOST to the NEW_HOST variable.
Change the values for the following variables.
For MySQL, MariaDB, DB2, and SQL Server, replace the values for the NEW_HOST and the NEW_PORT with new values.
For Oracle, replace all the occurrences of the NEW_HOST and the NEW_PORT with new values.
Important: If you have selected your database as DB2, follow the steps provided in the .sql file in the <MFinstallfolder>/scripts folder.
Run the SQL script on the database where you have installed Volt MX Foundry.
Issue
If the java.sql. BatchUpdateException: Prepared statement needs to be re-prepared error is logged in the Identity service logs or if certain operations fail to work properly when an identity service is invoked, do the following.
Workaround
Add the following server variable in MariaDB ini file located in the MariaDB installation folder.
table_open_cache=64
Path for MariaDB ini file, <USER_INSTALL_DIR>\MariaDB 10.1\data\my.ini
Issue
If you face the error dialogue “Windows error 2 occurred while loading the Java VM” while launching the Volt MX Foundry Patch Installer, because of the following:
Volt MX Foundry Patch Installer runs with your system’s default Java. If an user machine has Java 8 installed, then check if the machine’s System Environment Path for Java or JAVA_HOME is set to c:\programdata\oracle\java\javapath
Workaround
Remove the current path from JAVA_HOME and set the new path as C:\Program Files (x86)\Java\jre1.8.0_40\bin
Launch the Volt MX Foundry Patch Installer.
After the installation completed, reset the machine’s System Environment Path for Java or JAVA_HOME path to it’s original path. For example c:\programdata\oracle\java\javapath
Issue
If your service provider’s certificate is not configured, the system displays an error - “peer not authenticated.”
Upgrading from Foundry 6.5.2, 7.0.1 or 7.1.1 with MS SQL Server fails. Installer is rolling back, as the schema version table is not migrating properly while upgrade.
Workaround
To avoid this issue, follow these step:
Remove the version_rank column from schema_version table in each schema by following queries before upgrade.
{
drop index schema_version_vr_idx on master..schema_version;
alter table master..schema_version drop column version_rank;
}
Issue
Auth (VoltMX Identity Service) datasources are not created when upgraded from Foundry 6.5.2.GA to 7.2.GA.
Workaround
Create datasource for authconfigdb and authglobaldb. For more details, refer to Configuring_JNDI_for_Database> Data Source for Single Node and Multinode > VoltMX Identity Service Data Source section.
Issue
If you have installed Foundry 7.3 or older, and when you use the existing database for Volt MX Foundry V8 on JBoss, the Web Application publish fails.
Workaround
Update the management_server_port in the server_configuration table of admindb with the jboss.management.http.port in the <USER_INSTALL_DIR>\jboss\standalone\configuration\standalone.xml.
Issue
If you do not want to use a DB user with DBA role or Equivalent privileges for the Volt MX Foundry installation on ORACLE database, follow these steps:
Workaround
Manual Steps:
Create Component Users (schema) with the required grants as below.
{
CREATE USER MFCONSOLEDB identified by default tablespace profile default;
ALTER USER MFCONSOLEDB QUOTA UNLIMITED ON USERS;
GRANT CONNECT,RESOURCE,CREATE VIEW TO MFCONSOLEDB;
GRANT CREATE JOB TO MFCONSOLEDB;
GRANT MANAGE SCHEDULER TO MFCONSOLEDB;
CREATE USER MFACCOUNTSDB identified by default tablespace profile default;
ALTER USER MFACCOUNTSDB QUOTA UNLIMITED ON USERS;
GRANT CONNECT,RESOURCE,CREATE VIEW TO MFACCOUNTSDB;
GRANT CREATE JOB TO MFACCOUNTSDB;
GRANT MANAGE SCHEDULER TO MFACCOUNTSDB;
CREATE USER MFREPORTSDB identified by default tablespace profile default;
ALTER USER MFREPORTSDB QUOTA UNLIMITED ON USERS;
GRANT CONNECT,RESOURCE,CREATE VIEW TO MFREPORTSDB;
GRANT CREATE JOB TO MFREPORTSDB;
GRANT MANAGE SCHEDULER TO MFREPORTSDB;
CREATE USER IDCONFIGDB identified by default tablespace profile default;
ALTER USER IDCONFIGDB QUOTA UNLIMITED ON USERS;
GRANT CONNECT,RESOURCE,CREATE VIEW TO IDCONFIGDB;
GRANT CREATE JOB TO IDCONFIGDB;
GRANT MANAGE SCHEDULER TO IDCONFIGDB;
GRANT CREATE TABLE TO IDCONFIGDB;
GRANT CREATE ANY INDEX TO IDCONFIGDB;
GRANT ALTER ANY TABLE TO IDCONFIGDB;
CREATE USER ADMINDB identified by default tablespace profile default;
ALTER USER ADMINDB QUOTA UNLIMITED ON USERS;
GRANT CONNECT,RESOURCE,CREATE VIEW TO ADMINDB;
GRANT CREATE JOB TO ADMINDB;
GRANT MANAGE SCHEDULER TO ADMINDB;
CREATE USER VPNSDB identified by default tablespace profile default;
ALTER USER VPNSDB QUOTA UNLIMITED ON USERS;
GRANT CONNECT,RESOURCE,CREATE VIEW TO VPNSDB;
GRANT CREATE JOB TO VPNSDB;
GRANT MANAGE SCHEDULER TO VPNSDB;
}</code></pre></figure>
Create a non DBA user with the below grants. This user will be given to the Installer.
{
CREATE USER <INSTALLER\_USER> IDENTIFIED BY ;
GRANT CREATE SESSION TO <INSTALLER\_USER> WITH ADMIN OPTION;
GRANT SELECT ANY DICTIONARY TO <INSTALLER\_USER>;
ALTER USER <INSTALLER\_USER> QUOTA UNLIMITED ON ;
ALTER USER <INSTALLER\_USER> QUOTA UNLIMITED ON ;
ALTER USER <INSTALLER\_USER> QUOTA UNLIMITED ON ;
}</code></pre></figure>
Note: The password for the component users and the installer user have to be same.
Issue
For storage services to work, change the following storagedb entries in the admindb.
Workaround
Manual Steps:
{
storage\_database\_type - oracle
storage\_database\_hostname - Database hostname/IP
storage\_database\_port - Database Port
storage\_database\_username - DBA username
storage\_database\_password - DBA Password
storage\_database\_instance - service ID/service name
storage\_data\_tablespace - Data Tablespace name
storage\_index\_tablespace - Index Tablespace name
storage\_lob\_tablespace - Lob Tablespace name
}
Issue
If you do not want to use a DB user with DBA role or Equivalent privileges for the Volt MX Foundry installation on MSSQL, follow these steps:
Workaround
Manual Steps:
<pre>
Create database mfreportsdb;
Create database mfaccountsdb;
Create database mfconsoledb;
Create database admindb;
Create database vpnsdb;
Create database idconfigdb;
CREATE LOGIN loginId WITH PASSWORD = 'loginpwd'
GO
use msdb
GO
create user userId from LOGIN loginId;
GO
EXEC sp\_addrolemember 'SQLAgentUserRole', 'userId'
EXEC sp\_addrolemember 'SQLAgentReaderRole', 'userId'
EXEC sp\_addrolemember 'SQLAgentOperatorRole', 'userId'
GO
use mfreportsdbAN
GO
create user userId from LOGIN loginId;
GO
GRANT ALTER ANY DATABASE DDL TRIGGER TO userId
GO
GRANT CREATE TABLE,CREATE TYPE,CREATE PROCEDURE,SELECT,UPDATE,DELETE,INSERT,EXECUTE,REFERENCES,CREATE VIEW,ALTER,VIEW Definition TO userId
GO
use mfaccountsdb
GO
create user userId from LOGIN loginId;
GO
GRANT ALTER ANY DATABASE DDL TRIGGER TO userId
GO
GRANT CREATE TABLE,CREATE TYPE,CREATE PROCEDURE,SELECT,UPDATE,DELETE,INSERT,EXECUTE,REFERENCES,CREATE VIEW,ALTER,VIEW Definition TO userId
GO
use mfconsoledb
GO
create user userId from LOGIN loginId;
GO
GRANT ALTER ANY DATABASE DDL TRIGGER TO userId
GO
GRANT CREATE TABLE,CREATE TYPE,CREATE PROCEDURE,SELECT,UPDATE,DELETE,INSERT,EXECUTE,REFERENCES,CREATE VIEW,ALTER,VIEW Definition TO userId
GO
use admindb
GO
create user userId from LOGIN loginId;
GO
GRANT CREATE TABLE,CREATE TYPE,CREATE PROCEDURE,SELECT,UPDATE,DELETE,INSERT,EXECUTE,REFERENCES,CREATE VIEW,ALTER TO userId
GO
use vpnsdb
GO
CREATE SCHEMA vpnsdb;
GO
create user userId from LOGIN loginId;
GO
GRANT CREATE TABLE,CREATE TYPE,CREATE PROCEDURE,SELECT,UPDATE,DELETE,INSERT,EXECUTE,REFERENCES,CREATE VIEW,ALTER TO userId
GO
use idconfigdb
GO
create user userId from LOGIN loginId;
GO
GRANT CREATE TABLE,CREATE TYPE,CREATE PROCEDURE,SELECT,UPDATE,DELETE,INSERT,EXECUTE,REFERENCES,CREATE VIEW,ALTER TO userId
GO
</code></pre></figure>
Note: The whole script must be run at once.
Note: The loginId and password must be the same as used for Volt MX Foundry Installation.
Note: The and provided must be the same across the script and must also be provided at the time of the Volt MX foundry Installation.
Note: You can use the same loginId and userId to avoid confusion.
Note: The userId must be same across the script.
Issue
If you do not want to use a DB user with DBA role or Equivalent privileges for the Volt MX Foundry installation on IBM DB2, follow these steps:
Workaround
Manual Steps:
Important: Only DB2 database administrator (DBA) or equivalent DB user will have access to a create database.
Create a user based on your Operating System level.
{
GRANT CREATEIN,ALTERIN,DROPIN ON SCHEMA ADMINDB TO userid;
GRANT CREATEIN,ALTERIN,DROPIN ON SCHEMA MFCONSOLEDB<suffix TO userid;
GRANT CREATEIN,ALTERIN,DROPIN ON SCHEMA MFACCOUNTSDB TO userid;
GRANT CREATEIN,ALTERIN,DROPIN ON SCHEMA MFREPORTSDB TO userid;
GRANT CREATEIN,ALTERIN,DROPIN ON SCHEMA VPNSDB TO userid;
GRANT CREATEIN,ALTERIN,DROPIN ON SCHEMA IDCONFIGDB TO userid;
}
Grant schema level permissions to the user:
{
GRANT createtab,CONNECT,DATAACCESS,IMPLICIT\_SCHEMA,ACCESSCTRL ON database TO USER userid;
}
Note: The loginId and password must be the same as used for Volt MX Foundry Installation.
Note: The and provided must be the same across the script and must also be provided at the time of the Volt MX foundry Installation.
Issue
After entering Database details the DB connection fails with the following error:
Workaround
The password used for the Database must not contain exclamation marks (!).
Issue
If you are using any lower versions of MySQL 5.7 such as v5.7.12 or lower during installation, you may encounter an error due to which the installation rolls back. This error occurs due to a bug in the MySQL database.
For more information, refer MySQL Bugs
Hostname/Port changes for Tomcat Application Server
Volt MX Foundry On-Premises Installer provides a script to change the Hostname or Port of the installed Volt MX Foundry instance. In your installed Tomcat Application Server, you must also perform the following changes:
In //tomcat/webapps/apiportal/WEB-INF/classes/config.properties, replace the existing URL with the new URL in the following fields:
VOLTMX_ACCOUNT_API_BASE_URL=
VOLTMX_DEVELOPER_PORTAL_BASE_URL=
In //tomcat/webapps/mfconsole/WEB-INF/classes/config.properties, replace the existing URL with the new URL in the VOLTMX_ACCOUNT_API_BASE_URL= field.
In //tomcat/conf/server.xml, replace the port number with the new port number in the <Connector server="VoltMX" port= field.
In //tomcat/webapps/accounts/WEB-INF/classes/accounts.properties, replace the port number with the new port number in the following fields:
VOLTMX_INTEGRATION_SERVICE_PORT=
VOLTMX_MESSAGING_SERVICE_PORT=
Hostname/Port changes for JBoss Application Server
Volt MX Foundry On-Premises Installer provides a script to change the Hostname or Port of the installed Volt MX Foundry instance. The script can be found in the installation folder. In your installed JBoss Application Server, you must follow the instructions in the script and also perform the following steps:
In the standalone.xml file replace the IP address/port number with the new IP address/port number.
In mfconsole.war\WEB-INF\classes\config.properties, replace the existing URL with the new URL in the VOLTMX_ACCOUNT_API_BASE_URL= field.
In apiportal.war\WEB-INF\classes\config.properties, replace the existing URL with the new URL in the following fields:
VOLTMX_ACCOUNT_API_BASE_URL=
VOLTMX_DEVELOPER_PORTAL_BASE_URL=
In accounts.war\WEB-INF\classes\accounts.properties, replace the port number with the new port number in the VOLTMX_INTEGRATION_SERVICE_PORT= field.
When an administrator installs only integration services on Weblogic and would like to use it as a standalone server (without integrating to Volt MX Foundry) for Volt MX Studio apps, then app services which use custom code for pre-processor and post-processor will fail. For these services to work properly, add the custom code jar file to middleware.war and redeploy.
To add custom jar to middleware.war after installation, follow these steps:
Uninstall the middleware.war file from WebLogic Console > Deployments tab.
Go to your Volt MX Integration Server install location and Deployments folder.
Open the middleware.war file and do the following:
In the middleware.war file, go to WEB-INF/lib folder and add custom jar file.
Save the middleware.war file.
Deploy the middleware.war file back to server.
How to Configure Heap and PermGen Size
Configuring Heap and PermGen Size for Tomcat
By default, the heap settings for Tomcat allocated are Min -Xms1024m / Max - Xmx2048m, and default permgen settings are: -XX:PermSize=1024m -XX:MaxPermSize=1024m
For better performance in case of several publishes, update the following heap and permgen settings in the file: {Installation directory}/tomcat/bin/catalina.sh
heap settings: Min -Xms1024m / Max - Xmx1024m.
Important: While installing Volt MX Foundry Components including Integration services, set the heap settings to: Min -Xms2048m / Max - Xmx2048m.
Go to the {Server directory}/user_projects/domains/bin/ folder, and open the setDomainEnv.sh file in a text editor.
Search for the following comment line:
\# IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
Immediately after the comment line, add the following line:
export USER_MEM_ARGS="-Xms6144m -Xmx6144m"
Save the file, and then restart the WebLogic Server.
How to Configure Volt MX Foundry Behind a Reverse Proxy
If you want to access everything via a proxy URL, including Volt MX Foundry Console (for example, design time for your app developers) and authService, and integration services (for example, runtime from users using your apps), follow these steps:
Install Volt MX Foundry with internal details like your internal IP and HTTP port.
After installation, stop the Volt MX Foundry Console (without configuring authservice details) and update following property files:
In the accounts.war/WEB-INF/classes folder, open the accounts.properties file, and update the WAAS_BASE_URL=<PUBLIC_URL_OF_YOUR_APACHE>/workspace property with a public URL instead of the private URL. By default, the private URL is set during installation.
Following are the changes to be made in the war for each App Server:
Tomcat: In mfconsole.war/WEB-INF/classes, open the config.properties file, and update the VOLTMX_ACCOUNT_API_BASE_URL=<PUBLIC_URL_OF_YOUR_APACHE>/accounts/api/v1_0/ property with a public URL instead of the private URL that was generated during installation.
JBoss - Standalone (Bundled JBoss): In Standalone/deployments/mfconsole.war, open the config.properties file, and update the VOLTMX_ACCOUNT_API_BASE_URL=<PUBLIC_URL_OF_YOUR_APACHE>/accounts/api/v1_0/ property with a public URL instead of the private URL that was generated during installation.
JBoss - Pre-configured and Domain mode: Take a backup of the existing war. Undeploy mfconsole.war. In mfconsole.war/WEB-INF/classes, open the config.properties file, update the VOLTMX_ACCOUNT_API_BASE_URL=<PUBLIC_URL_OF_YOUR_APACHE>/accounts/api/v1_0/ property with a public URL instead of the private URL that was generated during installation, and re-deploy the war file.
WebLogic: In mfconsole.war/WEB-INF/classes, open the config.properties file, and update the VOLTMX_ACCOUNT_API_BASE_URL=<PUBLIC_URL_OF_YOUR_APACHE>/accounts/api/v1_0/ property with a public URL instead of the private URL that was generated during installation.
Start Volt MX Foundry Console.
Launch your Volt MX Foundry Console in browser by using <PUBLIC_URL_OF_YOUR_APACHE>/mfconsole. Now auth setup pages comes up.
Enter auth URL with public URL like <PUBLIC_URL_OF_YOUR_APACHE>/authService. If you provide an internal IP here, appconfig will show internal IPs.
Also after log in to Volt MX Foundry Console, while registering server, provide the PUBLIC_URL to register integration server. Now all the URLs will have the public hostnames.
If you want to give public access only to runtime services like authservice and integration services you can skip step 2 and step 3 from the above procedure. This will make sure service doc will have all public URLs.
Note: Proxy configuration should have preserver host directive for Volt MX Foundry to work correctly after start up.
For example, in case of apache proxy, use `ProxyPreserveHost On`
and in case of NGINX, use proxy_set_header Host $host; (For more information, refer Passing request headers)
How to Configure Frontend HTTPS to Tomcat HTTP Redirection
If you are installing Volt MX Foundry on Tomcat on HTTP and wants to route requests via HTTPS apache or loadbalancer, add a connector in the tomcat/server.xml with the following attributes:
