Thursday, 27 January 2011

Opalis 6.3 Operator Console Installation Utility

Always one to find the easiest way possible to do things, I thought I'd quickly mention this post from the Opalis Blog:
http://blogs.technet.com/b/opalis/archive/2011/01/26/new-utility-to-automate-the-installation-of-the-opalis-ops-console.aspx

A new utility has been released by Kelverion that automates the entire installation of the Opalis 6.3 operator console by removing all of the complexity of the install and making it very simple and quick to get up and running.

More details of the util can be found here

You can watch a demo of the util here

And finally you can register for the download here.  It's free but you need to fill out a quick form first to get the download link e-mailed to you.

1 comment:

DBT said...

Thanks for this, it's a great utility as I was unavailable to find all of the required pre-reqs for download - what with Orchestrator now releasing RC I'm guessing it'll be harder and harder to find support for 6.3.

I'm just rolling out a new installation, but I can't logon to the Operator console - can anyone help.

When logging in with an account that's a member of the security group we configured for access to the console I receive the message that "The username and password entered are not correct. Transaction failed"

When checking server.log in the JBoss folder I find:-




2011-11-02 15:01:05,949 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null

org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect)

We are using a cname alias configured in DNS to connect to the SQL server on a non-standard port. I have tried various configurations, by manually modifying the opalis-ds.xml file in the 'deploy' folder including both the cname and actual hostname (with and without fqdn) with a ,portnumber but still we see the same error.