How to deploy asset files with ant migration tool

HOW TO DEPLOY ASSET FILES WITH ANT MIGRATION TOOL SOFTWARE

Your IOC deployment is now ready for use with cram.Make sure your IOC has started up normally after the restart.You can also accomplish the same using iocConsole your_ioc -cleanup You need to do this only during migration this is because merely exiting from iocSh in iocConsole does not start a new screen session. For softIOC's, after changing screeniocs, you'll need to log into the machine hosting the softIoc and restart the softIoc using the /etc/init.d scripts.Reboot your IOC and make sure it comes up correctly with these changes. # Go to IOC top directory and execute IOC startup scriptД¬d /sioc-sys0-ml00/ iocSpecificRelease/iocBoot/sioc-sys0-ml00 Note this listing has some portions alterted to make it fit.

In addition to location from where iocBoot/st.cmd is loaded where bin/././iocBoot/ is replaced with iocSpecificRelease/iocBoot. # Abs: EPICS Soft IOC Startup Script for sioc-sys0-ml00 #!iocSpecificRelease/bin/linux-x86/matlabSupport You will need to change the hashbang portion of the startup script by replacing #!bin/linux-x86 with #!iocSpecificRelease/bin/linux-x86 sioc-sys0-ml00]$ cat startup.cmd

HOW TO DEPLOY ASSET FILES WITH ANT MIGRATION TOOL SOFTWARE

For softIOC's, for each IOC belonging to the software package, change startup.cmd to use the iocSpecificRelease softlink.

The recommended way to refer to collateral in iocTop is to use the iocSpecificRelease link. It does not hurt to have the bin softlink but it is confusing and it makes it very hard to debug cram failures.

For softIOC's, remove the bin softlink to the iocTop area (many softIOC's used this approach) if you previously had one.

Lrwxrwxrwx iocSpecificRelease -> sioc-sys0-ml00]$ You must use relative paths for these softlinks.

For each applicable facility, in iocCommon, for each IOC belonging to the software package, create a iocSpecificRelease softlink and point it to the current softlink defined above.

Lrwxrwxrwx 1 softegr lcls current -> MatlabSupport]$

For each applicable facility, in iocTop/ packageName, create the current softlink and point it to the release that is currently being used in production.Дrwxrwxr-x 9 iocegr lcls MatlabSupport-R3-0-0-0Дrwxrwxr-x 9 softegr lcls MatlabSupport-R3-1-0-0Дrwxrwxr-x 10 softegr lcls MatlabSupport-R3-2-0-0.

This should be the name of the folder in iocTop where the releases are located.

We should use the same name in all the build and deployment tools

Choose a name for your software package.

CRAM migration guide CRAM migration guide Preparing your current IOC deployment for cram

How to deploy asset files with ant migration tool