Post date: Oct 27, 2016 10:56:39 AM
Hi All,
#1) If any one wants to migrate a property which contains Triniti Deployment path or Triniti Deployment URL in its value, then please provide $TRINITI_HOME token for Triniti Deployment path and $TRINITI_URL token for Triniti Application URL. Migration Tool dynamically replaces these tokens according to target instance.
Eg: If user wants <Triniti Deployment Path/Tri2> as property value, then please provide $TRINITI_HOME/Tri2 as property value.
(or) If user wants <Triniti Deployment URL/tri2v2/AOMServlet> as property value, then please provide $TRINITI_URL/tri2v2/AOMServlet as property value.
(Migration tool replaces the $TRINITI_HOME dynamically. It will be replaced with '/software/Tri2ProductionHome/TrinitiApps28/Tri2' in our Triniti instances(Eg: HLPDTEST/TRI2 PROD) and with '/scm_tool/TrinitiAppsHome/TrinitiApps/Tri2' in SunPower client while upgrading instance with UpgradePacks, etc.)
#2) If any one wants to copy a file to some path in Triniti Deployment, then please provide $TRINITI_HOME token for Triniti Deployment path. This token will be taken based on target instance configuration details(which is already registered in Instance Registry worksheet for the target instance).
Eg: If a user wants to copy a jsp to <Triniti Deployment Path/Tri2> path, then please provide $TRINITI_HOME/Tri2 as target path for the object.
All configured migration related tokens for any target instance can be viewed using Application Object Migrator>>Reports>>Migration Tokens For Target Instance eWorksheet.
Note: It will be copied to '/software/Tri2ProductionHome/TrinitiApps28/Tri2' path in our Triniti instances(Eg: HLPDTEST/TRI2 PROD) and to '/scm_tool/TrinitiAppsHome/TrinitiApps/Tri2' path in SunPower client, etc.