Parallel Deployment Configuration Question

Virginia Tech is new to Luminis. We're struggling with getting parallel deployment working on a new installation of Luminis 4.1. SGHE has not been much help so I'm hoping one of you might have some ideas.

We currently have the resource server installed and running on a server called portal-dvlp-1.domain_name. We plan to run multiple portal tier boxes on servers named portal-dvlp-n.domain_name. We have the virtual hostname poral-dvlp.domain_name mapped to our load balancer.

Pointing a browser at portal-dvlp.domain_name results in a redirect to portal-dvlp-1 (resource server). We are now trying to get the resource box to respond as the virtual host. We changed the values for web.fqn and web.host to the virtual hostname and ran cpfixurls. The server now answers calls to portal-dvlp.domain_name. However, logins fail with a message saying "Can't service request to /cp/home/next". It looks as though the cpfixurls script didn't do anything. I still have a ton of references in webapps/luminis that point to portal-dvlp-1. Any ideas?

We created a service request with SGHE. They came back with a response saying that you can't run the portal tier on the resource server when using the parallel deployment configuration. Does this sound correct? It certainly goes against all of their documentation.

Ken

0
No votes yet

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Log files

Ken, what do you see in cp.log related to your login attempts?

hosts files

Are you still running through the load balancer to get to the resource box?

Try cutting that out of the scenario.
I've never used cpfixurls, so I don't know if that works well or not.

Just put your URL that you setup/fixed the site to use in the server and desktop hosts file, pointing to the machine you want to test directly. We've seen misconfigured loadbalancers give that error before.

Resource and portal tiers for PD install

Hi Ken-

SGHE told you correct - in a PD install, the resource server/tier is installed on a separate server instance than the portal/web tier. Each tier has a different function/role in a PD configuration :

  • The resource tier server is used to house the LDAP directory, and can also house the calendar application.
  • The portal tier server is where your tomcat application/web server instances are installed.

So in a PD install, the load balancer will pass the web request to one of the portal tier machines, which then queries your resource tier for the needed Luminis settings and configurations so that it can process the web request.

So to have a complete PD install, you need the following installed/configured in this order :

  • Load balancer which answers to your portal URL
  • Resource tier (install this first)
  • Calendar server (if installed on a separate machine than the resource tier
  • Web tier
  • Mail server/tier

   Alice Kim