The multilingual solution consists of a set of extensions
to Web Content Manager that can
be used to manage the authoring, workflow, and configuration of your
multilingual system.
Procedure
Note: With HCL Digital Experience 9.5 Container Update CF192, multilingual solution (MLS)
is now enabled out of the box. This means that the following steps do not need to be run
in the container.
- Ensure that the WasPassword and PortalAdminPwd passwords are set in the wkplc.properties file.
- Run the following registration command from the
wp_profile_root/ConfigEngine
directory:
- Windows™
- ConfigEngine.bat register-wcm-mls
- AIX® HP-UX Linux™ Solaris
- ./ConfigEngine.sh register-wcm-mls
- IBM® i
- ConfigEngine.sh register-wcm-mls
- z/OS®
- ./ConfigEngine.sh register-wcm-mls
- Run the following deployment command from the
wp_profile_root/ConfigEngine
directory:
- Windows
- ConfigEngine.bat deploy-wcm-mls
- AIX HP-UX Linux Solaris
- ./ConfigEngine.sh deploy-wcm-mls
- IBM i
- ConfigEngine.sh deploy-wcm-mls
- z/OS
- ./ConfigEngine.sh deploy-wcm-mls
- If your server contains virtual portals, you must also
run the following task for each virtual portal on your server:
- Windows
- ConfigEngine.bat import-wcm-mls-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=virtual_portal_context_url
- AIX HP-UX Linux Solaris
- ./ConfigEngine.sh import-wcm-mls-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=virtual_portal_context_url
- IBM i
- ConfigEngine.sh import-wcm-mls-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=virtual_portal_context_url
- z/OS
- ./ConfigEngine.sh import-wcm-mls-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=virtual_portal_context_url
- Restart HCL Portal.
- Repeat these steps on every server and cluster node.