Integrating into the packaging and install process
If your customization includes modules that need to be installed along with Creo Elements/Direct Model Manager, you can integrate their installation into the Creo Elements/Direct Model Manager installer.
You can write nsi scripts that will be included in the mmbuild.nsi file. The scripts can do anything required to install your modules. Installation scripts from multiple, independent modules can be included. Your nsi scripts can be included in the variable declaration, the installation section, the uninstall section, and/or the function section.
When Software Distribution Server is installed and mmbuild.bat is first run, the Creo Elements/Direct Manager Server installation created the following directory structure:
mm_modules
install – Should contain nsi scripts required to install a module and is included after Creo Elements/Direct Model Manager is installed.
tools – Should contain nsi scripts that define functions used by other parts of the installation.
uninstall – Should contain nsi scripts required to install a module and is included after Creo Elements/Direct Model Manager is uninstalled.
variables – Should contain nsi scripts with variables that will be included after the Creo Elements/Direct Model Manager variables defined in the mmbuild nsi file.
To have your nsi scripts included in the mmbuild.nsi file, copy your nsh files into the appropriate subdirectories. For example you can have custom nsi scripting included in the install section of mmbuild.nsi by adding a file with an nsh extension into the install subdirectory.
The updates from these changes will be written to the Creo Elements/Direct Model Manager directory. New jar files and customizations will then be available in Creo Elements/Direct Model Manager. New products can be started by also calling Java with a different PRODUCT_CODE and PRODUCT_NAME. See the .bat files to see these changes.
Was this helpful?