Jump to content


Setting Up Floats for Mass Deployment


  • Please log in to reply
No replies to this topic

#1 Guest_ttibbits_*

Guest_ttibbits_*
  • Guests

Posted 22 February 2010 - 06:53 PM

When installing Phoenix apps remotely, you can configure and add specific files to the deployment package that will reduce the amount of configuration that the end users will have to perform in order to get PHX working the first time.

 

End-users of Phoenix using Floating Licenses have to from have tell their local PHX installation where the floating license server is that they want to check out floating licenses from.

 

This can be done once in an IT environment and then the files can be added to the deployment package for distribution.

 

In the IT environment that you will copy and distribute, launch PHX and go to Edit | Preferences | License Server Management and add the DNS name or the IP address of the floating license server. Then in License Management, click on the button in the Name column list that will check out a license that is available to be checked out on the license server you just added.

 

This will make changes to two files in PHX.

 

Adding the address of the license server changes the configuration of the following file to contain the license server address:

C:\Documents and Settings\ttibbits\Application Data\Pharsight\Phoenix\Configuration\licensing.server.configuration.binconfig

 

Checking out an available license from the license server will make a change to this file:

C:\Documents and Settings\ttibbits\Application Data\Pharsight\Phoenix\Configuration\licensing.licenses.configuration.binconfig

 

When end-users launch Phoenix for the first time, this license server will have already been added for them and PHX will automatically grab or check out the type of license you defined in your IT environment (e.g.: PHX_WNL).

 

If you choose to configure the licensing.licenses.configuration.binconfig file to already select a license, be aware that all of the users that open PHX the first time will request all of the licenses you add to the config file from the server and possibly deplete them. Perhaps just selecting a PHX WNL license would be enough to get them up and running.

 

However, it is important that end-users learn how to go into Phoenix’s Preferences and check out a license so I wouldn’t recommend making this a part of your standard deployment package.

 

Page 31 of the Getting Start Guide includes information on how a user would “check out” a floating license. It’s simply a function of having them go into PHX’s Edit | Preferences | Licensing | License Management and having them click on the specific button for the license they want to check out.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users