> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/command-line-scripts/install-a-published-package-via-command-line.md). # Install a Published Package via Command Line System Administrators can install a published package in a different LogicNets installation using the following steps in the command line: 1. Publish a project and download the zip-file to the server (e.g. *c:\mypackage.zip*). 2. Open the command prompt. 3. Go to *c:\LogicNets\system\scripts*. 4. Start the install package script (). ``` install_package mycompany C:\mypackage.zip myapp. ``` 1. Start the package. 1. Open an internet browser. 2. Go to the URL Note: If you re-install a package with the same name the system overwrites the previous package. By default, the system sets already installed packages of the same category (project name in the Designer) *inactive*. You can disable this functionality by providing an additional command line parameter: *keepexistingactive*. **Using the Package Installer** The system interprets Designer project names as the category names for their published package, which provides an alternative to the above approach. If you copy a Designer project and rename it published packages from that project will acquire the new category name. Packages you install from the new Designer project will have their own unique category label, and will not deactivate any other packages. A naming example is laid out in the table below. |

Designer Project\*\*
\*\*(Published Category Name)

| Item | Published Package Name | Notes | | ------------------------------------------------------------ | ---- | ---------------------- | ---------------------------------------------------------- | | Project1\_0 | 1 | Project1\_0\_1 | | | Project1\_0 | 2 | Project1\_0\_2 | 2 WILL deactivate 1 | | Project1\_1 | 3 | Project1\_1\_1 | 3 will NOT deactivate 1 or 2 | | Project1\_1 | 4 | Project1\_1\_2 |

4 will NOT deactivate 1 or 2
4 WILL deactivate 3

| If a meta-xml file is located next to the package-zip file (*C:\mypackage.zip*) with the same name as the package-zip file added with ".xml" (*C:\mypackage.zip.xml)* the system installs the meta-xml file as well. If the installation fails the system sets a non-zero exit code. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/platform-documentation/system-administration/command-line-scripts/install-a-published-package-via-command-line.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.