Replies

Thanks for the quick resolution Tim!!

You can get a Community Edition of InterSystems IRIS as Evgeny suggested, or if you need a new developer license for your Caché instance you should work with your Account Manager to get one.  If you are not sure who your account manager is, contact the WRC who should be able to help direct you.

I agree with both Tim and Evgeny.  In addition, I will add that we also store our unit tests in a different location, which has a top level of /internal for all of our in-house applications.  We store unit tests and test data in /internal so our integration scripts can explicitly ignore changes in those branches when we're porting things to our LIVE branch.  This ensures that no testing code or testing data ever make it into production.  

@Perla Escarcega  - that is one of the ways to do a Refresh, yes.  You need to first populate all files in your Source Workspace, and then the Refresh will walk the directory contents and load everything in.

More details can be found on slides 43-45 of ICC520:

ftp://ftp.intersystems.com/isc/customers/ccrtraining/ICC520(Presentation)%20CCR%20Tier%201%20-%20Baselining%20Source%20Code.pdf
 

@Perla Escarcega  - taking a closer look at this, I think we had an issue with a historical file clean-up routine which was a little too overeager to reclaim space.  All of your source is safe and available but you may need to create a fresh ItemSet to push this source.  Note - you should always be making fresh ItemSets anyway because the head revision may be newer than what is in your historical ItemSet, and you don't want to get an older revision of something which breaks when interacting with a newer revision of other items.  So simply create a new ItemSet for BASE and deploy it and you should be all set.

P.S.  This does raise the question of why you are initializing a new Secondary BASE environment from old ItemSets as opposed to just grabbing the head revision of the BASE source and running Refresh to pull it all into the Namespace?  I am afraid your approach may be significantly more risky than the recommended approach.  

Actually - I take back my statement now that I looked at the error more closely.  It appears as though it's trying to fetch an ItemSet by ID that doesn't actually exist.   What is the CCR in question?

@Perla Escarcega  - the fact that it is already in LIVE should not have any bearing here.  I am guessing that the newly created Namespace is part of a newly created instance?  It looks like you may have an older version of the CCR Client Tools with a bug in it.  Could you provide the results of "Do Version^%buildccr" so we can see what versions of the tools you are running?

I hope that someone else can chime in and confirm, but my understanding is that we don't release Caché on containers, only InterSystems IRIS containers (I just looked in the Distributions section of the WRC to confirm).  However, you should be able to get a InterSystems IRIS container to play with so this shouldn't be a blocker for you - just grab an InterSystems IRIS container (available via the WRC Distributions page, or Docker Hub) and use that to try the demo.

In terms of Caché on containers, I know that there are people in the community who have 'rolled their own', and you can find details on threads here, but I don't think you want to go in that direction if you're new with containers.  

HTH - good luck!

Ben

I need to defer to @Sergei Shutov  for many of the answers but I can help with one of these:
[quote]

- General web application question for Cache/IRIS: once I create the web application for example at \csp\mxdtest, any subfolder there is treated as part of the app, yes?  So i could create C:\InterSystems\Cache\CSP\mxdtest\images and the images folder are part of the web applcation  \csp\mxdtest?

[/quote]

Yes, that is correct.  Your subfolders under the root should be navigable via the CSP application.  NOTE - I think this can be overridden by web server settings, but this is the default behavior and I leverage it frequently for my apps