Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

 
Advanced search

486 Posts in 148 Topics- by 530 Members - Latest Member: StWammes

September 03, 2010, 06:44:10 PM
RES Software User Group ForumProductsOrchestration Pack for WisdomFixing comms problem between PowerFuse and ORpack
Pages: [1]
Print
Author Topic: Fixing comms problem between PowerFuse and ORpack  (Read 636 times)
RESguru
RESUG Forum Moderator
Jr. Member
***
Posts: 62



WWW
« on: January 07, 2010, 11:49:21 AM »

Hi all.
For those of you who are testing the EAP release 2.9.4.7 of Orchestration Pack for Wisdom, here's an interesting tidbit. I ran into the problem, that I was trying to hook PowerFuse 2010 IR3 into the Orchestration Catalog host. This is done in the Setup|Integration|RES Wisdom|Enable Orchestration integration subsection.

I would get situation that:

a) when hitting the Test button, it would come up with a regular authentication dialog box (like when connecting to a share).

b) the configuration would fail wil the message "Catalog host not reachable or specified port incorrect"

Per default PowerFuse will talk to the Catalog host on tcp/8080. It turned out that something else was using that port. In my case it was my good old SoftGrid/App-V server 4.1, which was giving me grief.

As it would appear that in the IR it's currently not possible to change the port of the catalog host, I had to change it on the softgrid server. If you don't remember how to do this, here's how:

1) start the SoftGrid Management Console
2) go to Server Groups|Default Server Group and rightclick on your server
3) chose properties and go to the Ports tab
4) change port 8080 to something else
5) restart the "SoftGrid Virtual Application Server"

To use the new port on the softgrid clients, you will then have to specify the server as hostname:newport for it to use the alternate port. That is, if you are still using SoftGrid for icon deployment and/or authentication for some reason. (Way better to use PowerFuse for this)

When I figure out how/if you can change the CatHost's portnumber, I will post a followup.

/Max
« Last Edit: January 07, 2010, 12:11:34 PM by RESguru » Logged

Cheers,
Max Ranzau aka RESguru. Twitter: http://twitter.com/RESguru
jspeetjens
Newbie
*
Posts: 2


« Reply #1 on: February 16, 2010, 04:43:12 PM »

Hi i also had this problem, when i was new to Orchestration pack

soon i found out that i had to configure a 'third party integration' for res powerfuse in the orchestration pack control center Smiley

Logged
Pages: [1]
Print
Jump to: