> 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/logicnets-software-component-details/content-authoring-software-parts/logicnets-deployment-manager-ln-wsp-d.md). # LogicNets Deployment Manager (LN-WSP-D) ## License Basis: Per organization Notes: 1. Used in conjunction with the Designer (D) and Shared Workspaces (WSP) 2. Allows Designer users of the Shared Workspaces module to deploy and manage shared published packages across a multi-server environment 3. Must be ordered at the organizational level as part of the Enterprise Authoring Bundle (EAB) 4. Is an add-on option to and requires a license for Shared Workspaces (see the Shared Workspaces article) ## LN-WSP-D Description The Deployment Manager is an additional component you can acquire as an optional feature of Shared Workspaces. It provides a dashboard for managing the complete collection of LogicNets executable packages generated from Shared Workspaces and deployed for production use. Users can see all available packages, publish new versions, and control how they distribute different versions for runtime execution and track their status. When used with load balancing, the Deployment Manager dashboard lets users selectively take servers in and out of production while seamlessly preserving application access for users. Organizations deploying LogicNets for enterprise or mission-critical use are highly encouraged to acquire this option in particular if they have: * Sophisticated deployment and lifecycle management needs * Enterprise-level or mission-critical production processing requirements ## Services and Deployment Considerations No additional services are required for basic deployment of Deployment Manager. Optional LogicNets Training Services (LN-TS) are available to teach designer users how to use the module to optimally manage sophisticated rollout of LogicNets applications over a multi-server topology. PG-CO5-260217 --- # 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/logicnets-software-component-details/content-authoring-software-parts/logicnets-deployment-manager-ln-wsp-d.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.