Add Package

**Adding Packages: Two Methods**
There are two ways to add packages:
**1. Adding a New Package**: You can click the "Add Package" button in the upper right corner of the "Package Overview" page to open the package upload page.
**2. Adding a New Version**: You can click "Add New Version" in the operation bar of an existing package entry to create a new version of the package. The package ID remains consistent across different versions.
When adding a package, you can choose to upload a** portable green application (zip file)**, a s**erver-installed application**, or a **WEBGL application**.
• If you select "**Upload Portable Green Application**", you must upload a zip file.
• If you select "**Server-Installed Application**", you need to ensure that the executable file path is an absolute path, such as:   C:\Appli\20220811143250962\LarkDataChannelDemo.exe  , and that the application is installed on all rendering nodes.
• If you select "**WEBGL**", you need to provide the URL of the WebGL page.

![](https://docs.paraverse.cc/media/202504/141fa7bdbce341eb82813106f6fda9ae7697.png)

![](https://docs.paraverse.cc/media/202504/24ef352515ae4488b70d96a84c0012f54853.png)

**Glossary:**

- **Program Package Name:** Used to define the name of the program package, which will be filled into the default name of the application when adding it.

- **Version Number:** The version number of the program package used to differentiate between different versions. Applications can switch to using different versions based on the version number.

- **Workspace:** Represents the workspace to which the application belongs, used to differentiate user permissions, access permissions, and the application concurrency limit under the workspace.

- **Execution File Path:** The relative path of the executable file in the compressed package that launches the application. It will be automatically filled in the drop-down list of execution file paths after uploading the program package.

> **Special Note:** For applications developed using the Unreal Engine, when uploading the application, do not select the exe program in the root directory. The correct path should be: "Same directory -> Project name directory -> Binaries -> Win64 -> xxx.exe". An example of an execution file path is: **WindowsNoEditor\MyProject3\Binaries\Win64\MyProject3.exe**

- **Launch Parameters:** Applications developed using the Unreal Engine may require launch parameters. You can directly run locally -> launch [Task Manager] -> [Details] -> hover over the status bar, right-click and select [Select Columns] -> check [Command Line], then find the running UE4 application and view the command line parameters.

- **Synchronization Type:**

> **Active Sync:** Once the application or rendering node is registered, the application is directly synchronized and can be used immediately.

**Semi-Active Sync:** When choosing semi-active sync, you can select the synchronization area, with the default sync coefficient being 1, indicating that only one node synchronizes one application in one area. This scenario is suitable for when disk space is limited on multiple cluster nodes, syncing only one node to save disk space.