Jump to: navigation, search

Deploying Advisors Platform

You run a .jar installation file to deploy Advisors Platform.

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

Roadmap


  1. [+] Install the databases that correspond to the Advisors products you will deploy.
  2. Create the Advisors User and the Object Configuration User in Configuration Server.
  3. Pma you-are-here-arrow.png Install the Platform service (Geronimo) on all servers on which you will deploy one of the Advisors components.
    • Contact Center Advisor
    • Workforce Advisor
    • Frontline Advisor
    • Contact Center Advisor–Mobile Edition
    • Resource Management Console
  4. Install each adapter you will use (AGA and ACA).
  5. [+] Install the Advisors components for your enterprise.
  6. Make any required configuration changes.

1. If you are deploying Advisors platform on a Linux system, you must first create the Advisors group and user. The Advisors Platform is run as the advisors user, which belongs to the advisors group.
[+] Show Steps
2. Install Oracle Java Development Kit (JDK).
[+] Help with Linux environments
3. Place the advisors-platform-installer-<version>.jar file into the Advisors home directory.
[+] Show additional information for Linux environments
4. Launch the installation file.
[+] Show Steps for Linux
[+] Show Step for Windows
5. On the Module to Install screen, install the Administration workbench, if required.
[+] Show Important Notes
6. On the Languages for E-mail Templates screen, specify the languages to use in e-mail templates.
[+] Show Notes

7. On the Destination Directory screen, specify the directory for your Advisors installation.

[+] Show Notes
8. On the Java Development Kit screen, enter or select the root directory of the Java Development Kit (JDK).
9. On the Application Server Configuration screen enter the port numbers that the Geronimo application server will use. If you are installing only one deployment of Advisors, then accept the defaults that the installer offers.
Important
If you install Advisors on Linux and need to change the naming port, update the Advisors Platform service startup script as specified in Step 18.
10. On the Cluster Node configuration screen, configure the Advisors Platform installation as a unique node in the cluster. Each server on which you install Advisors Platform requires a unique cluster node ID. On this screen you also enter the port number that nodes in this cluster use to communicate.
[+] Show Notes
11. New3.png On the Cache Configuration screen, specify the port to be used by the distributed cache for communication. If you are installing only one deployment of Advisors, accept the default that the installer offers.

The port number must be unique to this deployment of Advisors. All nodes in one cluster must use the same port number.

12. On the Genesys Config Server Connection Details screen, configure the connection to the Genesys Configuration Server.
[+] Show Notes
13. On the CCAdv/WFAdv Object Configuration User screen, enter the name of the Object Configuration User account (configured in Configuration Server). You must enter this information if you use a Genesys data source and will be deploying Contact Center Advisor/Workforce Advisor (CCAdv/WA). This is not applicable on a Platform installation if CCAdv/WA is deployed with only Cisco data sources, or if you intend to deploy only Frontline Advisor (FA).
[+] Show Notes
14. On the User Management Options screen, configure options associated with user activities.
[+] Show Steps
15. On the Database Type screen, select either the SQL Server or the Oracle option – whichever you use for Advisors platform database(s). The screens that follow are dependent on your selection:
[+] Show Step for SQL Server
[+] Show Steps for Oracle
[+] Show Steps for Oracle RAC
16. On the Mail Service Configuration screen, specify the e-mail settings that the Forgot Password functionality will use to send e-mail.
  • SMTP Server—The SMTP service to use.
  • Application from address—The sender of this e-mail; for example, DO-NOT-REPLY@genesys.com.
  • Application to address—The recipient of this e-mail; for example, admin@genesys.com.
17. Click Install.

If errors display, diagnose them in the Errors tab, or refer to the Troubleshooting tab on this page.

18. If you use a Windows platform, install the Advisors windows service as follows:

[+] Show Steps

If you use a Linux platform, validate that Advisors Platform installed successfully and then configure Advisors Platform to run automatically as a system service:

[+] Show Steps
19. If you are running Platform with a 64-bit JVM, Genesys recommends that you increase your Geronimo PermGen memory settings.

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.
New3.pngjava.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.

This page was last modified on August 24, 2018, at 07:00.

Feedback

Comment on this article:

blog comments powered by Disqus