npm - @hcl-software/dxclient - Versions diffs - 226.0.0 → 227.0.0 - Mend

@hcl-software/dxclient 226.0.0 → 227.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (32) hide show

package/README.md CHANGED Viewed

@@ -6,372 +6,86 @@ DXClient can take artifacts developed locally and deploy them to HCL DX servers
 DXClient is meant to be the one-stop, platform-independent solution that lets you integrate HCL DX with any automation infrastructure of your choice.
-DXClient comes with two deployment options:
-1. One option is the DXClient container package. DXClient is packaged as a container that can be run using OCI-based runtimes such as Docker or Podman. It is available as a container image with HCL DX 9.5 CF196 and later releases.
-**Warning** - Recent changes to Podman introduced by RedHat have caused a compatibility issue with the container implementation of DXClient. HCL is currently investigating how this might be resolved. Until further notice, Docker is recommended for using the DXClient container implementation.
-2. The alternative deployment option is DXClient as native JavaScript code. Customers who want to rely on this deployment option need to install their own Node.js and NPM runtime environment in the correct version and must install necessary dependencies as needed.
-**Important Note related to DXClient version & distribution:** DXClient is now available free to download/install through NpmJS and harbor repositories. Following the decision to openly distribute DXClient, we have changed the current versioning format of DXClient from 1.xx.x to <CFNumber>.x.x. For example, the last release version of DXClient was "1.29.0" but the upcoming release is reformatted to "221.0.0". The number 221 is synonymous with the CF Number version of DX deployments.
+## Table of Contents
+- [DXClient](#dxclient)
+- [Deployment Options](#deployment-options)
+- [Native JavaScript Code Installation Options](#native-javascript-code-installation-options)
+- [Verify the DXClient Installation](#verify-the-dxclient-installation)
+- [DXClient Configuration](#dxclient-configuration)
+  - [Configuring TLS Certificate Validation for Secure Connections](#configuring-tls-certificate-validation-for-secure-connections)
+- [DXClient Help Commands](#dxclient-help-commands)
+- [All Available Commands](#all-available-commands)
+- [Command Options](#command-options)
+- [Logger Enablement](#logger-enablement)
+  - [Enable Logger](#enable-logger)
+  - [Disable Logger](#disable-logger)
+- [DXClient Release Timelines & Updates](#dxclient-release-timelines--updates)
+- [DXClient Documentation](#dxclient-documentation)
+## Deployment Options
+1. This documentation, recommended for **local developers and admins**, is for the Native JavaScript Code Installation Option of DXClient.
+2. One other option is the DXClient container package which is preferred for **CI/CD automation** scenarios. DXClient is packaged as a container that can be run using OCI-based runtimes such as Docker or Podman. It is available as a container image with HCL DX 9.5 CF196 and later releases. More information could be found in the [dxclient-scripts](https://github.com/HCL-TECH-SOFTWARE/dxclient-scripts).
+**Important Note related to DXClient version & distribution:** DXClient is now available free to download/install through NpmJS and harbor repositories. Following the decision to openly distribute DXClient, we have changed the current versioning format of DXClient from 1.xx.x to CFNumber.x.x. For example, the old release version of DXClient was "1.29.0" but the upcoming releases is reformatted to "221.0.0". The number 221 is synonymous with the CF Number version of DX deployments.
 **This document is for the native JS (non-container) version of DXClient**
-# Requirements
-To use these tools you will need:
-- Node.js must be installed on your workstation. It is tested using the LTS versions of Node.js.
-  Note: You can verify that Node.js is installed by running the following commands:
-    `node -v`
-# Install DXClient with package from HCL Software Portal
-Complete the following steps to install the DXClient tool to your local development workstation or automation server.
-1. Download the DXClient.zip file (DXClient_VX_XXXXXXXX-XXXX.zip) to a local directory on the local workstation from your HCL Digital Experience 9.5 CF196 or higher entitlements on the HCL Software License Portal.
-2. run `make install` to install all dependencies
-   In case of windows OS run `make_install.bat` to install all dependencies
- (Optional)Run the below command in case you prefer to link your application to the local npm module in your machine (Refer to the Notes section before you proceed).
- For Linux and Apple MacOS platforms
- ```
-  make link
- ```
- For Microsoft Windows platforms:
- ```
- make_link.bat
- ```
-> ### Notes:
-> Avoid using `make link` command when scripting deployments from an automation server (e.g. in pipelines) as there is a chance of picking up the wrong dependencies during tool version upgrades.
-3. Use the command below to run the application.
-	For Linux and Apple MacOS platforms
-  ```
-  ./bin/dxclient
-  ```
-  For Microsoft Windows platforms:
-  ```
-  node bin/dxclient
-  ```
-4. Run 'dxclient -V' to verify that the dxclient command line is installed.
-5. A folder named 'store' will be created in your working directory.
-6. You will be able to find the configuration, logger, output, and sample files under location - <working-directory>/store.
-If you require to create a new configuration, set the environment variable `VOLUME_DIR` to the desired directory name and run your task. For example:
-    "Linux and Apple macOS"
-        ```
-		bash
-        export VOLUME_DIR=storeForScriptApplication
-        # or if you want spaces in its value, enclose it in double quotes ("")
-        export VOLUME_DIR="store for script application"
-        ```
-    "Microsoft Windows"
-        ```
-		batch
-        set VOLUME_DIR=storeForScriptApplication
-        :: or if you want spaces in its value
-        set VOLUME_DIR=store for script application
-        ```
+## Native JavaScript Code Installation Options
-        !!!important
-            Do not enclose the value of `VOLUME_DIR` in double quotes ("") in Windows. This produces errors when executing DXClient commands.
+1. **From NpmJS Registry**:
+   1. To install globally (Recommended): `npm install -g @hcl-software/dxclient`
+   2. To install locally: `npm install @hcl-software/dxclient`
+   3. To uninstall: `npm uninstall @hcl-software/dxclient`
-7. The `VOLUME_DIR` requires read and write access permissions. Set appropriate permissions for the `VOLUME_DIR` as per user/group/owner.
+2. **From HCL Software Portal**:
+   - Download the DXClient.zip file from your HCL Digital Experience 9.5 CF196 or higher entitlements.
+   - Run `make install` to install all dependencies (for Windows, run `make_install.bat`).
+   - (Optional but recommended) Link your application to the local npm module: `make link` (for Windows, run `make_link.bat`), this will make your dxclient available globally.
+   - Run `dxclient -V` to verify the installation.
-    "Linux and Apple macOS"
-        ```
-		bash
-        chmod xxx <working-directory>/<VOLUME_DIR>
-        # where xxx is a 3-digit number where each digit can be anything from 0 to 7.
-        # Ref: https://wiki.archlinux.org/title/File_permissions_and_attributes#Numeric_method
-        ```
-    "Microsoft Windows"
-		```
-        1. Right click `<working-directory>/<VOLUME_DIR>` directory > "Properties" > "Security" Tab.
-        2. Set the appropriate permission for the folder.
-		```
-You can find the configuration, logger, and output files under `<working-directory>/<VOLUME_DIR>`.
-Common command arguments can be pre-configured inside the config.json file available under the `<working-directory>/<VOLUME_DIR>` folder. A sample configuration file that can be used on on-premises platforms in standalone, cluster (default-config.json), or Kubernetes (default-config-kube.json) platforms is also available under <working-directory>/samples/sample-configurations for reference. If you want to override any of the parameters in the config.json, add them in your command line.
-## DXClient uninstall
-To uninstall the DXClient tool, follow the commands below.
-For Linux and Apple MacOS platforms:
-```
-make clean
-```
-For Microsoft Windows platforms:
-```
-make uninstall.bat
-```
-To unlink the DXClient tool, follow the commands below.
-For Linux and Apple MacOS platforms:
-```
-make unlink
-```
-For Microsoft Windows platforms:
-```
-make_unlink.bat
-```
-# Install/Uninstall DXClient from NpmJS registry
-Use `npm install @hcl-software/dxclient` command to install the latest version of DXClient.
-Use `npm install -g @hcl-software/dxclient` command to install DXClient globally.
-Use `npm uninstall @hcl-software/dxclient` command to uninstall.
-This option to install/uninstall are avaialble from HCL DX 9.5 CF221 deployment. The latest version you install will be "221.0.0".
-> **Note:**
-> To install dxclient on a Windows OS in an empty folder, first create an empty `package.json` file before running the npm install commands.
-## Additional Information
-1. The attribute `-dxConnectHostname` has been deprecated (since CF202) and removed (since CF210) and must be replaced with `-hostname` wherever necessary.
-2. The attribute `-targetServerHostname`, `-targetServerPort`,`-targetServerUsername`,`-targetServerPassword` & `-targetServerProfileName` has been deprecated (since CF202) and removed (since CF210) and must be replaced with `-targetHostname`, `-targetDxConnectPort`,`-targetDxConnectUsername`,`-targetDxConnectPassword` & `-targetDxProfileName` respectively wherever necessary.
-3. If deploying or importing huge CICD artifacts using DXClient to the Kubernetes environment, you might receive failure or request pending messages while you run the ceratin tasks. This might happen because of the connection getting closed by the load balancer due to timeout before the response is ready. In such situations, before re-triggering the request, we advise you to check your target server to verify if the artifact has been deployed/imported or the server is up, as the request was already triggered from the client-side. In cases of request pending you are expected to receive a `requestId` which you can use to check the status of response later. Find troubleshooting tips [here](troubleshooting_dxclient.md#troubleshooting-for-some-known-issues).
-4. The maximum input file size allowed in DXClient is 256 MB currently. This limitation will be addressed in one of the future releases.
-5. As of CF213, the property `DXCONNECT_MAX_MEMORY_SIZE_MB` in DXC_ConfigSettings Resource Environment Provider has been removed. Refer [DXC_ConfigSettings](dxconnect.md#resource-environment-provider-property-for-dxconnect) for more details.
-6. As of CF226, Enabled TLS certificate validation while using DXClient.Refer [here](#configuring-tls-certificate-validation-for-secure-connections) for more details.
 ## Verify the DXClient installation
-Successful installation of the DXClient tool can be checked using the "`dxclient -V`" command which should show the version of the DX Client tool installed.
+Successful installation of the DXClient tool can be checked using the "`dxclient -V`" command which should show the version of the DX Client tool installed (Option 1.1). Use "`./node_modules/.bin/dxclient -V`" when installed locally (Option 1.2).
 Once installed, commands can be executed using the DXClient tool to perform CI / CD actions on HCL DX 9.5 servers.
-**Important:**
-The DXClient version is mostly forward and backward compatible with the DX CF versions. However, in some cases, it might not work as expected if the CF versions are different. Make sure that the CF versions of both DXClient and DX Core are the same in your installation.
-You may use "`dxclient version-compat`" to check version compatibility between DX Core and DXClient.
-### DXClient Release Timelines & Updates
-1. If connecting to an HCL DX 9.5 CF19 deployment, the DXClient tool provides commands supporting the following artifact types along with the documentation -
-* deploy/undeploy portlets
-* deploy script applications
-* xmlaccess
-* restore script application
-2. If connecting to an HCL DX 9.5 CF192 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation -
-* undeploy script applications
-* deploy themes (EAR & WebDAV based)
-3. If connecting to an HCL DX 9.5 CF193 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation -
-* restart application
-* deploy application
-* manage syndicator
-* manage subscriber
-4. If connecting to an HCL DX 9.5 CF195 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* undeploy theme
-5. If connecting to an HCL DX 9.5 CF196 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* shared library
-6. If connecting to an HCL DX 9.5 CF197 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* Get Syndication failed report
-* Delete DAM schema
-7. If connecting to an HCL DX 9.5 CF198 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* Resource Environment Provider Updates - Create,update and delete
-* Create/import/export/list of virtual portal
-* Import and Export PZN
-* List DAM schemas
-8. If connecting to an HCL DX 9.5 CF199 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* Resource Environment Provider Updates - Export and Import
-* Create Credential Vault Slot
-* Create Syndication Relation
-* DAM Staging - Register, Deregister and Trigger
-9. If connecting to an HCL DX 9.5 CF200 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* WCM Libraries - Export and Import
-* DX Core Configuration Reports - summary-report
-10. If connecting to an HCL DX 9.5 CF201 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* An optional parameter requestId added to Deploy theme, Deploy application, Restart DX Core server, and Manage virtual portals.
-* Retrieve feature added to the Resource environment provider.
-* Accessing ConfigWizard in container environment
-Note that a few parameters are deprecated and replaced with new parameters in the DX Core configuration reports. For information, see DX Core server configuration report.
-11. If connecting to an HCL DX 9.5 CF202 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* Deprecated parameter dxConnectHostname. It is recommended that you start using the replacement parameter -hostname starting from CF202 wherever necessary.
-* DAM Assets Export & import
-12. If connecting to an HCL DX 9.5 CF207 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* Support to set different Container Runtimes.
-13. If connecting to an HCL DX 9.5 CF208 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* Get all subscribers details for DAM staging
-14. If connecting to an HCL DX 9.5 CF209 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-* Restart Core Pods in a Kubernetes Deployment
-15. If connecting to an HCL DX 9.5 CF210 deployment, following changes are to be expected.
-* Removed paramaters deprecated during CF201 & CF202 deployment.
-* added ability to export/import wcm libraries in Virtual Portal.
-16. If connecting to an HCL DX 9.5 CF211 deployment, following changes are to be expected.
-* Deploy and Undeploy Applications
-17. If connecting to an HCL DX 9.5 CF213 deployment, following changes are to be expected.
-* Livesync of WebDAV based Themes
-18. If connecting to an HCL DX 9.5 CF214 deployment, following changes are to be expected.
-* Livesync Improvements
-	- List themes during Pull theme in case themeName is not provided.
-	- Livesync is now supported in scaled DX environment setups
-19. If connecting to an HCL DX 9.5 CF216 deployment, following changes are to be expected.
-* Show Version compatibility details between DXCore and DXClient
-20. If connecting to an HCL DX 9.5 CF219 deployment, following changes are to be expected.
-* Enabled multiple environment configuration in node version
-21. If connecting to an HCL DX 9.5 CF221 deployment, following changes are to be expected.
-* DXClient Version Type(Node/Container) information available using help/version-compat commands
-* A one time license agreement click-through is enabled. To skip the prompt, use "accept-license" command.
-* DXClient will be openly distributed in NpmJS & harbor repository.
-* In DAM Staging tasks, the parameters dxWASUsername, dxWASPassword, targetServerWASUsername, and targetServerWASPassword are now deprecated and should no longer be used.
-22. If connecting to an HCL DX 9.5 CF224 release, following changes are to be expected.
-* New DXClient LiveSync Sub-Commands: LiveSync push-wcm-design-library | pull-wcm-design-library
-24. If connecting to an HCL DX 9.5 CF225 release, following changes are to be expected.
-* Livsync enabled for Presentation Template under WCM Design Library.
-25. If connecting to an HCL DX 9.5 CF226 release, following changes are to be expected.
-* Enabled TLS certificate validation while using DXClient.
+> **Important:**
+> The DXClient version is mostly forward and backward compatible with the DX CF versions. However, in some cases, it might not work as expected if the CF versions are different. Make sure that the CF versions of both DXClient and DX Core are the same in your installation. You may use "`dxclient version-compat`" to check version compatibility between DX Core and DXClient.
 ## DXClient configuration
-Common command arguments that are listed in `config.json` can be pre-configured via this file. The common arguments could also be provided through command line. If so, it will override the values in `config.json` and execute.
+Common command arguments that are listed in `config.json` can be pre-configured via this file. The common arguments could also be provided through command line. If so, it will override the values in `config.json` and execute. This json file will be generated in the store folder that is created where you executed the dxclient command.
-A sample configuration file that could be used on-premises platforms in standalone, cluster platforms is also available under `samples/sample-configurations/default-config.json` for reference.
+A sample configuration file that could be used on-premises platforms in standalone, cluster platforms is also available under [here](https://github.com/HCL-TECH-SOFTWARE/dxclient-scripts/blob/main/samples/sample-configurations/default-config.json) for reference.
 ### Configuring TLS Certificate Validation for Secure Connections
 As part of our ongoing efforts to improve security and maintain best practices in our development and production environments, we have made a key change in the way we handle TLS (Transport Layer Security) connections while using DXClient from CF226. You can still trust custom certificates (e.g., self-signed or third-party CAs), without disabling validation entirely.
-Step 1:Obtain the Certificate
+**Step 1: Obtain the Certificate**
 Ensure you have the .pem certificate file that you wish to add to the trust store. It must contain the whole content of both key and certificate files.
-Step 2:Add the certificate
+**Step 2: Add the certificate**
 You have two ways to add/set the Certificate file.
 a. Using NODE_EXTRA_CA_CERTS
 By enabling NODE_EXTRA_CA_CERTS, we now provide a secure way to add custom trusted certificates. To use the NODE_EXTRA_CA_CERTS environment variable, you need to specify the path to a PEM file that contains the key & certificate details. Here's how you can configure it in your local or production environment:
 "Linux and Apple macOS"
-	```
-	export NODE_EXTRA_CA_CERTS=/Users/myUser/my-cert.pem
-	```
+ ```
+ export NODE_EXTRA_CA_CERTS=/Users/myUser/my-cert.pem
+ ```
 "Microsoft Windows"
-	```
-	set NODE_EXTRA_CA_CERTS=C:\Users\myUser\my-cert.pem
-	```
+ ```
+ set NODE_EXTRA_CA_CERTS=C:\Users\myUser\my-cert.pem
+ ```
 b. Add certificate to the trust store on your OS.
 **Note**  In local or development environments, you may want to disable this security feature to allow connections to services with self-signed or invalid certificates. By setting NODE_TLS_REJECT_UNAUTHORIZED to 0, you can bypass certificate validation. This can be useful for testing, but it should never be used in production environments because it can expose your application to potential security risks.
-### DXClient Commands
-- `make link`: To create a symlinks to global npm folder for Microsoft Windows platforms
-- `make_link.bat` : To create a symlinks to global npm folder
-- `make unlink`: To remove the symlink created by the make link
-- `make_unlink.bat`: To remove the symlink created by the make link for Microsoft Windows platforms
-- `make install`: To install all dependency
-- `make_install.bat` :  To install all dependencies of windows OS
-- `make uninstall`: To uninstall the package and dependency
-- `make_uninstall.bat`: To uninstall the package and dependency of windows OS
-To list the artifact details, run
-```
-dxclient                                        - help document for the commands usage
-dxclient accept-license							- command to skip prompt of click-through license acceptance agreement.
-dxclient version-compat							- command to show version compatibility details between DX Core and DXClient
-dxclient deploy-portlet [options]               - command to execute the deploy portlet action
-dxclient undeploy-portlet [options]             - command to execute the undeploy portlet action
-dxclient xmlaccess [options]                    - command to execute the xmlaccess action
-dxclient deploy-scriptapplication [options]     - command to execute the deploy script application action
-dxclient undeploy-scriptapplication [options]   - command to execute the undeploy script application action
-dxclient restore-scriptapplication [options]    - command to execute the restore script application action
-dxclient deploy-theme [options]                 - command to execute the deploy theme action
-dxclient undeploy-theme [options]               - command to execute the undeploy theme action
-dxclient deploy-application [options]           - command to execute the deploy application action
-dxclient undeploy-application [options]         - command to execute the undeploy application action
-dxclient manage-syndicator [options]            - command to execute the syndicator action
-dxclient manage-subscriber [options]            - command to execute the subscriber action
-dxclient restart-dx-core [options]              - command to execute the DX Core restart action
-dxclient mls-export  [options]                  - command to export content of a WCM Library for translation
-dxclient mls-import  [options]                  - command to import the translated contents into the DX
-dxclient manage-syndicator get-syndication-report [options] - command to execute the syndication failed report
-dxclient delete-dam-schema  [options]           - command to execute the delete dam schema action
-dxclient list-dam-schemas  [options]            - command to execute the list of all dam schema action
-dxclient pzn-export [options]                   - command to export the pzn rules from the target server
-dxclient pzn-import [options]                   - command to import the pzn rules into the target server
-dxclient resource-env-provider [options]        - command to create, update or delete a custom property from an existing Resource Environment  Provider
-dxclient manage-virtual-portal [options]        - command to manage virtual portal tasks in the DX server
-dxclient manage-dam-staging register-dam-subscriber [options] - command to execute the register subscriber action
-dxclient manage-dam-staging trigger-staging [options] - command to execute the trigger staging action
-dxclient manage-dam-staging deregister-dam-subscriber  [options] - command to execute the deregister subscriber action
-dxclient manage-dam-staging get-all-subscribers [options] - command to execute the get subscribers details action
-dxclient manage-dam-staging update-secrets [options] - command to execute the update secrets action
-dxclient manage-dam-staging find-staging-mismatch [options] - command to execute the find mismatch action
-dxclient manage-dam-staging get-staging-mismatch-report [options] - command to generate staging mismatch report
-dxclient manage-dam-staging start-staging-resync [options] - command to execute the staging resync action
-dxclient manage-dam-staging delete-staging-mismatch [options] - command to execute the delete staging mismatch action
-dxclient create-credential-vault [options]      - command to create credential vault in the DX server
-dxclient wcm-library-export  [options]          - command to export the wcm libraries from the target server
-dxclient wcm-library-import  [options]          - command to import the wcm libraries from the target server
-dxclient dx-core-configuration-reports [options] - command to generate any dx core configuration reports
-dxclient manage-dam-assets export-assets [options] - command to export the dam assets
-dxclient manage-dam-assets validate-assets [options] - command to validate the dam assets
-dxclient manage-dam-assets import-assets [options] - command to import the dam assets
-dxclient restart-core-pods [options]            - command to execute the Restart Core Pods action (for Kubernetes deployments)
-dxclient livesync push-theme [options]          - command for watching a theme folder path live and syncs it in DX Server
-dxclient livesync pull-theme [options]          - command for downloading theme files from DX Server to a target local theme folder
-dxclient livesync push-wcm-design-library [options]          - command for watching a WCM Design Library folder path live and syncs it in DX Server
-dxclient livesync pull-wcm-design-library [options]          - command for downloading WCM Design Library files from DX Server to a target local folder
-```
-### DXClient Help commands
+## DXClient Help commands
 The following commands show the Help documents for DXClient command usage.
@@ -391,12 +105,6 @@ Use the following command to display the DXClient version number:
 dxclient -V, --version
 ```
-Use the following command to skip prompt of click-through license acceptance agreement:
-```
-dxclient accept-license
-```
 Use the following command to display the detailed help for a specific command:
 ```
@@ -408,2957 +116,215 @@ Use the following command to show version compatibility details between DX Core
 ```
 dxclient version-compat [command] [options]
-```
-Command options
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxConnectProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the CW server
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
-```
-### 1. Deploy Portlet
-Deploy-portlet command is used to deploy new or updated portlets to  target  DX Servers using the provided input xmlaccess file and path of the deployable war.
-Commands Description
-```
-dxclient deploy-portlet
-This command invokes the deploy-portlet tool inside the DXClient. The deploy-portlet dxtool uses the provided files and execute the deploy portlets task using the above available endpoints.
-```
-**Help command**
-This command shows the help document on the `deploy-portlet` command usage:
-```
-dxclient deploy-portlet -h
-```
-**Required files**
-Xml file: This xml file should contain the definition of the web application along with the details of the portlet\(s\) to be deployed. The web archive file path referred to in this file inside the URL element is ignored, but the URL element itself must exist as it is dynamically replaced when the command is executed. A sample XML file for deploying portlet\(s\) can be found in the samples directory of DXClient \(samples/DeployPortlet.xml\) or in DX server located in the following directory: PortalServer\_root/doc/xml-samples/DeployPortlet.xml.
-Portlet Application web archive file:This web archive .war file should contain the necessary portlet artifacts for deployment. Reference the Importing WAR files[https://help.hcltechsw.com/digital-experience/8.5/admin-system/adxmlref_import_war.html] for more details.
-**Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--xmlConfigPath <value>
-	Use this attribute to specify the path to DX configuration endpoint
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--xmlFile <xml file name with absolute path of the xmlaccess input file>
-	Use this attribute to specify the xml file that will be used while executing the deploy portlet task. For an example, see the DeployPortlet.xml file in the directory dxclient/samples/sample-xml-files/
--warFile <war file name with absolute path of the deployable war file>
- 	Use this attribute to specify the path of the war file to be deployed. For an example, see the WelcomePortlet.war file in the directory dxclient/samples/sample-xml-files/
-**Note:** Mandatory parameters xmlFile and warFile should be passed into the command line.
-```
- Example Usage:
-```
-dxclient deploy-portlet -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -xmlConfigPath <xmlConfigPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxConnectPort <dxConnectPort> -xmlFile <xml-file-with-path> -warFile <war-file-with-path>
-```
-### 2. Undeploy Portlet
-Undeploy-portlet command is used to undeploy the deployed portlets in the target DX Servers.
-**Note:** Undeploy-portlet will take the back up of deployed portlet application's xml file and application(EAR) if user has given enableBackup as true. By default enableBackup is set to true and placed in the `<working-directory>/store/outputFiles/portlets/backup/undeploy-portlet/`. In case if undeployed portlet is required, then the user can restore the portlet WAR file from the downloaded portlet application EAR file along with the exported deployable portlet application XML file.
-Commands Description
-```
-dxclient undeploy-portlet
-This command invokes the undeploy-portlet tool inside the DXClient. The undeploy-portlet dxtool uses the provided files and execute the undeploy portlet task.
-```
-**Help command**
-This command shows the help information for `undeploy-portlet` command usage:
-```
-dxclient undeploy-portlet -h
-```
-**Required files**
-```
-Xml file: This file should contain the definition of the web application along with the undeploy portlet details.
-```
-**Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--xmlConfigPath <value>
-	Use this attribute to specify the path to DX configuration endpoint
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--xmlFile <xml file name with absolute path of the xmlaccess input file>
-	Use this attribute to specify the xml file that will be used while executing the deploy portlet task. For an example, see the UndeployPortlet.xml file in the directory `<working-directory>/samples/sample-xml-files/`
--enableBackup <value>
- Use this attribute to take the backup of portlet application before undeploying it
-```
-Commands required when enableBackup is set to true
-```
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxSoapPort <Soap port of the DX server>
-    Use this attribute to specify Soap port of the DX server
--dxProfileName <Profile name of the DX core server>
-    Use this attribute to specify the profile name of the DX core server
--dxProfilePath <Profile path of the DX core server>
-    Use this attribute to specify the profile path of the DX core server
-```
-**Note:** Mandatory parameter xmlFile should be passed into the command line.
-Example Usage:
-```
-dxclient undeploy-portlet -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -xmlConfigPath <xmlConfigPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -xmlFile <xml-file-with-path>
-```
-Example Usage with dxProfileName and when enableBackup is set to true:
-```
-dxclient undeploy-portlet -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -xmlConfigPath <xmlConfigPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -xmlFile <xml-file-with-path> -enableBackup true -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxProfileName <Profile name of the DX core server profile>
-```
-Example Usage with dxProfilePath and when enableBackup is set to true:
-```
-dxclient undeploy-portlet -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -xmlConfigPath <xmlConfigPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -xmlFile <xml-file-with-path> -enableBackup true -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxProfilePath <Profile path of the DX core server profile>
-```
-### 3. XML Access
-The `xmlaccess` command is used to export or import pages or portlet configurations from a target HCL DX 9.5 CF 19 or higher server using a provided input XMLAccess file.
-Command Description:
-```
-dxclient xmlaccess -xmlFile <path>
-```
-**Help command**
-This command shows the help information for `xmlaccess` command usage:
-```
-dxclient xmlaccess -h
-```
-**Required files**
-```
-Xml file: This XML file should contain the configuration update or export operation for the web application
-```
-**Command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the DX server (wp_profile):
--hostname <value>
-	Use this attribute to specify the hostname of the target DX server:
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the DX server (wp_profile),for Kubernetes Environment dxPort is 443:
--xmlConfigPath <value>
-	Use this attribute to specify the path to DX configuration endpoint (e.g. /wps/config):
--dxUsername <value>
-	Use this attribute to specify the username to authenticate with the DX server (wp_profile):
--dxPassword <value>
-	Use this attribute to specify the password for the user in the "dxUsername" attribute:
--xmlFile <Absolute or relative path to xmlaccess input file>
-	Use this attribute to specify the local path to the XMLAccess file. Sample Files for creating or deleting pages can be found under the directory `dxclient/samples/sample-xml-files/`:
-```
-**Note:** Mandatory parameter xmlFile should be passed into the command line.
-Example usage:
-```
-dxclient xmlaccess -xmlFile <xml-file-with-path>
-```
-### 4. Deploy Script Application
-Deploy Script Application dxtool is  used to deploy the script based applications either from local or source environments to different target environments. This tool will push files that are associated with script-based applications to a Script Application instance in a Web Content Manager Site Library by running below commands.
-Commands Description
-```
-dxclient deploy-scriptapplication
-This command invokes the deploy-script-application tool inside the DXClient. This dxtool uses the provided files and executes the deploy script application task to the provided target DX server.
-```
-**Help command**
-This command shows the help document on the `deploy-scriptapplication` command:
-```
-dxclient deploy-scriptapplication pull -h
-dxclient deploy-scriptapplication push -h
-```
-**Command options**
-```
-push [OPTIONS]
-	Create or update the content of a Script Application in the DX server
-pull [OPTIONS]
-	Downloads the content of a Script Application present in the DX server
-```
-**Required options - Pull command**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol of the target server.
--hostname <value>
-	Use this attribute to specify the hostname of the target server.
--dxPort <value>
-	Use this attribute to specify the port of the target server(for Kubernetes Environment dxPort is 443).
--dxUsername <value>
-    The name of the dxUsername for authentication.
--dxPassword <value>
-    The password of the dxUsername for authentication.
--wcmContentID <value>
-    WCM content ID of the Script Application instance.
--virtualPortalContext <value>
-	The context of the virtual portal that contains the Script Application instance that you want to create or update.
--projectContext <value>
-	The context of the portal project that manages the publication of changes to the Script Application content.
-```
-**Required options - Push command**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol of the target server.
--hostname <value>
-	Use this attribute to specify the hostname of the target server.
--dxPort <value>
-	Use this attribute to specify the port of the target server(for Kubernetes Environment dxPort is 443).
--dxUsername <value>
-    The name of the dxUsername for authentication.
--dxPassword <value>
-    The password of the dxUsername for authentication.
--wcmContentName <value>
-    Name of the Script Application instance to be created or updated.
--wcmContentPath <value>
-    Full WCM path of the Script Application instance to be created or updated.
-	You cannot use this argument with -wcmSiteArea and -wcmContentName.
--wcmContentID <value>
-    WCM content ID only if you are updating an existing Script Application instance on a portal page.
--wcmContentTitle <value>
-    Sets or updates the title of the Script Application instance.
--wcmSiteArea <value>
-	SiteArea of the Script Application content.
--contenthandlerPath <value>
-	The path to the contenthandler servlet on the Script Application server.
--contentRoot <value>
-    Absolute or relative path to the Script Application's content.
--virtualPortalContext <value>
-	The context of the virtual portal that contains the Script Application instance that you want to create or update.
--projectContext <value>
-	The context of the portal project that manages the publication of changes to the Script Application content.
--prebuiltZip <value>
-    Path to an existing compressed file that provides the content to be pushed to the portal instead of the -contentRoot option.
-	Note: When -prebuiltZip is specified, the main HTML file path must be relative to the top-level directory in the compressed file.
--mainHtmlFile <value>
-   	Path to the main HTML file of the Script Application.
-**Note:** Mandatory parameters contentRoot and prebuiltZip should be passed into the command line.
-```
-Example Usage:
-```
-Script Application Pull , execute
-dxclient deploy-scriptapplication pull -wcmContentID <wcmContentID>
-The outputfile for pull will be generated inside store/outputFiles/sp-pull-output
-If the options are configured in dist/configuration/config.json, then execute
-dxclient deploy-scriptapplication pull
-dxclient deploy-scriptapplication push , execute
-dxclient deploy-scriptapplication push  -contentRoot /temp -wcmSiteArea "Script Application Library/Script Applications/" -wcmContentName DemoScriptApplication
-If the options are configured in dist/configuration/config.json, then execute
-dxclient deploy-scriptapplication push
-```
-### 5. Deploy Theme
-Deploy-theme command is used to create and update the existing theme into  target  DX Servers using the provided theme registration xml file, deployable EAR file and WebDAV theme collection.
-Commands Description
-```
-dxclient deploy-theme
-This command invokes the deploy-theme tool inside the DXClient. This command uses the provided files and execute the deploy theme task.
-```
-**Help command**
-This command shows the help document on the `deploy-theme` command usage:
-```
-dxclient deploy-theme -h
-```
-**Required files**
-```
-Theme Registration XML file: This XML file is required to register the theme into DX Server and should contain the details of the theme. The xml file referred in this file should be made reachable while executing the deploy theme task.
-Theme deployable EAR file: This EAR file containing theme data will be used for deploying it into  the WebSphere Application Server.
-WebDAV theme collection: The theme collection folder/zip will be used to create or update the collection in WebDAV file store of the DX Server.
 ```
-This command can execute below one or more tasks together:
-1. Theme Registration
-2. Theme EAR deployment
-3. WebDAV theme collection
+## All available commands
+| Command                                                           | Description                                            |
+|-------------------------------------------------------------------|--------------------------------------------------------|
+| [dxclient](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/)                                                          | Help document for the commands usage                   |
+| [dxclient version-compat](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/versionCompat/)                                           | Command to show version compatibility details          |
+| [dxclient accept-license](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/#dxclient-information-commands)                                           | Command to explicitly accept the license without prompt|
+| [dxclient deploy-portlet](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/portlets/#deploy-portlets) [options]                                 | Command to execute the deploy portlet action           |
+| [dxclient undeploy-portlet](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/portlets/#undeploy-portlets) [options]                               | Command to execute the undeploy portlet action         |
+| [dxclient xmlaccess](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/xmlaccess/) [options]                                      | Command to execute the xmlaccess action                |
+| [dxclient deploy-scriptapplication](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/scriptapplications/#deploy-script-applications) [options]                       | Command to execute the deploy script application action|
+| [dxclient undeploy-scriptapplication](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/scriptapplications/#undeploy-script-applications) [options]                     | Command to execute the undeploy script application action|
+| [dxclient restore-scriptapplication](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/scriptapplications/#restore-script-application) [options]                      | Command to execute the restore script application action|
+| [dxclient deploy-theme](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/themes/#deploy-theme) [options]                                   | Command to execute the deploy theme action             |
+| [dxclient undeploy-theme](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/themes/#undeploy-theme) [options]                                 | Command to execute the undeploy theme action           |
+| [dxclient deploy-application](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/deployapplication/) [options]                             | Command to execute the deploy application action       |
+| [dxclient undeploy-application](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/deployapplication/#undeploy-application) [options]                           | Command to execute the undeploy application action     |
+| [dxclient manage-syndicator](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/syndicatorsandsubscribers/) [options]                              | Command to execute the syndicator action               |
+| [dxclient manage-subscriber](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/syndicatorsandsubscribers/#managing-subscribers) [options]                              | Command to execute the subscriber action               |
+| [dxclient restart-dx-core](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/dxcoreserver/) [options]                                | Command to execute the DX Core restart action          |
+| [dxclient mls-export](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/wcm_mls_export_import/) [options]                                     | Command to export content of a WCM Library for translation|
+| [dxclient mls-import](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/wcm_mls_export_import/) [options]                                     | Command to import the translated contents into the DX   |
+| [dxclient manage-syndicator get-syndication-report](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/syndicatorsandsubscribers/#manage-syndicator-get-syndication-report) [options]       | Command to execute the syndication failed report|
+| [dxclient delete-dam-schema](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/usage/managing_dam/damschemas/#deleting-dam-schemas) [options]                              | Command to execute the delete dam schema action         |
+| [dxclient list-dam-schemas](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/usage/managing_dam/damschemas/#listing-dam-schemas) [options]                               | Command to execute the list of all dam schema action    |
+| [dxclient pzn-export](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/personalization/) [options]                                     | Command to export the pzn rules from the target server  |
+| [dxclient pzn-import](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/personalization/#import-pzn-rules) [options]                                     | Command to import the pzn rules into the target server  |
+| [dxclient resource-env-provider](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/resourceenvironments/) [options]                          | Command to create, update or delete a custom property from an existing Resource Environment Provider|
+| [dxclient manage-virtual-portal](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/virtualportals/) [options]                          | Command to manage virtual portal tasks in the DX server |
+| [dxclient manage-dam-staging register-dam-subscriber](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_subscription_staging/#registering-or-deregistering-for-dam-staging) [options]     | Command to execute the register subscriber action|
+| [dxclient manage-dam-staging trigger-staging](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_subscription_staging/#managing-dam-staging) [options]             | Command to execute the trigger staging action|
+| [dxclient manage-dam-staging deregister-dam-subscriber](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_subscription_staging/#registering-or-deregistering-for-dam-staging) [options]   | Command to execute the deregister subscriber action|
+| [dxclient manage-dam-staging get-all-subscribers](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_subscription_staging/#getting-all-subscribers-details-for-dam-staging) [options]         | Command to execute the get subscribers details action|
+| [dxclient manage-dam-staging update-secrets](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_subscription_staging/#updating-secrets-for-dam-staging) [options]              | Command to execute the update secrets action|
+| [dxclient manage-dam-staging find-staging-mismatch](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_staging_mismatch/) [options]       | Command to execute the find mismatch action|
+| [dxclient manage-dam-staging get-staging-mismatch-report](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_staging_mismatch/#download-mismatch-report) [options] | Command to generate staging mismatch report|
+| [dxclient manage-dam-staging start-staging-resync](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_staging_mismatch/#staging-resync) [options]        | Command to execute the staging resync action|
+| [dxclient manage-dam-staging delete-staging-mismatch](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/configuration/staging_dam/dam_staging_mismatch/#delete-staging-mismatch) [options]     | Command to execute the delete staging mismatch action|
+| [dxclient create-credential-vault](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/credentialvaultslot/) [options]                        | Command to create credential vault in the DX server    |
+| [dxclient wcm-library-export](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/wcmlibraries/) [options]                             | Command to export the wcm libraries from the target server|
+| [dxclient wcm-library-import](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/wcmlibraries/#import-wcm-libraries) [options]                             | Command to import the wcm libraries from the target server|
+| [dxclient dx-core-configuration-reports](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/dxcoreserver/#dx-core-server-configuration-report) [options]                  | Command to generate any dx core configuration reports|
+| [dxclient manage-dam-assets export-assets](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/usage/managing_dam/dam_exim/#export-dam-assets) [options]                | Command to export the dam assets                      |
+| [dxclient manage-dam-assets validate-assets](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/usage/managing_dam/dam_exim/#validate-exported-dam-assets) [options]              | Command to validate the dam assets                    |
+| [dxclient manage-dam-assets import-assets](https://opensource.hcltechsw.com/digital-experience/latest/manage_content/digital_assets/usage/managing_dam/dam_exim/#import-dam-assets) [options]                | Command to import the dam assets                      |
+| [dxclient restart-core-pods](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/dxcoreserver/#restart-dx-core-pods) [options]                              | Command to execute the Restart Core Pods action (for Kubernetes deployments)|
+| [dxclient livesync push-theme](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/livesync/) [options]                            | Command for watching a theme folder path live and syncs it in DX Server|
+| [dxclient livesync pull-theme](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/livesync/#livesync-pull-theme) [options]                            | Command for downloading theme files from DX Server to a target local theme folder|
+| [dxclient livesync pull-wcm-design-library](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/livesync/#livesync-pull-wcm-design-library) [options]               | Command for downloading WCM Design Library files from DX Server to a target local folder|
+| [dxclient livesync push-wcm-design-library](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/dxclient_artifact_types/livesync/#livesync-push-wcm-design-library) [options]               | Command watching a WCM Design Library folder path live and syncs it in DX Server|
+## Command options
+| Attribute                  | Description                                                                 |
+|----------------------------|-----------------------------------------------------------------------------|
+| -hostname [value]          | Use this attribute to specify the hostname of the target server              |
+| -dxConnectProtocol [value] | Use this attribute to specify the protocol with which to connect to the CW server |
+| -dxConnectUsername [value] | Use this attribute to specify the username that is required for authenticating to the cw_profile |
+| -dxConnectPassword [value] | Use this attribute to specify the password that is required for authenticating to the cw_profile |
+| -dxConnectPort [value]     | Use this attribute to specify the port number of the cw_profile (for Kubernetes Environment dxConnectPort is 443) |
+## Logger enablement
+### Enable Logger
+Logger can be enabled by setting parameter "enableLogger": true in the `config.json` file. If logger enabled then logger file will be generate in logs folder of the dxclient.
-**Common Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
+If logger enabled then logger file will be available in the below location:
+`store/logs/`
-Required options for Theme Registration:
+### Disable Logger
--xmlFile <xml file name with absolute path of the xmlaccess input file>
-	Use this attribute to specify the theme registration xml file that will be used while executing the deploy theme task. For an example, see the Theme-registration.xml file in the directory dxclient/samples/sample-xml-files/
+Logger can be disabled by setting parameter "enableLogger":false in the `config.json` file
--xmlConfigPath <value>
-	Use this attribute to specify the path to DX configuration endpoint
+### DXClient Release Timelines & Updates
-Required options for Theme EAR deployment:
+<details>
+  <summary>Show Changelog Details</summary>
+  1. If connecting to an HCL DX 9.5 CF19 deployment, the DXClient tool provides commands supporting the following artifact types along with the documentation
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
+  - deploy/undeploy portlets
+  - deploy script applications
+  - xmlaccess
+  - restore script application
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
+  2. If connecting to an HCL DX 9.5 CF192 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
+  - undeploy script applications
+  - deploy themes (EAR & WebDAV based)
--dxSoapPort <Soap port of the DX server>
-    Use this attribute to specify Soap port of the DX server
+  3. If connecting to an HCL DX 9.5 CF193 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
--dxProfileName <Profile name of the DX core server>
-    Use this attribute to specify the profile name of the DX core server
+  - restart application
+  - deploy application
+  - manage syndicator
+  - manage subscriber
--dxProfilePath <Profile Path of the DX core server>
-    Use this attribute to specify the profile path of the DX core server
+  4. If connecting to an HCL DX 9.5 CF195 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-–applicationFile <Absolute or relative path to deployable theme ear file>
-    Use this attribute to specify the theme ear file path that is required while executing the deploy theme task
+  - undeploy theme
--applicationName <value>
-    Use this attribute to specify the theme application name
+  5. If connecting to an HCL DX 9.5 CF196 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-Required options for creating/updating WebDAV theme collection:
+  - shared library
--themeName <value>
- Use this attribute to specify the theme name of the collection created under WebDav server in DX
--themePath <value>
- Use this attribute to specify the theme file path that contains all static files to be pushed into DX theme
+  6. If connecting to an HCL DX 9.5 CF197 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
--contenthandlerPath <value>
- Use this attribute to specify the path to the contenthandler servlet on the DX server (e.g. /wps/mycontenthandler):
+  - Get Syndication failed report
+  - Delete DAM schema
-Optional arguments:
+  7. If connecting to an HCL DX 9.5 CF198 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
- -requestId <Unique Id of a previously triggered deploy theme request>
- 	Use this attribute and retrigger the command to check the status of any previous request that was incomplete.
+  - Resource Environment Provider Updates - Create,update and delete
+  - Create/import/export/list of virtual portal
+  - Import and Export PZN
+  - List DAM schemas
-**Note:** Mandatory parameters applicationFile, applicationName, themeName, themePath and xmlFile should be passed into the command line.
-```
+  8. If connecting to an HCL DX 9.5 CF199 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-  Example Usage with dxProfileName:
-```
-dxclient deploy-theme -dxProtocol <http/https> -hostname <host-name> -dxPort <dxPort> -xmlConfigPath <xmlConfigPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -xmlFile <xml-file-with-path> -applicationFile <application-file-with-path> -applicationName <application name> -themeName <theme-name> -themePath <theme-path> -dxProfileName <Profile name of the DX core server>
-```
- Example Usage with dxProfilePath:
- ```
-dxclient deploy-theme -dxProtocol <http/https> -hostname <host-name> -dxPort <dxPort> -xmlConfigPath <xmlConfigPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -xmlFile <xml-file-with-path> -applicationFile <application-file-with-path> -applicationName <application name> -themeName <theme-name> -themePath <theme-path> -dxProfilePath <Profile path of the DX core server>
- ```
+  - Resource Environment Provider Updates - Export and Import
+  - Create Credential Vault Slot
+  - Create Syndication Relation
+  - DAM Staging - Register, Deregister and Trigger
-### 6. Undeploy Theme
+  9. If connecting to an HCL DX 9.5 CF200 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-undeploy-theme command is used to undeploy EAR application and undeploy WebDAV and unregister the registered theme from target DX server.
+  - WCM Libraries - Export and Import
+  - DX Core Configuration Reports - summary-report
-**Note**: If user sets the enableBackup as true then undeploy-theme will take the back up of deployed EAR theme,WebDAV theme collection and complete DX configuration export(not including users) and placed it in the backup folder. When the user is downloading EAR, WeDAV and XML to backup we seprate it by `store/outputFiles/themes/backup/foldername`.
+  10. If connecting to an HCL DX 9.5 CF201 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-example for backup of EAR, it is placed in `store/outputFiles/themes/backup/application`.
+  - An optional parameter requestId added to Deploy theme, Deploy application, Restart DX Core server, and Manage virtual portals.
+  - Retrieve feature added to the Resource environment provider.
+  - Accessing ConfigWizard in container environment
+  Note that a few parameters are deprecated and replaced with new parameters in the DX Core configuration reports. For information, see DX Core server configuration report.
-In case if undeployed theme is required,then user can restore the theme back using the back up files.
+  11. If connecting to an HCL DX 9.5 CF202 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-Commands Description
-```
-dxclient undeploy-theme
-This command invokes the undeploy-theme tool inside the DXClient. This command uses the provided files and execute the undeploy theme task.
-```
-**Required files**
-```
-Theme Unregistration XML file: This XML file is required to unregister the theme into DX Server and should contain the details of the theme. The xml file referred in this file should be made reachable while executing the undeploy theme task.
+  - Deprecated parameter dxConnectHostname. It is recommended that you start using the replacement parameter -hostname starting from CF202 wherever necessary.
+  - DAM Assets Export & import
-```
+  12. If connecting to an HCL DX 9.5 CF207 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
-This command can execute below one or more tasks together:
-1. Theme Unregistration
-2. Theme EAR undeploy
-3. WebDAV theme collection undeploy
+  - Support to set different Container Runtimes.
-**Common Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
+  13. If connecting to an HCL DX 9.5 CF208 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
+  - Get all subscribers details for DAM staging
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
+  14. If connecting to an HCL DX 9.5 CF209 deployment, the DXClient tool provides commands supporting the following additional artifact types along with the documentation
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
+  - Restart Core Pods in a Kubernetes Deployment
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
+  15. If connecting to an HCL DX 9.5 CF210 deployment, following changes are to be expected.
--contenthandlerPath <value>
- Use this attribute to specify the path to the contenthandler servlet on the DX server (e.g. /wps/mycontenthandler):
+  - Removed paramaters deprecated during CF201 & CF202 deployment.
+  - added ability to export/import wcm libraries in Virtual Portal.
--enableBackup <value>
- Use this attribute to take the backup before undeploying theme
+  16. If connecting to an HCL DX 9.5 CF211 deployment, following changes are to be expected.
-**Note** : User can sets the sets the enableBackup as true to take backup before undeploying, enableBackup is set to false by default.
+  - Deploy and Undeploy Applications
-Required options for Theme Unregistration:
+  17. If connecting to an HCL DX 9.5 CF213 deployment, following changes are to be expected.
--xmlFile <xml file name with absolute path of the xmlaccess input file>
-	Use this attribute to specify the theme registration xml file that will be used while executing the undeploy theme task. For an example, see the Theme-registration.xml file in the directory dxclient/samples/
+  - Livesync of WebDAV based Themes
--xmlConfigPath <value>
-	Use this attribute to specify the path to DX configuration endpoint
+  18. If connecting to an HCL DX 9.5 CF214 deployment, following changes are to be expected.
-Required options for Theme EAR and WebDAV undeployment:
+  - Livesync Improvements
+    - List themes during Pull theme in case themeName is not provided.
+    - Livesync is now supported in scaled DX environment setups
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
+  19. If connecting to an HCL DX 9.5 CF216 deployment, following changes are to be expected.
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
+  - Show Version compatibility details between DXCore and DXClient
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
+  20. If connecting to an HCL DX 9.5 CF219 deployment, following changes are to be expected.
--dxSoapPort <Soap port of the DX server>
-    Use this attribute to specify Soap port of the DX server
+  - Enabled multiple environment configuration in node version
--dxProfileName <Profile name of the DX core server profile>
-    Use this attribute to specify the profile name of the DX core server
+  21. If connecting to an HCL DX 9.5 CF221 deployment, following changes are to be expected.
--dxProfilePath <Profile path of the DX core server profile>
-    Use this attribute to specify the profile path of the DX core server
+  - DXClient Version Type(Node/Container) information available using help/version-compat commands
+  - A one time license agreement click-through is enabled. To skip the prompt, use "accept-license" command.
+  - DXClient will be openly distributed in NPMJS & Harbor repository.
--applicationName <value>
-    Use this attribute to specify the EAR application name
+  22. If connecting to an HCL DX 9.5 CF224 deployment, following changes are to be expected.
--themeName <value>
- Use this attribute to specify the theme name of the collection created under WebDAV
-**Note:** Mandatory parameters applicationName, themeName and xmlFile should be passed into the command line.
-```
+  - LiveSync Pull and Push commands for WCM Design Library are now available for HTML and Folder Components.
-  Example Usage with dxProfileName:
-```
-dxclient undeploy-theme -dxProtocol <http/https> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -xmlFile <xml-file-with-path> -applicationName <application name> -themeName <theme-name> -enableBackup <enable-backup> -dxProfileName <Profile name of the DX core server profile>
-```
- Example Usage with dxProfilePath:
-```
-dxclient undeploy-theme -dxProtocol <http/https> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -xmlFile <xml-file-with-path> -applicationName <application name> -themeName <theme-name> -enableBackup <enable-backup> -dxProfilePath <Profile path of the DX core server profile>
-```
+  23. If connecting to an HCL DX 9.5 CF225 deployment, following changes are to be expected.
-### 7. Undeploy Script Application
+  - LiveSync now supports Presentation Templates.
-Undeploy Script Application command is used to un-deploy an existing or delete the newly deployed script application from the target DX Server.
+  24. If connecting to an HCL DX 9.5 CF226 deployment, following changes are to be expected.
-**Note:**
-Undeploy script application will take the back up of an already deployed script application, if user has set "enableBackup" as true in the configuration file and deletes it. The backup files are placed under the `store/outputFiles/scriptApplications/backup/{wcmContentId}` by default.
+  - DXClient no longer ignores certificates that cannot be properly validated when using Transport Layer Security (TLS) connections
+  - New documented limitations for LiveSync
+  - Updated scripts to pass certificates to container.
-Commands Description
-```
-dxclient undeploy-scriptapplication
-This command invokes the undeploy-scriptapplication tool inside the DXClient. The undeploy-scriptapplication dxtool uses the provided files and execute the undeploy scriptapplication task.
-```
-**Help command**
-This command shows the help information for `undeploy-scriptapplication` command usage:
-```
-dxclient undeploy-scriptapplication -h
-```
-**Required command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server.
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server.
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443).
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server.
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server.
--wcmContentID <value>
-    WCM content ID only if you are updating an existing Script Application instance on a portal page.
--contenthandlerPath <value>
-	The path to the contenthandler servlet on the Script Application server.
--virtualPortalContext <value>
-	The context of the virtual portal that contains the Script Application instance that you want to create or update.
--projectContext <value>
-	The context of the portal project that manages the publication of changes to the Script Application content.
--f
- The -f flag is to delete the Script Application forcefully overstepping the prompt.
-```
- Example Usage:
-```
-dxclient undeploy-scriptapplication -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -wcmContentID <wcmContentID> -f
-```
-## 8.Restore Script Application
-Restore Script Application command is used to restore the script application into one of its previous versions already present in the target DX Server.
-Commands Description
-```
-dxclient restore-scriptapplication
-This command invokes the restore-scriptapplication tool inside the DXClient. The restore-scriptapplication dxtool uses the provided files and execute the restore scriptapplication task.
-```
-**Help command**
-This command shows the help information for `restore-scriptapplication` command usage:
-```
-dxclient restore-scriptapplication -h
-```
-**Required command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--wcmContentID <value>
-    WCM content ID only if you are updating an existing Script Application instance on a portal page.
--contenthandlerPath <value>
-	The path to the contenthandler servlet on the Script Application server.
--virtualPortalContext <value>
-	The context of the virtual portal that contains the Script Application instance that you want to create or update.
--projectContext <value>
-	The context of the portal project that manages the publication of changes to the Script Application content.
--versionName <value>
-	Use this attribute to specify the versionname that is restore version of Script Application.
-	Note: When -versionName is not specified, the script application will rollback to the previous version default.
--restoreAsPublished <value>
-	Use this attribute to specify the restore as a draft or replace the published version of Script Application.
-```
- Example Usage:
-```
-dxclient restore-scriptapplication -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -wcmContentID <wcmContentID> -versionName <versionName> -restoreAsPublished <restoreAsPublished>
-```
-### 9. Export Content of a WCM Library
-The export command is used to export the content of a wcm library for translation into a .csv file at the location specified by the user.
-Commands Description
-```
-dxclient mls-export
-The export command would create a new .csv file with an auto-generated file name in a file path specified by the user every-time the export command is run.
-```
-**Required command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the DX server
--hostname <value>
-	Use this attribute to specify the hostname of the DX server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the DX server
--contenthandlerPath <value>
-	Use this attribute to specify the path to the contenthandler servlet on the DX server (e.g. /wps/mycontenthandler)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--wcmLibraryId <value>
-    WCM library ID(s) within quotation("") to export the contents of the library. For multiple WCM library ids, enter separated by comma.
--wcmLibraryName <value>
-    Provide the WCM library name(s) within quotation("") to export the contents of the library. For multiple WCM library name, enter separated by comma.
--lastModifiedAfter <value>
-    Last modified after will give the contents of WCM library id and name from specified date and time in GMT format.
--wcmProjectName <value>
-    Optional attribute: Provide the WCM project name within quotation("") to export the contents of the project.
--exportPath <value>
-		The path to the exports the wcm contents of a library.
--virtualPortalContext <value>
-		The context of the virtual portal from which mls library should be exported.
-**Note:** Mandatory parameter exportPath should be passed into the command line.
-```
- Example Usage:
-```
-To Export contents from Library :
-dxclient mls-export -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort>
--contenthandlerPath <contenthandlerPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -wcmLibraryId <wcmLibraryId> -wcmLibraryName <wcmLibraryName> -lastModifiedAfter <lastModifiedAfter> -exportPath <exportPath> -virtualPortalContext <virtualPortalContext>
-To Export contents from Project :
-dxclient mls-export -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort>
--contenthandlerPath <contenthandlerPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -wcmProjectName <wcmProjectName> -exportPath <exportPath> -virtualPortalContext <virtualPortalContext>
-```
-### 10. Import Translated Contents into DX
-The import command is used to import the translated contents into DX at the location specified by the user.
-Commands Description
-```
-dxclient mls-import
-The import command imports the translated contents into DX and It would overwrite any translations which are already present in the content of the environment.
-```
-**Required command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the DX server
--hostname <value>
-	Use this attribute to specify the hostname of the DX server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the DX server
--contenthandlerPath <value>
-	Use this attribute to specify the context root on which to connect to the DX server
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--importPath <value>
-	The path(s) (separated by comma) to import the translated contents into DX.
--wcmProjectName <value>
-	Optional attribute: Provide the WCM project name within quotation("") to export the contents of the project.
--forceImport <value>
-	Optional attribute: Flag to forcefully import the content. This allows the import process to proceed even if the content is modified in the DX since the last export. (e.g. true or false)
--virtualPortalContext <value>
-	The context of the virtual portal to which mls library should be imported.
-**Note:** Mandatory parameter importPath should be passed into the command line.
-```
- Example Usage:
-```
-dxclient mls-import -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort>
--contenthandlerPath <contenthandlerPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -importPath <importPath> -wcmProjectName <wcmProjectName> -virtualPortalContext <virtualPortalContext>
-```
-Editable fields in CSV files
-In the exported CSV file, you can only edit the following fields: **target**, **title**, and **description**.
-Maximum data length for importing the translated contents:
-```
-Only ShortTextComponent element type has an explicit maximum data length defined as 250 characters. Import command would validate the length of the data for this particular element type before proceeding with the actual import flow. Any errors due to custom configuration of limits are caught by the import/export during the execution cycle and the error log is reported.
-```
-CSV file length limits
-```
-Only ShortTextComponent element type has an explicit maximum data length defined as 250 characters. And this limit is seen by users in the CSV file as new column called fieldLimit is added.
-```
-Link field to see translators content
-```
-User can just preview the link of the portal content directly from the CSV file as new column called previewLink is added.
-```
-Content information data
-```
-Content specific information rows namely title and description has been provided in the CSV file. User can edit the title and description of the content while importing the contents to portal.
-```
-### 11. Deploy Application
-Deploy-application command is used to deploy EAR file into the WebSphere Application Server.
-Commands Description
-```
-dxclient deploy-application
-This command invokes the deploy-application tool inside the DXClient. This command uses the provided files and execute the deploy application task.
-```
-**Help command**
-This command shows the help information for `deploy-application` command usage:
-```
-dxclient deploy-application -h
-```
-**Required files**
-```
-Deployable EAR file: This EAR file will be used for deploying it into  the WebSphere Application Server.
-```
-**Common Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
-Required options for application deployment:
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxSoapPort <Soap port of the DX server>
-    Use this attribute to specify Soap port of the DX server
--dxProfileName <Profile name of the DX core server>
-    Use this attribute to specify the profile name of the DX core server
--dxProfilePath <Profile path of the DX core server>
-    Use this attribute to specify the profile path of the DX core server
-–applicationFile <Absolute or relative path to deployable ear file>
-    Use this attribute to specify the ear file path that is required while executing the deploy application task
--applicationName <value>
-    Use this attribute to specify the application name
-Optional arguments:
--requestId <Unique Id of a previously triggered deploy application request>
- 	Use this attribute and retrigger the command to check the status of any previous request that was incomplete.
-**Note:** Mandatory parameters applicationFile and applicationName should be passed into the command line.
-```
-  Example Usage with dxProfileName:
-```
-dxclient deploy-application -dxProtocol <http/https> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -applicationFile <application-file-with-path> -applicationName <application name> -dxProfileName <Profile name of the DX core server>
-```
- Example Usage with dxProfilePath:
-```
-dxclient deploy-application -dxProtocol <http/https> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -applicationFile <application-file-with-path> -applicationName <application name> -dxProfilePath <Profile path of the DX core server>
-```
-### 12. Restart DX Core
-restart-dx-core command is used to restart the DX Core server.
-**Note:** It is not recommended to run this command in Kubernetes based deployments. To restart all the pods, use the Kubernetes interfaces like kubectl.
-Commands Description
-```
-dxclient restart-dx-core
-This command invokes the restart-dx-core tool inside the DXClient and executes the DX Core restart action.
-```
-**Help command**
-This command shows the help information for `restart-dx-core` command usage:
-```
-dxclient restart-dx-core -h
-```
-**Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the DX Core
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the DX Core
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxProfileName <Profile name of the DX core server>
-    Use this attribute to specify the profile name of the DX Core server
--dxProfilePath <Profile path of the DX core server>
-    Use this attribute to specify the profile path of the DX Core server
-Optional arguments:
--requestId <Unique Id of a previously triggered restart request>
-	Use this attribute and retrigger the command to check the status of any previous request that was incomplete.
-```
-  Example Usage with dxProfileName:
-```
-dxclient restart-dx-core -hostname <host-name> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxProfileName <Profile name of the DX core server>
-```
- Example Usage with dxProfilePath:
-```
-dxclient restart-dx-core -hostname <host-name> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxProfilePath <Profile path of the DX core server>
-```
-### 13. Manage Syndicator
-manage-syndicator command is used to enable/disable syndicator in the target server.
-Commands Description
-```
-dxclient manage-syndicator
-This command invokes the manage-syndicator tool inside the DXClient. The manage-syndicator dxtool is used to enable/disable syndicator.
-```
-**Help command**
-This command shows the help information for `manage-syndicator` command usage:
-```
-dxclient manage-syndicator -h
-```
-**Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--contenthandlerPath <value>
- Use this attribute to specify the path to the contenthandler servlet on the DX server (e.g. /wps/mycontenthandler)
--UUID <value>
-	Use this attribute to specify the UUID of the syndicator instance
--enable <value>
-	Use this attribute to specify the enable/disable the syndicator instance. This value can be true or false. If true then enable the syndicator otherwise it will disable the syndicator
-```
- Example Usage:
-```
-dxclient manage-syndicator -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -contenthandlerPath <contenthandlerPath> -UUID <UUID> -enable <enable>
-```
-### 14. Manage Subscriber
-manage-subscriber command is used to enable/disable subscriber in the target server.
-Commands Description
-```
-dxclient manage-subscriber
-This command invokes the manage-subscriber tool inside the DXClient. The manage-subscriber dxtool is used to enable/disable subscriber.
-```
-**Help command**
-This command shows the help information for `manage-subscriber` command usage:
-```
-dxclient manage-subscriber -h
-```
-**Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--contenthandlerPath <value>
- Use this attribute to specify the path to the contenthandler servlet on the DX server (e.g. /wps/mycontenthandler)
--UUID <value>
-	Use this attribute to specify the UUID of the subscriber instance
--enable <value>
-	Use this attribute to specify the enable/disable the subscriber instance. This value can be true or false. If true then enable the subscriber otherwise it will disable the subscriber
-```
- Example Usage:
-```
-dxclient manage-subscriber -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -contenthandlerPath <contenthandlerPath> -UUID <UUID> -enable <enable>
-```
-### 15. Manage-syndicator get-syndication-report
-Manage-syndicator get-syndication-report command is used to fetch the syndicator failed reports.
-Commands Description
-```
-dxclient manage-syndicator get-syndication-report
-This command invokes the report generation of items that failed to syndicate in DX through DXClient. If the user provides syndicator UUID it will fetch the report of items that failed to syndicate with respect to the UUID, otherwise, it will display items that failed to syndicate for all syndicators present in the DX environment provided. The report is available in HTML format.
-```
-**Help command**
-This command shows the help information for `manage-syndicator get-syndication-report` command usage:
-```
-dxclient  manage-syndicator get-syndication-report -h
-```
-**Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--contenthandlerPath <value>
-    Use this attribute to specify the path to the contenthandler servlet on the DX server (e.g. /wps/mycontenthandler)
--UUID <value>
-	Use this attribute to specify the UUID of the syndicator instance
-```
- Example Usage with UUID:
-```
-dxclient manage-syndicator get-syndication-report -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -contenthandlerPath <contenthandlerPath> -UUID <UUID>
-```
- Example Usage without UUID:
- ```
-dxclient manage-syndicator get-syndication-report -dxProtocol <dxProtocol> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -contenthandlerPath <contenthandlerPath>
-```
-### 16. Shared Library
-shared-library command is used to manage files in the shared library. The sub-command upload is used to `upload` jar files and sub-command `delete` is used to delete the files from the default shared library location provided below.
-Default shared Library: DXCLib
-Default shared library location: <dx-profile>/PortalServer/sharedLibrary
-Commands Description
-```
-dxclient shared-library upload
-This command invokes the shared library upload task inside the DXClient. This is used to upload jar files into the default shared library location.
-```
-```
-dxclient shared-library delete
-This command invokes the shared library delete task inside the DXClient. This is used to delete jar files from the default shared library location.
-```
-**Help command**
-This command shows the help information for `shared-library upload` command usage:
-```
-dxclient shared-library upload -h
-```
-This command shows the help information for `shared-library delete` command usage:
-```
-dxclient shared-library delete -h
-```
-**Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxProfileName <Profile name of the DX core server>
-    Use this attribute to specify the profile name of the DX Core server
-Command option for Upload
--libFilePath <value>
-	Use this attribute to specify the path to a jar/zip file or folder containing jars in it.
-Command option for Delete
--libFileNames <value>
-	Use this attribute to specify the names of the jar files present in the shared library location on the server (e.g. "abc.jar,sample.jar,test.jar")
-**Note:** Mandatory parameter libFilePath should be passed into the command line.
-For upload, The folder/zip should contain only jars files that are to be  uploaded to the default shared library location
-```
- Example Usage:
-```
-dxclient shared-library upload -hostname <host-name> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxProfileName <Profile name of the DX Server> -libFilePath <path to jar/zip/Folder>
-dxclient shared-library delete -hostname <host-name> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxProfileName <Profile name of the DX Server> -libFileNames <file names>
-```
-### 17. Delete DAM schema
-Delete-dam-schema command is used to delete inactive DAM schema from persistence.
-Commands Description
-```
-dxclient delete-dam-schema
-```
-**Help command**
-This command shows the help information for `delete-dam-schema` command usage:
-```
-dxclient delete-dam-schema -h
-```
-**Command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--damAPIPort <value>
-	Use this attribute to specify the port number of the DAM server(for Kubernetes Environment default port is 443 )
--ringAPIPort <value>
-	Use this attribute to specify the port number of the DX Core API server(for Kubernetes Environment default port is 443 )
--damAPIVersion <value>
-	Use this attribute to specify the API Version number of DAM(for Kubernetes Environment default port is 443 )
--ringAPIVersion <value>
-	Use this attribute to specify the API Version number of DX Core(for Kubernetes Environment default port is 443 )
--schemaVersion <value>
-	Use this attribute to specify the DAM Schema Version(for Kubernetes Environment default port is 443 )
-	Note : In case if the user do not enter the schemaVersion, it will prompt the user with a list of inactive schemas to select from and proceed forward.
-```
- Example Usage:
-```
-dxclient delete-dam-schema -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -ringAPIVersion <ringAPIVersion> -damAPIVersion <damAPIVersion> -schemaVersion <schemaVersion>
-```
-### 18. List DAM schema
-list-dam-schemas command is used to list of all DAM schema.
-Commands Description
-```
-dxclient list-dam-schemas
-```
-**Help command**
-This command shows the help information for `list-dam-schemas` command usage:
-```
-dxclient list-dam-schemas -h
-```
-**Command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--damAPIPort <value>
-	Use this attribute to specify the port number of the DAM server(for Kubernetes Environment default port is 443 )
--ringAPIPort <value>
-	Use this attribute to specify the port number of the DX Core API server(for Kubernetes Environment default port is 443 )
--damAPIVersion <value>
-	Use this attribute to specify the API Version number of DAM(for Kubernetes Environment default port is 443 )
--ringAPIVersion <value>
-	Use this attribute to specify the API Version number of DX Core(for Kubernetes Environment default port is 443 )
-```
- Example Usage:
-```
-dxclient list-dam-schemas -dxProtocol <dxProtocol> -hostname <hostname> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -ringAPIVersion <ringAPIVersion> -damAPIVersion <damAPIVersion>
-```
-### 19. PZN Export
-The `pzn-export` command is used to export the rules from the source server to a user-specified location.
-Command Description:
-```
-dxclient pzn-export
-```
-**Help command:**
-This command shows the help information for `pzn-export` command usage:
-```
-dxclient pzn-export -h
-```
-**Command options:**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the DX server
--hostname <value>
-	Use this attribute to specify the hostname of the target DX server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the DX server ,for Kubernetes Environment dxPort is 443
--dxUsername <value>
-	Use this attribute to specify the username to authenticate with the DX server
--dxPassword <value>
-	Use this attribute to specify the password for the user in the "dxUsername" attribute
--targetPath <value>
-	Use this attribute to specify the rule or folder containing the rules in the target workspace (default targetPath is '/'), which is the parent for the published nodes. The target path must exist before publishing
--targetWorkspace <value>
-	Use this attribute to specify the name of the workspace containing the rules in DX server (default targetWorkspace is 'ROOTWORKSPACE')
--dxContextRoot <value>
- 	Use this attribute to specify the path to the context root on the DX server (e.g. /wps):
-```
-**Note:** targetPath and targetWorkspace are optional parameters. If the user does not pass the respective parameters then the default value will be taken.
-Example usage:
-```
-dxclient pzn-export -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxContextRoot <dxContextRoot>
-The outputfile for pzn export will be generated inside store/outputFiles/pznrules
-```
-### 20. PZN Import
-The `pzn-import` command is used to import the rules from the source server into the target server.
-Command Description:
-```
-dxclient pzn-import
-```
-**Help command:**
-This command shows the help information for `pzn-import` command usage:
-```
-dxclient pzn-import -h
-```
-**Required files**
-```
-Rules file: This file should contain the configuration XML representation of all the currently selected personalization objects.
-```
-**Command options:**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the DX server
--hostname <value>
-	Use this attribute to specify the hostname of the target DX server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the DX server ,for Kubernetes Environment dxPort is 443
--dxUsername <value>
-	Use this attribute to specify the username to authenticate with the DX server
--dxPassword <value>
-	Use this attribute to specify the password for the user in the "dxUsername" attribute
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--rulesFilePath <Absolute or relative path to import nodes file>
-    Use this attribute to specify the path to the file containing the rules to be imported
--targetPath <value>
-	Use this attribute to specify the rule or folder containing the rules in the target workspace (default targetPath is '/'), which is the parent for the published nodes. The target path must exist before publishing
--targetWorkspace <value>
-	Use this attribute to specify the name of the workspace containing the rules in DX server (default targetWorkspace is 'ROOTWORKSPACE')
--dxContextRoot <value>
-   Use this attribute to specify the path to the context root on the DX server (e.g. /wps):
-```
-**Note:** dxProtocol, hostname, dxPort, targetWorkspace and targetPath are optional parameters. If the user does not pass the respective parameters then the default value will be taken.
-Example usage:
-```
-dxclient pzn-import -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxConnectPort <dxConnectPort> -rulesFilePath <rulesFilePath> -dxContextRoot <dxContextRoot>
-```
-### 21. Resource Environment Provider
-The `resource-env-provider` command is used to create, update, delete, export or import custom properties from an existing Resource Environment Provider.
-Commands Description:
-```
-dxclient resource-env-provider
-```
-**Help command:**
-This command shows the help information for `resource-env-provider` command usage:
-```
-dxclient resource-env-provider -h
-```
-```
-dxclient resource-env-provider create-property -h
-dxclient resource-env-provider update-property -h
-dxclient resource-env-provider delete-property -h
-dxclient resource-env-provider export-properties -h
-dxclient resource-env-provider import-properties -h
-dxclient resource-env-provider retrieve-property -h
-```
-**Commands**
-```
-resource-env-provider create-property [OPTIONS]
-	Create a custom property from an existing Resource Environment Provider
-resource-env-provider update-property [OPTIONS]
-	Update a custom property from an existing Resource Environment Provider
-resource-env-provider delete-property [OPTIONS]
-	Delete a custom property from an existing Resource Environment Provider
-resource-env-provider export-properties [OPTIONS]
-	Export all the existing Resource Environment Provider
-resource-env-provider import-properties [OPTIONS]
-	Import all the existing Resource Environment Provider
-resource-env-provider retrieve-property [OPTIONS]
-	Retrieve a property from an existing Resource Environment Provider
-```
-**Required options for create, update or delete property Command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--providerName <value>
-  Use this attribute to specify the name of the Resource Environment Provider
--propertyName <value>
-  Use this attribute to specify the name of the Custom Property
--propertyValue <value>
-  Use this attribute to specify the value of the Custom Property
--propertyDesc <value>
-  Use this attribute to specify the description of the Custom Property
-```
-**Required options for export properties Command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxWASUsername <value>
-	Use this attribute to specify the username of the DX WAS server
--dxWASPassword <value>
-	Use this attribute to specify the password of the DX WAS server
--dxProfileName <Profile name of the DX core server>
-  Use this attribute to specify the profile name of the DX core server
-```
-**Required options for import properties Command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxWASUsername <value>
-	Use this attribute to specify the username of the DX WAS server
--dxWASPassword <value>
-	Use this attribute to specify the password of the DX WAS server
--dxProfileName <Profile name of the DX core server>
-  Use this attribute to specify the profile name of the DX core server
--filePath <value>
-  Use this attribute to specify the File path of the import Resource Environment Provider files.
-```
-Example Usage:
-```
-dxclient resource-env-provider create-property -providerName <providerName> -propertyName <propertyName> -propertyValue <propertyValue>
-dxclient resource-env-provider update-property -providerName <providerName> -propertyName <propertyName> -propertyValue <modifiedpropertyValue>
-dxclient resource-env-provider delete-property -providerName <providerName> -propertyName <propertyName> -propertyValue <modifiedpropertyValue>
-dxclient resource-env-provider export-properties -dxProfileName <dxProfileName>
-dxclient resource-env-provider import-properties -dxProfileName <dxProfileName> -filePath <filePath>
-dxclient resource-env-provider retrieve-property -providerName <providerName> -propertyName <propertyName>
-```
-### 22. Manage virtual Portal
-The `manage-virtual-portal` command is used to create, list ,export and import of virtual portal in the DX server.
-Commands Description
-```
-dxclient manage-virtual-portal
-```
-**Help command**
-This command shows the help document on the `manage-virtual-portal` command:
-```
-dxclient manage-virtual-portal create -h
-dxclient manage-virtual-portal list -h
-dxclient manage-virtual-portal import -h
-dxclient manage-virtual-portal export -h
-```
-**Commands**
-```
-manage-virtual-portal create [OPTIONS]
-	Create virtual portal task in the DX server
-manage-virtual-portal list [OPTIONS]
-	List virtual portal task in the DX server
-manage-virtual-portal import [OPTIONS]
-	Import virtual portal task in the DX server
-manage-virtual-portal export [OPTIONS]
-	Export virtual portal task in the DX server
-```
-**Required options - `manage-virtual-portal create` command**
-```
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxProfileName <Profile name of the DX core server>
-  Use this attribute to specify the profile name of the DX core server
--dxWASUsername <value>
-	Use this attribute to specify the username of the DX WAS server
--dxWASPassword <value>
-	Use this attribute to specify the password of the DX WAS server
--vpTitle <value>
-	Use this attribute to specify the  virtual portal Title
--vpRealm <value>
-	Use this attribute to specify the virtual portal Realm
--vpAdminGroup <value>
-	Use this attribute to specify the virtual portal AdminGroup
--vpHostname <value>
-	Use this attribute to specify the virtual portal Hostname
--vpContext <value>
-	Use this attribute to specify the virtual portal Context
-Optional arguments:
--requestId <Unique Id of a previously triggered create virtual portal request>
-	Use this attribute and retrigger the command to check the status of any previous request that was incomplete.
-```
-Example Usage:
-```
- dxclient manage-virtual-portal create -hostname <hostname> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxProfileName <Profile name of the DX Server> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxWASUsername < Username of the DX WAS server> -dxWASPassword <Password of the DX WAS server> -vpTitle <virtual-portal-Title> -vpRealm <virtual-portal-realm>  -vpAdminGroup <virtual-portal-adminGroup> -vpHostname <virtual-portal-hostname> -vpContext <virtual-portal-context>
-```
-**Required options - `manage-virtual-portal list` command**
-```
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxProfileName <Profile name of the DX core server>
-  Use this attribute to specify the profile name of the DX core server
--dxWASUsername <value>
-	Use this attribute to specify the username of the DX WAS server
--dxWASPassword <value>
-	Use this attribute to specify the password of the DX WAS server
-```
-Example Usage:
-```
-dxclient manage-virtual-portal list -hostname <hostname> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxProfileName <profile-name-of-the-DX-server> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxWASUsername <username-of-the-DX-WAS-server> -dxWASPassword <password-of-the-DX-WAS-server>
-```
-**Required options - `manage-virtual-portal import` command**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--xmlConfigPath <value>
-	Use this attribute to specify the path to DX configuration endpoint (e.g. /wps/config)
--xmlFile <value>
-	Use this attribute to specify the xml file name with absolute path of the input file
--vpContext <value>
-	Use this attribute to specify the virtual portal Context
-```
-Example Usage:
-```
-dxclient manage-virtual-portal import -dxProtocol <http/https> -hostname <host-name> -dxPort <dxPort> -xmlConfigPath <xmlConfigPath> -dxUsername <dxUsername> -dxPassword <dxPassword>  -xmlFile <xml-file-with-path> -vpContext <virtual-portal-context>
-```
-**Required options - `manage-virtual-portal export` command**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--xmlConfigPath <value>
-	Use this attribute to specify the path to DX configuration endpoint (e.g. /wps/config)
--vpContext <value>
-	Use this attribute to specify the virtual portal Context
--vpTitle <value>
-	Use this attribute to specify the  virtual portal Title
--xmlFile <value>
-	Use this attribute to specify the xml file name with absolute path of the input file to export the virtual portal content.
-```
-**Note:** Currently export virtual portal supports only vpContext and does not support vpHostname. Support for Virtual portal with hostname can be added in future release.
-Example Usage:
-```
-dxclient manage-virtual-portal export -hostname <hostname> -dxProtocol <dxProtocol> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -vpTitle <vpTitle> -vpContext <vpContext>
-```
-### 23. Manage dam staging subscriber register
-manage-dam-staging register-dam-subscriber command is used to register the subscriber for dam staging.
-Commands Description
-```
-dxclient manage-dam-staging register-dam-subscriber
-```
-**Help command**
-This command shows the help information for `manage-dam-staging register-dam-subscriber` command usage:
-```
-dxclient manage-dam-staging register-dam-subscriber -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-    Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-    Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-    Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-    Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-    Password of the DX server of the publisher (default: "")
--targetServerUsername, --targetServerUsername <value>
-    Username of the DX server of the subscriber (default: "")
--targetServerPassword, --targetServerPassword <value>
-    Password of the DX server of the subscriber (default: "")
--damAPIPort, --damAPIPort <value>
-    Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-    Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-    API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-    API Version number of DX Core API server of the publisher (default: "")
--targetHostname, --targetHostname <value>
-    Host name of the target environment of the subscriber
--interval,--interval <value>
-    Interval between two sync cycles. The unit of interval is minute. Default value of interval is 2 minutes.
-```
-Example usage:
-```
-dxclient manage-dam-staging register-dam-subscriber -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -targetServerUsername <targetServerUsername> -targetServerPassword <targetServerPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion> -targetHostname <targetHostname> -interval <interval>
-```
-24. Manage dam staging update secrets
-manage-dam-staging update-secrets command is used to update publisher & subscriber secrets for dam staging.
-Commands Description
-```
-dxclient manage-dam-staging update-secrets
-```
-**Help command**
-This command shows the help information for `manage-dam-staging update-secrets` command usage:
-```
-dxclient manage-dam-staging update-secrets -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-    Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-    Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-    Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-    Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-    Password of the DX server of the publisher (default: "")
--targetServerUsername, --targetServerUsername <value>
-    Username of the DX server of the subscriber (default: "")
--targetServerPassword, --targetServerPassword <value>
-    Password of the DX server of the subscriber (default: "")
--damAPIPort, --damAPIPort <value>
-    Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-    Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-    API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-    API Version number of DX Core API server of the publisher (default: "")
--targetHostname, --targetHostname <value>
-    Host name of the target environment of the subscriber
--interval,--interval <value>
-    Interval between two sync cycles. The unit of interval is minute. Default value of interval is 2 minutes.
-```
-Example usage:
-```
-dxclient manage-dam-staging update-secrets -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -targetServerUsername <targetServerUsername> -targetServerPassword <targetServerPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion> -targetHostname <targetHostname> -interval <interval>
-```
-### 25. Manage dam staging trigger
-manage-dam-staging trigger-staging command is used to trigger the DAM staging.
-Commands Description
-```
-dxclient manage-dam-staging trigger-staging
-```
-**Help command**
-This command shows the help information for `manage-dam-staging trigger-staging` command usage:
-```
-dxclient manage-dam-staging trigger-staging -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-    Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-    Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-    Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-    Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-    Password of the DX server of the publisher (default: "")
--damAPIPort, --damAPIPort <value>
-    Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-    Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-    API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-    API Version number of DX Core API server of the publisher (default: "")
--targetHostname, --targetHostname <value>
-    Host name of the target environment of the subscriber
-```
-Example usage:
-```
-dxclient manage-dam-staging trigger-staging -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion> -targetHostname <targetHostname>
-```
-### 26. Manage dam staging subscriber deregister
-manage-dam-staging deregister-dam-subscriber command is used to deregister subscriber.
-Commands Description
-```
-dxclient manage-dam-staging deregister-dam-subscriber
-```
-**Help command**
-This command shows the help information for `manage-dam-staging deregister-dam-subscriber` command usage:
-```
-dxclient manage-dam-staging deregister-dam-subscriber -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-    Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-    Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-    Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-    Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-    Password of the DX server of the publisher (default: "")
--damAPIPort, --damAPIPort <value>
-    Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-    Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-    API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-    API Version number of DX Core API server of the publisher (default: "")
--subscriberId, --subscriberId <value>
-    Subscriber id of the target environment of the subscriber
-```
-Example usage:
-```
-dxclient manage-dam-staging deregister-dam-subscriber -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion> -subscriberId <subscriberId>
-```
-### 27. Create syndication relation
-Create syndication relation command is used to create the relation between syndicator and subscriber in DX server.
-Commands Description
-```
-dxclient create-syndication-relation
-```
-**Help command**
-This command shows the help information for `create-syndication-relation` command usage:
-```
-dxclient create-syndication-relation -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-    Protocol of the DX server (default: "")
--hostname, --hostname <value>
-    Host name of the DX server (default: "")
--dxPort, --dxPort <value>
-    Port number of the DX server, for any Kubernetes Environment default port is 443 (default: "")
--contenthandlerPath <value>
-	The path to the contenthandler servlet on the Script Application server.
--dxUsername, --dxUsername <value>
-    Username of the DX server (default: "")
--dxPassword, --dxPassword <value>
-    Password of the DX Core (default: "")
--syndicatorUrl, --syndicatorUrl<value>
-  Syndicator URL of target server e.g http(s)://host:port/wps/wcm
--syndicatorName, --syndicatorName <value>
-  New syndicator name
--subscriberName, --subscriberName <value>
-  New subscriber name
--vaultSlotName, --vaultSlotName <value>
-  Credential Vault Name of source server
--isEnabled, --isEnabled <value>
-  Whether the syndicator/subscriber pair is enabled on creation: isEnabled (default is true)
--updateAfterCreation, --updateAfterCreation <value>
-  Whether the syndicator/subscriber pair is updateAfterCreation : updateAfterCreation (default is true)
--syndicationType, --syndicationType <value>
-  The libraries to syndicate eg. all-items,liveItems,liveProjectsItem,all-items,published-items and all-items-and-versions.
--webContentLibraries, --webContentLibraries <value>
-  Libraries Name of target Server
--subscriberURL, --subscriberURL <value>
- Subscriber URL e.g http(s)://host:port/wps/wcm
--mode, --mode <value>
- Syndicator/subscriber mode
--syndicatorVaultSlotName, --syndicatorVaultSlotName <value>
- Credential Vault Name
--dxContextRoot, --dxContextRoot <value>
- Dx context root
--virtualPortalContext, --virtualPortalContext <value>
- Virtual portal Context
-```
-Example usage:
-```
-dxclient create-syndication-relation -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -contenthandlerPath <contenthandlerPath> -dxUsername <dxUsername> -dxPassword <dxPassword> -syndicatorUrl <syndicatorUrl>
--syndicatorName <syndicatorName> -subscriberName <subscriberName> -vaultSlotName <vaultSlotName>
--isEnabled <isEnabled> -updateAfterCreation <updateAfterCreation> -syndicationType <syndicationType> -webContentLibraries <webContentLibraries> -subscriberURL <subscriberURL>
--mode <mode> -syndicatorVaultSlotName <syndicatorVaultSlotName> -dxContextRoot <dxContextRoot>
--virtualPortalContext <virtualPortalContext>
-```
-### 28. Create Credential Vault
-The `create-credential-vault` command is used to create or update a credential vault slot in the DX server.
-Commands Description
-```
-dxclient create-credential-vault
-```
-**Help command**
-This command shows the help document on the `create-credential-vault` command:
-```
-dxclient create-credential-vault -h
-```
-**Commands options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--xmlConfigPath <value>
-	Use this attribute to specify the path to DX configuration endpoint
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--credentialSlotName <value>
-	Use this attribute to specify the credential vault segment slot name
--vaultUsername <value>
-	Use this attribute to specify the credential vault vaultUsername
--vaultUserGroup <value>
-	Use this attribute to specify the credential vault UserGroup
--vaultPassword <value>
-	Use this attribute to specify the credential vault shared userid password
--vaultSegmentName <value>
-	Use this attribute to specify the credential vault segment name and the default is set to "DefaultAdminSegment"
--vaultDescription <value>
-	Use this attribute to specify the credential vault segment description
-```
-Log files from command execution can be found in the logs directory of the DXClient installation.
-Example Usage:
-```
- dxclient create-credential-vault -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword>  -xmlConfigPath <xmlConfigPath> -credentialSlotName <credentialSlotName> -vaultUsername <vaultUsername> -vaultPassword <vaultPassword>
-```
-### 29. WCM Libraries Export
-The `wcm-library-export` command is used to export the wcm libraries from the source server to a user-specified location.
-Commands Description
-```
-dxclient wcm-library-export
-```
-**Help command**
-This command shows the help document on the `wcm-library-export` command:
-```
-dxclient wcm-library-export -h
-```
-**Commands options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxWASUsername <value>
-	Use this attribute to specify the username of the DX WAS server
--dxWASPassword <value>
-	Use this attribute to specify the password of the DX WAS server
--dxProfileName <Profile name of the DX core server>
-  	Use this attribute to specify the profile name of the DX core server
--librariesName  <value>
-	Use this attribute to specify the names of the wcm libraries of the DX core server (e.g. "hello_library,demo_library")
--exportAllLibraries <value>
-	Use this attribute to specify the export libraries. This value can be true or false. If true then export the all libraries
--virtualPortalContext <value>
-	The context of the virtual portal from which wcm library should be exported.
-```
-Log files from command execution can be found in the logs directory of the DXClient installation.
-Example Usage:
-```
- dxclient wcm-library-export -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxWASUsername <dxWASUsername> -dxProfileName <dxProfileName> -librariesName <librariesName>
-```
-### 30. WCM Libraries Import
-The `wcm-library-import` command is used to import the wcm libraries from the source server into the target server.
-Commands Description
-```
-dxclient wcm-library-import
-```
-**Help command**
-This command shows the help document on the `wcm-library-import` command:
-```
-dxclient wcm-library-import -h
-```
-**Commands options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxWASUsername <value>
-	Use this attribute to specify the username of the DX WAS server
--dxWASPassword <value>
-	Use this attribute to specify the password of the DX WAS server
--dxProfileName <Profile name of the DX core server>
-  	Use this attribute to specify the profile name of the DX core server
--libFilePath <value>
-	Use this attribute to specify the path to a zip/tar containing wcm libraries in it
--virtualPortalContext <value>
-	The context of the virtual portal to which wcm library should be imported.
-```
-Log files from command execution can be found in the logs directory of the DXClient installation.
-Example Usage:
-```
- dxclient wcm-library-import -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxWASUsername <dxWASUsername> -dxProfileName <dxProfileName> -libFilePath <libFilePath>
-```
-### 31. DX Core Configuration Reports
-The `dx-core-configuration-reports` command is used to generate the differential reports on various core configurations between two dx server nodes.
-The dx-core-configuration-reports summary-report command shows the summary of the configurations of a single DX server or both source and target DX servers, which users may use to compare.
-Command Description:
-```
-dxclient dx-core-configuration-reports
-```
-**Help command:**
-This command shows the help information for `dx-core-configuration-reports` command usage:
-```
-dxclient dx-core-configuration-reports summary-report -h
-```
-**Commands**
-```
-dx-core-configuration-report summary-reports [OPTIONS]
-	Provides a configurational report with differences for the source or target DX Core Servers.
-```
-Command options: Summary report command
-```
--hostname <value>
-	Use this attribute to specify the hostname of the DX Core server
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxProfileName <Profile name of the DX core server>
-  Use this attribute to specify the profile name of the DX core server
--targetHostname <value>
-	Use this attribute to specify the hostname of the target DX core server
--targetDxConnectPort <value>
-	Use this attribute to specify the port number of the target cw_profile server
--targetDxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the target cw_profile server
--targetDxConnectPassword<value>
-	Use this attribute to specify the password that is required for authenticating to the target cw_profile server
--targetDxProfileName <Profile name of the DX core server>
-  Use this attribute to specify the profile name of the target DX Core server
-```
-```
-**Note:** target server details are only needed when the user needs to generate the summary of the configurations to both servers.
-```
-Example usage:
-```
-dxclient dx-core-configuration-reports summary-report -hostname <hostname> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -dxConnectPort <dxConnectPort> -dxProfileName <dxProfileName> -targetHostname <targetHostname> -targetDxConnectUsername <targetDxConnectUsername> -targetDxConnectPassword <targetDxConnectPassword> -targetDxConnectPort <targetDxConnectPort> -targetDxProfileName <targetDxProfileName>
-```
-### 32. Export dam assets
-The export command is used to export the assets of a dam in the file system at the location specified by the user or default location `store/outputFiles/dam-export-assets/`
-Commands Description
-```
-dxclient manage-dam-assets export-assets
-```
-**Help command**
-This command shows the help information for `manage-dam-assets` command usage:
-```
-dxclient manage-dam-assets export-assets -h
-```
-**Commands options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the DX server
--hostname <value>
-	Use this attribute to specify the hostname of the DX server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--damAPIPort <value>
-    Port number of the DAM server, for any Kubernetes Environment default port is 443 (default: "")
--ringAPIPort <value>
-    Port number of the DX Core API server, for any Kubernetes Environment default port is 443 (default: "")
--ltpaTokenRefreshTime <value>
-    LTPA Token Refresh time in minutes (default: "5")
--exportPath <value>
-   Location of the file path to export(Default path is store/outputFiles/dam-export-assets/)
--exportBinary <value>
-   Use true or false to include or exclude binary as part of export(default is true)
-**Note:** Optional parameter are exportPath and exportBinary.
-```
-Example Usage:
-```
-dxclient manage-dam-assets export-assets -dxProtocol https -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -exportPath <exportPath> -exportBinary <exportBinary>
-```
-### 33. Validation of exported dam assets
-The valdiate command is used to validate exported DAM assets file at the location specified by the user or default location `store/outputFiles/dam-export-assets/`
-Commands Description
-```
-dxclient manage-dam-assets validate-assets
-```
-**Help command**
-This command shows the help information for `manage-dam-assets` command usage:
-```
-dxclient manage-dam-assets validate-assets -h
-```
-**Commands Optional options**
-```
--exportPath <value>
-   Location of the file path to export(Default path is store/outputFiles/dam-export-assets/)
--importBinary <value>
-   Use true or false to include or exclude binary as part of import(default is true)
-**Note:** Optional parameter are exportPath and importBinary.
-```
-Example Usage:
-```
-dxclient manage-dam-assets validate-assets -exportPath <exportPath> -importBinary <importBinary>
-```
-### 34. Import dam assets
-The import command is used to import the assets of a dam to the target environment from the location specified by the user or default location `store/outputFiles/dam-export-assets/`
-Commands Description
-```
-dxclient manage-dam-assets import-assets
-```
-**Help command**
-This command shows the help information for `manage-dam-assets` command usage:
-```
-dxclient manage-dam-assets import-assets -h
-```
-**Commands options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the DX server
--hostname <value>
-	Use this attribute to specify the hostname of the DX server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
--damAPIPort <value>
-    Port number of the DAM server, for any Kubernetes Environment default port is 443 (default: "")
--ringAPIPort <value>
-    Port number of the DX Core API server, for any Kubernetes Environment default port is 443 (default: "")
--exportPath <value>
-   Location of the file path to import(Default path is store/outputFiles/dam-export-assets/)
--importBinary <value>
-   Use true or false to include or exclude binary as part of import(default is true)
-**Note:** Optional parameter are exportPath and importBinary.
-```
-Example Usage:
-```
-dxclient manage-dam-assets import-assets -dxProtocol https -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -exportPath <exportPath> -importBinary <importBinary>
-```
-### 35. Manage dam staging get all subscribers
-manage-dam-staging get-all-subscribers command is used to get all the subscribers details for dam staging.
-Commands Description
-```
-dxclient manage-dam-staging get-all-subscribers
-```
-**Help command**
-This command shows the help information for `manage-dam-staging get-all-subscribers` command usage:
-```
-dxclient manage-dam-staging get-all-subscribers -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-	Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-	Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-	Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-	Password of the DX server of the publisher (default: "")
--damAPIPort, --damAPIPort <value>
-	Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-	Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-	API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-	API Version number of DX Core API server of the publisher (default: "")
-```
-Example usage:
-```
-dxclient manage-dam-staging get-all-subscribers -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion>
-```
-### 36. Restart Core Pods
-restart-core-pods command is used to restart all the Core Pods in a Kubernetes-based deployments.
-Commands Description
-This command triggers a rollout restart for a Kubernetes-based deployments, similar to `kubectl rollout retstart` command.
-Note: Only the user set as `wasAdmin` in the Helm values in authorised to trigger this command.
-```
-dxclient restart-core-pods
-```
-**Help command**
-This command shows the help information for `restart-dx-core` command usage:
-```
-dxclient restart-dx-core -h
-```
-**Command options**
-```
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxWASUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the DX WAS Server:
--dxWASPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the DX WAS Server:
--hostname <value>
-	Use this attribute to specify the hostname of the target DX deployment:
-```
-### 37. Undeploy Application
-undeploy-application command is used to undeploy an EAR file from the WebSphere Application Server.
-Commands Description
-```
-dxclient deploy-application
-This command undeploys the application from WAS. User could opt to store backup by setting 'enable-backup' parameter to true .
-```
-**Help command**
-This command shows the help information for `undeploy-application` command usage:
-```
-dxclient undeploy-application -h
-```
-**Common Command options**
-```
--hostname <value>
-	Use this attribute to specify the hostname of the target server
--dxProtocol <value>
-	Use this attribute to specify the protocol with which to connect to the server
--dxPort <value>
-	Use this attribute to specify the port on which to connect to the server(for Kubernetes Environment dxPort is 443)
--dxUsername <value>
-	Use this attribute to specify the username that is required for authenticating with the server
--dxPassword <value>
-	Use this attribute to specify the password that is required for authenticating with the server
-Required options for application deployment:
--dxConnectPort <value>
-	Use this attribute to specify the port number of the cw_profile(for Kubernetes Environment dxConnectPort is 443)
--dxConnectUsername <value>
-	Use this attribute to specify the username that is required for authenticating to the cw_profile
--dxConnectPassword <value>
-	Use this attribute to specify the password that is required for authenticating to the cw_profile
--dxSoapPort <Soap port of the DX server>
-    Use this attribute to specify Soap port of the DX server
--dxProfileName <Profile name of the DX core server profile>
-    Use this attribute to specify the profile name of the DX core server
--applicationName <value>
-    Use this attribute to specify the application name
- Optional arguments:
--enable-backup <value>
- 	Set the flag to true to take backup of the application to be undeployed. Default is false.
-**Note:** Mandatory parameters applicationName should be passed into the command line.
-```
-  Example Usage:
-```
-dxclient undeploy-application -dxProtocol <http/https> -hostname <host-name> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -dxSoapPort <dxSoapPort> -dxConnectPort <dxConnectPort> -dxConnectUsername <dxConnectUsername> -dxConnectPassword <dxConnectPassword> -applicationName <application name> -dxProfileName <Profile name of the DX core server>
-```
-### 38. LiveSync Push Theme
-This command will sync your WebDAV based theme files into DX Server. Then, it will watch for succeeding changes within the given `themePath` and immediately reflect the changes in the DX Server.
-Commands Description
-This command initially pushes the local theme (provided in `themePath`) into DX Server with the theme system name (provided in `themeName`). During this initial synchronization, theme files in the WebDAV server are currently unavailable for other clients. It will then create a file system watcher which will watch for any changes (files or folders) under `themePath` and immediately reflect those changes in DX Server. To stop watching, press (Ctrl + C).
-```
-dxclient livesync push-theme
-```
-**Help command**
-This command shows the help information for `live-sync` command usage:
-```
-dxclient livesync push-theme -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server
--hostname, --hostname <value>
-	Host name of the DX server
--dxPort, --dxPort <value>
-	Port number of the DX Server, for any Kubernetes Environment default port is 443
--dxUsername, --dxUsername <value>
-	Username of the DX Core server
--dxPassword, --dxPassword <value>
-	Password of the DX Core server
--contenthandlerPath,--contenthandlerPath <value>
-	Alternate path for the portal context root or the content handler servlet (default: "/wps/mycontenthandler")
--themeName, --themeName <value>
-	Theme System Name
--themePath, --themePath <value>
-	Local path to the Theme folder
--disablePrompt, --disablePrompt <value>
-	Disable the confirmation prompt for overwriting local and server files. Bypasses the prompt and immediately proceeds on pushing or pulling theme files.
-```
-Example usage:
-```
-dxclient livesync push-theme -dxUsername <dxUsername> -dxPassword <dxPassword> -dxPort <dxPort> -dxProtocol <dxProtocol> -hostname <hostname> -contenthandlerPath <contenthandlerPath> -themePath <themePath> -themeName <themeSystemName>
-```
-**Ignoring files and folders**
-You can opt to ignore files and folder paths to sync to server by creating an ignore file (`.ignore`) under the root of theme folder. When changing contents of the ignore file, the command needs to be re-run again to reflect the files the needs to be ignored.
-Sample ignore file contents:
-```
-#.ignore
-test.txt
-sample.txt
-logs/
-```
-### 39. LiveSync Pull Theme
-The livesync pull-theme command is used to sync WebDAV based theme files from the DX server to a local folder.
-Commands Description
-This command will download a zipped file from the theme server which then will be extracted to the chosen local directory of the theme (provided in `themePath`), overwriting existing files and deleting stale files in the process. If `themeName` option is not provided, a list of WebDAV themes are dislayed and user may select a theme to pull into their local.
-```
-dxclient livesync pull-theme
-```
-**Help command**
-This command shows the help information for `livesync pull-theme` command usage:
-```
-dxclient livesync pull-theme -h
-```
-**Command Options:**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server
--hostname, --hostname <value>
-	Host name of the DX server
--dxPort, --dxPort <value>
-	Port number of the DX Server, for any Kubernetes Environment default port is 443
--dxUsername, --dxUsername <value>
-	Username of the DX Core server
--dxPassword, --dxPassword <value>
-	Password of the DX Core server
--contenthandlerPath,--contenthandlerPath <value>
-	Alternate path for the portal context root or the content handler servlet (default: "/wps/mycontenthandler")
--themeName, --themeName <value>
-	Theme System Name
--themePath, --themePath <value>
-	Local path to the Theme folder
--disablePrompt, --disablePrompt <value>
-	Disable the confirmation prompt for overwriting local and server files. Bypasses the prompt and immediately proceeds on pushing or pulling theme files.
-```
-Example usage:
-```
-dxclient livesync pull-theme --dxUsername <dxUsername> --dxPassword <dxPassword> --dxPort <dxPort> --dxProtocol <dxProtocol> --hostname <hostname> --contenthandlerPath <contenthandlerPath> --themePath <themePath> --themeSystemName <themeName>
-```
-### 40. Manage dam staging get staging mismatch report
-manage-dam-staging get-staging-mismatch-report command is used to generate staging mismatch report.
-Commands Description
-```
-dxclient manage-dam-staging get-staging-mismatch-report
-```
-**Help command**
-This command shows the help information for `manage-dam-staging get-staging-mismatch-report` command usage:
-```
-dxclient manage-dam-staging get-staging-mismatch-report -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-	Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-	Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-	Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-	Password of the DX server of the publisher (default: "")
--damAPIPort, --damAPIPort <value>
-	Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-	Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-	API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-	API Version number of DX Core API server of the publisher (default: "")
--subscriberId, --subscriberId <value>
-	Subscriber id of the target environment of the subscriber (default: "")
--recordType, --recordType <value>
-	Type of the mismatch record (default: "")
--recordAction, --recordAction <value>
-	Action of the mismatch record (default: "")
--reportPath, --reportPath <value>
-	Location of the file path to download report (Default path is store/outputFiles/)
--ltpaTokenRefreshTime, --ltpaTokenRefreshTime <value>
-	LTPA Token refresh time in minutes (default: 5)
-```
-Example usage:
-```
-dxclient manage-dam-staging get-staging-mismatch-report -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion> -subscriberId <subscriberId> -recordType <recordType> -recordAction <recordAction> -reportPath <reportPath> -ltpaTokenRefreshTime <ltpaTokenRefreshTime>
-```
-!!!warning
-        1. Avoid using `~` `!` `()` `'` and `*` special characters when naming files and folders.
-        2. If you have a theme title name with special characters, those are automatically converted to underscores (`_`) by the server (for example, `来源folder` is translated to `__folder`). For the theme name, use the Theme System Name, the one with `_` like `__folder` in the following example.
-### 41. Manage dam staging find staging mismatch
-manage-dam-staging find-staging-mismatch command is used to get mismatch logs for dam staging.
-Commands Description
-```
-dxclient manage-dam-staging find-staging-mismatch
-```
-**Help command**
-This command shows the help information for `manage-dam-staging find-staging-mismatch` command usage:
-```
-dxclient manage-dam-staging find-staging-mismatch -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-	Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-	Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-	Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-	Password of the DX server of the publisher (default: "")
--damAPIPort, --damAPIPort <value>
-	Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-	Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-	API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-	API Version number of DX Core API server of the publisher (default: "")
--subscriberId, --subscriberId <value>
-	Subscriber id of the target environment of the subscriber
-```
-Example usage:
-```
-dxclient manage-dam-staging find-staging-mismatch -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion> -subscriberId <subscriberId>
-```
-### 42. Manage dam staging start staging resync
-manage-dam-staging start-staging-resync command is used to trigger staging resync.
-Commands Description
-```
-dxclient manage-dam-staging start-staging-resync
-```
-**Help command**
-This command shows the help information for `manage-dam-staging start-staging-resync` command usage:
-```
-dxclient manage-dam-staging start-staging-resync -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-	Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-	Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-	Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-	Password of the DX server of the publisher (default: "")
--damAPIPort, --damAPIPort <value>
-	Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-	Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-	API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-	API Version number of DX Core API server of the publisher (default: "")
--subscriberId, --subscriberId <value>
-	Subscriber id of the target environment of the subscriber
-```
-Example usage:
-```
-dxclient manage-dam-staging start-staging-resync -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion> -subscriberId <subscriberId>
-```
-### 43. Manage dam staging delete staging mismatch
-manage-dam-staging delete-staging-mismatch command is used to delete mismatch logs for all the registered dam staging subscribers.
-Commands Description
-```
-dxclient manage-dam-staging delete-staging-mismatch
-```
-**Help command**
-This command shows the help information for `manage-dam-staging delete-staging-mismatch` command usage:
-```
-dxclient manage-dam-staging delete-staging-mismatch -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server of the publisher (default: "")
--hostname, --hostname <value>
-	Host name of the DX server of the publisher (default: "")
--dxPort, --dxPort <value>
-	Port number of the DX server of the publisher (default: "")
--dxUsername, --dxUsername <value>
-	Username of the DX server of the publisher (default: "")
--dxPassword, --dxPassword <value>
-	Password of the DX server of the publisher (default: "")
--damAPIPort, --damAPIPort <value>
-	Port number of the DAM API server of the publisher (default: "")
--ringAPIPort, --ringAPIPort <value>
-	Port number of the DX Core API server of the publisher (default: "")
--damAPIVersion, --damAPIVersion <value>
-	API Version number of DAM API server of the publisher (default: "")
--ringAPIVersion, --ringAPIVersion <value>
-	API Version number of DX Core API server of the publisher (default: "")
--subscriberId, --subscriberId <value>
-	Subscriber id of the target environment of the subscriber (default: "")
-```
-```
-**Note:** The "subscriberId" is required only when a user intends to delete mismatch logs for a particular subscriber.
-```
-Example usage:
-```
-dxclient manage-dam-staging find-staging-mismatch -dxProtocol <dxProtocol> -hostname <hostname> -dxPort <dxPort> -dxUsername <dxUsername> -dxPassword <dxPassword> -damAPIPort <damAPIPort> -ringAPIPort <ringAPIPort> -damAPIVersion <damAPIVersion> -ringAPIVersion <ringAPIVersion> -subscriberId <subscriberId>
-```
-### 44. LiveSync Push WCM Design Library
-This command will sync your WCM Design Library local files into DX Server. Then, it will watch for succeeding changes within the given `wcmLibraryPath` and immediately reflect the changes in the DX server.
-> :warning: **Feature Limitations:**
-> 1. Supported WCM Types: Presentation Template, HTML Component and Folder Component.
-> 2. Moving and Renaming of files will be equivalent to deleting the original components and creation of an entirely new components.
-> 3. If a published component have a draft version, the feature will pull and push into the draft version.
-> 4. The Push WCM Design Library feature will only work on WCM Design Library previously pulled by the LiveSync Pull WCM Design Library feature.
-Commands Description
-This command invokes the livesync push-wcm-design-library tool inside the DXClient.
-This command initially pushes all the changes that happened in local WCM Design Library files (provided in `wcmLibraryPath`) to DX Server with the WCM Design Library system name (provided in `wcmLibraryName`). It will then create a file system watcher which will watch for any changes (files or folders) under `wcmLibraryPath` and immediately reflect those changes in DX Server. To stop watching, press (Ctrl + C).
-```shell
-dxclient livesync push-wcm-design-library
-```
-**Help command**
-This command shows the help information for `live-sync` command usage:
-```shell
-dxclient livesync push-wcm-design-library -h
-```
-**Command options**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server
--hostname, --hostname <value>
-	Host name of the DX server
--dxPort, --dxPort <value>
-	Port number of the DX Server, for any Kubernetes Environment default port is 443
--dxUsername, --dxUsername <value>
-	Username of the DX Core server
--dxPassword, --dxPassword <value>
-	Password of the DX Core server
--contenthandlerPath,--contenthandlerPath <value>
-	Alternate path for the portal context root or the content handler servlet (default: "/wps/mycontenthandler")
--wcmLibraryName, --wcmLibraryName <value>
-	WCM Design Library Name
--wcmLibraryId, --wcmLibraryId <value>
-	UUID of the WCM Design Library
--wcmLibraryPath, --wcmLibraryPath <value>
-	Local path to the Library folder
--wcmProjectName, --wcmProjectName <value>
-	Name of the WCM Project
--virtualPortalContext, --virtualPortalContext <value>
-	Context of the virtual portal of the DX Core server
--disablePrompt, --disablePrompt <value>
-	Disable the confirmation prompt for overwriting local and server files. Bypasses the prompt and immediately proceeds on pushing or pulling theme files.
-```
-Example usage:
-```
-dxclient livesync push-wcm-design-library -dxUsername <dxUsername> -dxPassword <dxPassword> -dxPort <dxPort> -dxProtocol <dxProtocol> -hostname <hostname> -contenthandlerPath <contenthandlerPath> -wcmLibraryPath <wcmLibraryPath> -wcmLibraryName <wcmLibraryName>
-```
-**Optional wcmLibraryName and wcmLibraryId inputs**
-If the user provided neither of these options. The dxclient livesync push-wcm-design-library will use the metadata of saved WCM Design Library in the `wcmLibraryPath`.
-### 45. LiveSync Pull WCM Design Library
-This command is used to sync a DX WCM Design Library from DX Server to a local folder.
-> :warning: **Feature Limitations:**
-> 1. Supported WCM Types: Presentation Template, HTML Component and Folder Component.
-> 2. Moving and Renaming of files will be equivalent to deleting the original components and creation of an entirely new components.
-> 3. If a published component have a draft version, the feature will pull and push into the draft version.
-> 4. The Push WCM Design Library feature will only work on WCM Design Library previously pulled by the LiveSync Pull WCM Design Library feature.
-Commands Description
-This command invokes the livesync pull-wcm-design-library tool inside the DXClient.
-This command will download the WCM Design Library files in DX Server under the given library name (provided in `-wcmLibraryName`). This will then be saved to the target local directory of the library (provided in `-wcmLibraryPath`), overwriting existing files in this local directory which also deletes stale files in the process.
-```
-dxclient livesync pull-wcm-design-library
-```
-**Help command**
-This command shows the help information for `livesync pull-wcm-design-library` command usage:
-```
-dxclient livesync pull-wcm-design-library -h
-```
-**Command Options:**
-```
--dxProtocol, --dxProtocol <value>
-	Protocol of the DX server
--hostname, --hostname <value>
-	Host name of the DX server
--dxPort, --dxPort <value>
-	Port number of the DX Server, for any Kubernetes Environment default port is 443
--dxUsername, --dxUsername <value>
-	Username of the DX Core server
--dxPassword, --dxPassword <value>
-	Password of the DX Core server
--contenthandlerPath,--contenthandlerPath <value>
-	Alternate path for the portal context root or the content handler servlet (default: "/wps/mycontenthandler")
--wcmLibraryName, --wcmLibraryName <value>
-	WCM Design Library Name
--wcmLibraryId, --wcmLibraryId <value>
-	UUID of the WCM Design Library
--wcmibraryPath, --wcmLibraryPath <value>
-	Local path to the Library folder
--wcmProjectName, --wcmProjectName <value>
-	Name of the WCM Project
--virtualPortalContext, --virtualPortalContext <value>
-	Context of the virtual portal of the DX Core server
--disablePrompt, --disablePrompt <value>
-	Disable the confirmation prompt for overwriting local and server files. Bypasses the prompt and immediately proceeds on pushing or pulling theme files.
-```
-Example usage:
-```
-dxclient livesync pull-wcm-design-library -dxUsername <dxUsername> -dxPassword <dxPassword> -dxPort <dxPort> -dxProtocol <dxProtocol> -hostname <hostname> -contenthandlerPath <contenthandlerPath> -wcmLibraryPath <wcmLibraryPath> -wcmLibraryName <wcmLibraryName>
-```
-**Optional wcmLibraryName and wcmLibraryId inputs**
-If neither of these options is not provided:
-1. The LiveSync will check if a saved library was previously pull using this command and use that as the basis.
-2. If no saved library is detected, a list of WCM Design Libraries displayed and you can select a WCM Design Library to pull.
-Sample WCM Design Library Selection Prompt
-```shell
-$ dxclient livesync pull-wcm-design-library -dxUsername <dxUsername> -dxPassword <dxPassword> -dxPort <dxPort> -dxProtocol <dxProtocol> -hostname <hostname> -contenthandlerPath <contenthandlerPath> -wcmLibraryPath <wcmLibraryPath>
-2024-08-16 19:53:06 : Checking for saved WCM Design Library in <wcmLibraryPath>
-2024-08-16 19:53:06 : Please select a WCM Design Library
-(x) [Library Name: blog solo template v70,  Display Title: Blog Solo Template v70,  ID: ddc1c6de-b18d-4cfd-af8f-dac5ccdd5d30]
-( ) [Library Name: blog template v70,  Display Title: Blog Template v70,  ID: 5eb62c46-6f7d-498f-b71d-6bbdaac3e84a]
-( ) [Library Name: ml configuration,  Display Title: ML Configuration,  ID: cac73711-d639-436b-a922-1a717c5e1105]
-( ) [Library Name: portal site,  Display Title: Portal Site,  ID: TWFuYWdlZCBQYWdlcyBSb290IExpYnJhcnk]
-```
-# Logger enablement
-## Enable logger
-Logger can be enabled by setting parameter "enableLogger": true in the below file. If logger enabled then logger file will be generate in logs folder of the dxclient.
-dist/configuration/config.json
-If logger enabled then logger file will be available in the below location:
-store/logs/
+  25. If connecting to an HCL DX 9.5 CF227 deployment, following changes are to be expected.
-## disable logger
+  - LiveSync now supports Style-Sheet Components.
-Logger can be disabled by setting parameter "enableLogger":false in the below file
+</details>
-dist/configuration/config.json
+## [DXClient Documentation](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/)
-All the generic command options can be configured inside “config.json” of the tool, which will be read as default.
-The options passed through command line will override these default values.
+Full documentation of DXClient can be found [here](https://opensource.hcltechsw.com/digital-experience/latest/extend_dx/development_tools/dxclient/).