Hello adepters, I have to do a training for Epic beginners, and was asked to use their application. My question is: which files do I have to ask for, so that my installation will work exactly as their.
1. doctype directory 2. catalog file 3. To be sure: additional entity sets 4. To be very sure, all startup files: - init.acl -scripts in Epic-path\custom\init - epicprefs.acl -APTRC file - doktyp.acl and doktyp.js - instance.acl and instance.js - documentname.acl and documentname.js
Is that too less or too much? Thanks for your help
Don't forget APTCATPATH and APTGRPATH and any other environmental variables that may be used. If the graphics directory is on a server, make sure you have access to this directory when you are logged in to the system. Same would be true for the catalog and doctype directory if these are also on a server.
That is a good start. You might also want to see what if any environment variables are set. This can impact how you work. If you can, I'd build in at least a half day for you to get set up when you get there. Just to make sure you have their environment. If you can't do that, you may want to take your material on a CD or portable hard drive and use one of the customer's computers to teach from.
Capturing a working environment can be a major "Pein im der Hintern"
Hi Pia-- I agree with everything Lynn said--we ended up writing detailed instructions for new users on how to set up their Epic environment for our application, and we still run into more problems than we'd like. It's a reliable source of headaches (as well as other kinds of aches Lynn mentions :-). One thing I'd recommend changing in your list: Instead of limiting it to $EPIC/custom/init, I would just copy the entire contents of the $EPIC/custom directory. That way you get any custom scripts, Java classes, etc. etc. Oh, and check whether their application is set up to use some external custom directory (by defining the APTCUSTOM environment variable). For example, our system uses a network location for the custom directory to keep everyone up to date more easily. If that's the case, you'll want to get your copy of the custom directory from the external location, of course. --Clay
Depending on the depth and breadth of what you are expected to train to, you may also need to know what additional modules have been installed and how they use them. For example, do they Print Compose to a printer, Compose / PDF, use E3, use either the Documentum or Oracle adapters? Do they used fixed or concurrent licensing? Understanding a failure to acquire a license isn't rocket science, but how to recover may be "job knowledge" they'll require. Hopefully, though, this is all the responsibility of someone in their organization! Even so, it's nice to know how they will be expected to work, not necessarily so you can instruct to it, but so if there are answers that go beyond the "basics" of Epic, you will be able to limit your answer to the domain of likely, rather than possible. ------ Paul Nagai
I found a good help in using the "bugsave" utility (or as from Epic 5.x the tools/save application or "appsave" command, which I believe is equivalent): it saves all relevant pieces you need (including entities, environment variables etc). That may be a good start to get all the necessary information about their environment (see also the log file!). It's a tool normally used for Arbortext support, but it may help you out there as well. I had just to add quotation marks in the last line of the "start.bat" file where Epic is called to made it to work.
That's a great idea, but you have to use some caution with this approach. We have a pretty complex DTD and very complex XSLT stylesheets. When we tried using the Appsave feature, we found that it omitted large numbers of files from our application.
So, my advice would be to try this, but to check the resulting app copy carefully to make sure all the pieces really are there.
the training will take place at a training center (not within their environment) so licensing will not be the problem. I tried the "bugsave" or "appsave" utility in my own environment to figure out how it works. Let me tell what I understand: - The customer has to call the command "bugsave" or "appsave" when s/he has opened a valid file of that special application. - The result will be a directory which (hopefully) contains all necessary files for setting up/mirrowing the customers environment at the training center. - The customer has to send me the resulting directory, and I will set up the environment in the training center.
Hans, for what reason do I need the quotation in the "start.bat"
Helberg, Clay schrieb:
>Hi Hans-- > >That's a great idea, but you have to use some caution with this approach. We have a pretty complex DTD and very complex XSLT stylesheets. When we tried using the Appsave feature, we found that it omitted large numbers of files from our application. > >So, my advice would be to try this, but to check the resulting app copy carefully to make sure all the pieces really are there. > > --Clay >
Yes, you are understanding perfectly well. I myself didn't observe that something was ever missing and when I have sent in cases to Arbortext I can't remember that they ever mentioned a missing file, but I fully believe Clay (he is a reliable person 😉 I met him on the last AUGI): so be careful and test before you start your training. There's nothing worse (for you and your students) than starting a training in the morning and nothing works...
As regards the quotations: maybe that's just necessary on Win XP, so if it works for you without modifying this line, just ignore my remark! It simply works for me and I haven't spend any further thoughts about it.
P.S.: Und noch schoene Gruesse aus Strasbourg nach Ulm
Well, I missed some of this while I was traveling last week. There is one reason I can think of you would need to delimited with quotes. This is if you have Epic contained in the "Program Files" folder. There are cases where apps (maybe even Windoze itself) where the space in the folder name causes programs not to work. I know I've had this with Epic in the past. Adding the quotes just makes things work smoother.
My advice (for what it's worth [thank you Mr. Stills]) is not to install into the program files directory. However in your case, for the class, you may not have any choice.