Control Center Binary Package

Downloading and Installing the Binary Package

Obtain the Control Center 2025.2 binaries and license from our Sales.
Unpack the archive into a directory of your choice (“installation directory”).
Once you have unpacked the package, launch Control Center by running control-center.sh (or control-center.bat for Windows) in the installation directory.

Control Center starts with the default configuration and listens on the default port (3000). Open http://localhost:3000 in your browser and sign up for an account.

Explicitly Defining Your Work Folder

By default, Control Center stores all data in $CC_ROOT/work. However, we recommend using a folder outside of the default location to simplify version update operations. To change the default work folder, do one of the following:

Define the IGNITE_WORK_DIR environment variable; for example:

IGNITE_WORK_DIR=/path/to/cc/work $CC_ROOT/control-center.sh

Define the JAVA_OPTS env variable; for example:

JAVA_OPTS="${JAVA_OPTS} -DIGNITE_WORK_DIR=/path/to/cc/work" $CC_ROOT/control-center.sh

Explicitly define the work folder in $CC_ROOT/ignite-config.xml:

<bean class="org.apache.ignite.configuration.IgniteConfiguration">
    ...
    <property name="workDirectory" value="/your/path/to/cc-work"/>

Setting Control Center URI

The Control Center URI is the URI where the GridGain Control Center is running. Your clusters will need to know this URI to be able to establish connection with Control Center.

Set the URI by using the management script:

{GRIDGAIN_HOME}/bin/management.sh --uri http://localhost:3000

Note the ID of the cluster in the node output. You will need it to add the cluster in the Control Center UI. See Connecting a Cluster.

You can also set the URI in System Properties: -Dcontrol.center.agent.uris=https://portal-test.gridgain.com.

Open Port Requirements

To ensure proper Control Center operation, port 3000 must be open for the system’s backend.

SSL Configuration

To configure SSL for the on-premise version of GridGain Control Center:

Create an application.properties file in the Control Center root folder.

Add the following lines to the file:

server.port=
server.ssl.client-auth=need
server.ssl.protocol=TLS
server.ssl.key-store-type=JKS
server.ssl.key-store=node.jks
server.ssl.key-store-password={safe_password}
server.ssl.trust-store-type=JKS
server.ssl.trust-store=trust.jks
server.ssl.trust-store-password={safe_password}

Run the following command:
```
bash control-center.sh
```
Control Center is started at https://localhost:3000.
Navigate to the cluster you want to connect and use the management.sh utility to override the Control Center URI:
```
${GG_ROOT}/bin/management.sh --uri https://localhost:3000
```
If you have used a self-signed certificate in Control Center, make sure that this certificate is present in truststore used by the Control Center agent at the cluster side. You can import the self-signed certificate into separate truststore file and expose it to the Control Center:
```
${GG_ROOT}/bin/management.sh --uri https://localhost:3000 --management-truststore /path/to/truststore.jks --management-truststore-password changeit
```

Next Steps

Change Configuration Parameters - make sure you optimize the disk space utilization
Add a License
Connect a GridGain or Apache Ignite Cluster

© 2025 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.

Last updated on May 29, 2025