8.5

Edit

VDS Server Post-install Procedures

Update Models

There may be a need to update the models used in VDS at some point after the initial installation. To do so:

  • Make sure you have the updated models package file on the master or standalone server.

  • Run the uploader utility and let it do the update:

    cd <install_dir>


# Will update the models, merging the already uploaded with the new ones
./vds_models_uploader.sh <path_to_models_package>


# Use -o flag to overwrite everything with the new models instead of merging
./vds_models_uploader.sh -o <path_to_models_package>

Install ML SDK

You may want to install ML SDK after the main installation. Make sure to perform the below steps from the unpacked installer directory (<package_dir>).

First, check or alter some config options. In config.yml:

  • vds_nexus_url: If installing VDS along with all other components, leave this empty. If installing VDS separately, you'll have to provide a Nexus URL.

In secrets.yml:

  • workfusion_nexus_admin
  • workfusion_nexus_admin_pass

Finally, run the vds-ml-sdk installation:

./install.sh install vds-ml-sdk

ML SDK repository fix for non-Internet environment

If environment for your developers has no access to internet they can have issue during model generation from archetype using installed ML SDK repository.

Error looks like this: "[ERROR] No plugin found for prefix 'archetype' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories". To fix this issue follow next steps:

#Make sure you work under <install_user>
su - <install_user>
# Stop nexus service
 wfmanager stop nexus


# Go to nexus storage and rename maven-metadata-central.xml files into maven-metadata.xml
cd <install_dir>/nexus/sonatype-work/nexus/storage/ml-sdk
find ./ -name "*-central.xml" -exec sh -c 'mv "$1" "$(echo "$1" | sed s/central.xml/\.xml/)"' _ {} \;


# Start nexus service
 wfmanager start nexus
← PreviousNext →