Jump to: navigation, search

Java_Database_Connectivity

Also known as JDBC. A Java Application Programming Interface (API) that enables Java programs to execute SQL statements.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Deploying Advisors Platform

You run a .jar installation file to deploy Advisors Platform. Use the procedure below to start your installation. The installer guides you through the deployment. The screens displayed during your deployment are dependent on the selections you make on the Module to Install screen. Information about each screen is available on the Installation Screens tab below.

You can deploy Advisors Platform on a Red Hat Linux or a Windows platform, and with Oracle or MS SQL databases.

Important
New3.png In release 9.0, there are changes to the installation wizard screens; therefore, you cannot reuse your previous setup for silent installation or any saved ant.install.properties file.

Deployment Roadmap

The arrow icon in the following roadmap indicates where you are in the Advisors deployment process.

  1. [+] Install the databases that correspond to the Advisors products you will deploy.
  2. Create the Advisors User account in Genesys Configuration Server.
  3. Pma you-are-here-arrow.png Install the Platform service on servers where it is required for Advisors components. The Platform service is a prerequisite for installing the following components:
    • Advisors Administration
    • Advisors Web Services
    • WA Server
    • FA Server with rollup engine
    • CCAdv/WA/FA Accessibility services
    • CCAdv/WA Resource Management Console
  4. Install each adapter that you will use and configure the adapter Application objects with Stat Server connections.
  5. [+] Install the Advisors components for your enterprise.
  6. Make any required configuration changes.

Deploying the Advisors Platform Application

Procedure:


Steps

  1. Launch the installation file.
    [+] Show Steps for Linux
    [+] Show Step for Windows
  2. Use the Next and Back buttons on the installer to navigate through the installation screens. Enter your information on each screen. Use the information provided in the Installer Screens section on this page to complete the remaining deployment screens. Ensure you provide complete information on each screen.
  3. On the final screen, click Install.
    If errors display, diagnose them in the Errors tab, or refer to the Troubleshooting tab on this page.
  4. If you use a Windows platform, install the Advisors windows service as follows. Do this only for Advisors servers that are not controlled by Solution Control Server (SCS). For the list of servers that are not controlled by SCS, see Integration with Solution Control Server.

    [+] Show Steps

    If you use a Linux platform, validate that the Advisors Platform component installed successfully, and then configure Advisors Platform to run automatically as a system service. Do this only for Advisors servers that are not controlled by Solution Control Server. For the list of servers that are not controlled by SCS, see Integration with Solution Control Server.

    [+] Show Steps

Installation Screens


[+] Authentication Options
[+] Administration Configuration - CCAdv XMLGen
[+] Administration Configuration - SC Server
[+] Backup Config Server
[+] Cache Configuration
[+] Cluster Node Configuration
[+] Destination Directory
[+] Genesys Advisors Platform Database
[+] Genesys Advisors Platform Database - Advanced
[+] Genesys Config Server Connection Details
[+] Genesys Pulse Integration
[+] Java Development Kit
[+] Language Options
[+] Log Files Directory
[+] Mail Service Configuration
[+] Metric Graphing Database
[+] Metric Graphing Database - Advanced
[+] Modules to Install
[+] Oracle JDBC Driver
[+] Password Management Options
[+] RDBMS Type And JDBC Connectivity
[+] Tomcat Configuration
[+] User Management Options

Troubleshooting

The following Table shows parameter validation errors that you may encounter at the end of installation.

Installation Error Message Cause
[echo] Setting up cluster member configuration for this node

[java] Connecting to database: inf-wolf.us.int.genesyslab.com;oracle:1521;DatabaseName=orcl;user=yevgeny_plt_81 ...
[java] updating node: KoolNode ipAddress: 138.120.xx.xx localhost: localhost
[java] java.sql.SQLException: ORA-01013: user requested cancel of current operation
[java] at oracle.jdbc.driver.Database Error.throwSqlException(DatabaseError.java:112)
[java] at oracle.jdbc.driver.T4CTTIoer.process Error(T4CTTIoer.java:331)
[java] at oracle.jdbc.driver.T4CTTIoer.process Error(T4CTTIoer.java:288)
[java] at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
[java] at oracle.jdbc.driver.T4CPreparedStatement. doOall8(T4CPreparedStatement.java:219)
[java] at oracle.jdbc.driver.T4CPreparedStatement. executeForRows(T4CPreparedStatement.java:970)
[java] at oracle.jdbc.driver.OracleStatement. doExecuteWithTimeout(OracleStatement.java:1190)
[java] at oracle.jdbc.driver.OraclePreparedStatement. executeInternal(OraclePreparedStatement.java:3370)
[java] at oracle.jdbc.driver.OraclePreparedStatement. executeUpdate(OraclePreparedStatement.java:3454)
[java] at com.informiam.installer.DAO.executeTimedOutUpdate (DAO.java:214)
[java] at com.informiam.installer.ConfigureClusterMember. performActivities(ConfigureClusterMember.java:60)
[java] at com.informiam.installer.AbstractDatabaseUtility. doMain(AbstractDatabaseUtility.java:56)
[java] at com.informiam.installer.ConfigureClusterMember. main(ConfigureClusterMember.java:34)

This type of error may happen when the installer attempts to update a table which is locked by a not-committed transaction (usually with Oracle database).

