Helix Core Server Administrator Guide: Fundamentals (2018.2)

Adding or updating the license file

Note

When you receive your license file, its name might include the license host, an IP address, or other identifying information.

Rename the new license file to license.txt.

Important

If you have purchased Helix4Git in addition to Helix Core, you will receive:

The email for Helix4Git, which contains the license file that enables both Helix Core and Helix4Git. You will install this license file.
The email for Helix Core, contains a license file that does NOT enable Helix4Git. Do NOT install this license file, but do keep it for your records.

If your P4ROOT directory has a file named license, remove it.

To add or update the license file, use one of the following:	Valid for ...
Copy the license file to the P4ROOT directory. see License file in the P4ROOT directory	Server Any replica that you want to enable to become a master through failover
Issue the p4 license command. see p4 license command	Server
Use P4Admin. see Helix Visual Client (P4V) Administration tool	Server

To add or update the license file, use one of the following:

Valid for ...

Copy the license file to the P4ROOT directory.

Issue the p4 license command.

Server

Use P4Admin.

Server

License file in the P4ROOT directory

Stop and restart the server if ...	No server restart required if ...
Any of the following are true: Server's IP address changes Port number in the license file changes You are adding a server license to a previously unlicensed replica to prepare for a possible failover Additional information is available in the Knowledge Base article P4D: Installing A New License File.	All of the following are true: Server's IP address remains as-is Port number in the license file remains as-is Any unlicensed replica remains unlicensed, and thus is not prepared to become the new master in case of a failover Note An edge server is a filtered replica and therefore not eligible to be a standby server.

Stop and restart the server if ...

No server restart required if ...

Any of the following are true:

Server's IP address changes
Port number in the license file changes
You are adding a server license to a previously unlicensed replica to prepare for a possible failover

Additional information is available in the Knowledge Base article P4D: Installing A New License File.

All of the following are true:

Server's IP address remains as-is
Port number in the license file remains as-is
Any unlicensed replica remains unlicensed, and thus is not prepared to become the new master in case of a failover

Note
An edge server is a filtered replica and therefore not eligible to be a standby server.

If you need to stop and restart the server ...

	Windows	Linux/UNIX/Mac
To stop the server	p4 -u User -p Server:Port admin stop
To restart the server	Open an administrator command prompt and enter `net start perforce` or enter `services.msc`, go to the Services Management Console, find `Perforce`, and select Start.	Run the Perforce Server startup script you usually use. If you do not have a Perforce startup script, the command to start the Perforce Server in Daemon Mode in the specified P4ROOT location might resemble the following: `p4d -r /specify/path/to/P4ROOT -d`

If a valid license file is already in the server root directory, as a super user, you can update it.

If the IP address or port number has not changed,

Launch P4V as a Helix Server superuser.
Choose Tools > Administration.
On the Administration Home page, click Load new license file and browse to the license file on your local disk.
After successful installation, verify that the Administration tool Home page is updated with the new license information.

Tip

For more information, see the Support Knowledgebase article, "Moving the Perforce Server".