The wording of the error may differ, but the key phrase to look for is ORA-01013: user requested cancel of current operation.
Typically this could happen with an Oracle database when someone runs a query such as DELETE FROM <TABLE_NAME> without then executing COMMIT; and the installer tries to update the same table.
In this case, the installer will wait for 20 seconds and fail with an error similar to the above. To correct this, execute COMMIT; after the DELETE statement and re-run the installer. To prevent this situation, always run COMMIT; when manually updating tables in Oracle.

[java] Failed to connect to the database using connection URL:

[java]
jdbc:sqlserver://192.168.xx.yy:nnn;DatabaseName=ys_pldb;user=sa;
password=very_secure_pwd;selectMethod=cursor
[java] The following exception was thrown:
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 192.168.xx.yy, port nnn has failed. Error: "Connection refused. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.

Wrong database server name / IP address or port number
[java] Failed to connect to the database using connection URL:

[java]
jdbc:sqlserver://192.168.xx.yy:nnnn;DatabaseName=NotAPlatformDB;selectMethod=cursor;
user=sa;password=very_secure_pwd
[java] The following exception was thrown:
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 192.168.xx.yy, port nnnn has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port."

Wrong database name
[java] Exception while connecting: Login failed for user 'badUserId'.

[java] url used:
jdbc:sqlserver://192.168.xx.yy:nnnn;DatabaseName=ys_pldb;selectMethod=cursor;
user=badUserId;password=very_secure_password

Wrong database user name or password
[echo] pinging cluster node IP address 138.120.yy.zz...


[java] WARNING! Host 138.120.yy.zz is unknown - java.net.UnknownHostException: 138.120.yy.zz. This may be due to a firewall blocking requests or a specific server configuration, e.g.: permissions.

[java] ERROR! Host 138.120.yy.zz is unknown - java.net.UnknownHostException: 138.120.yy.zz. This may be due to a firewall blocking requests or a specific server configuration, e.g.: permissions.

[java] Exception in thread "main" java.security.InvalidParameterException: Host 138.120.yy.zz is unknown - java.net.UnknownHostException: 138.120.yy.zz. This may be due to a firewall blocking requests or a specific server configuration, e.g.: permissions.

The cluster member node identified by the IP address specified is not reachable. This may be for one of the following reasons:
  • The host is not online
  • A firewall is blocking access to the host
  • The IP address of the host is incorrect
  • The host is configured to not respond to ICMP ping requests
Apr 11, 2011 3:53:46 PM oracle.jdbc.driver.OracleDriver registerMBeans

WARNING: Error while registering Oracle JDBC Diagnosability MBean.
java.security.AccessControlException: access denied (javax.management.MBeanTrustPermission register)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.checkMBeanTrust
Permission(Unknown Source)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(Unknown Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(Unknown Source)
at oracle.jdbc.driver.OracleDriver.registerMBeans(OracleDriver.java:360)
at oracle.jdbc.driver.OracleDriver$1.run(OracleDriver.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.jdbc.driver.OracleDriver.<clinit>(OracleDriver.java:195)

Produced in error and can be ignored.

Displays in the Errors tab when installing Platform with Oracle JDBC driver ojdbc6-11.2.0.2.0, and accurately reports that installation was successful.

Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: 32

at sun.font.FontDesignMetrics.charsWidth(Unknown Source)
at javax.swing.text.Utilities.getTabbedTextOffset(Unknown Source)
at javax.swing.text.Utilities.getTabbedTextOffset(Unknown Source)
at javax.swing.text.Utilities.getTabbedTextOffset(Unknown Source)
at javax.swing.text.PlainView.viewToModel(Unknown Source)
at javax.swing.text.FieldView.viewToModel(Unknown Source)
at javax.swing.plaf.basic.BasicTextUI$RootView.viewToModel(Unknown Source)
at javax.swing.plaf.basic.BasicTextUI.viewToModel(Unknown Source)

Produced in error and can be ignored.
[loadfile] Unable to load file: java.io.FileNotFoundException: C:\ (The system cannot find the path specified) Produced in error and can be ignored.
java.sql.SQLRecoverableException: IO Error: Connection reset Related to the operation of the Oracle JDBC driver. Use the following workaround.

Edit the <jdk>/jre/lib/security/java.security file:
Change securerandom.source=file:/dev/urandom to securerandom.source=file:///dev/urandom.

The installer fails or gives the following error message:

Caused by: java.security.AccessControlException: access denied ("javax.management.MBeanTrustPermission" "register")

To correct this error, go to the Java installation that is specified in the path included in the error message, or the Java installation defined as JAVA_HOME.

To the java.policy file under jre/lib/security, add the following to the granted permissions:
permission java.util.PropertyPermission "javax.management.MBeanTrustPermission", "register"

New3.png C:\Users\<USERNAME>\AppData\Local\Temp\antinstall\ build.xml:189: The following error occurred while executing this line:

C:\Users\<USERNAME>\AppData\Local\Temp\antinstall\ installer-common.xml:468: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:4061) ...

Ensure that you are launching the installer with Java JDK version 1.8. You can type java --version in a Windows command prompt window or in the Linux terminal to see which version is currently configured on your system. If you are using a Windows OS, add the Java JDK 1.8 folder path to both JAVA_HOME and PATH in environment variables. If you use Red Hat Enterprise Linux, add the Java JDK 1.8 folder path to the PATH variable.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on October 11, 2018, at 11:24.