Forums

by Aaron. >> Thu, 29 May 2008 0:30:49 GMT

Hi all,

Does anyone know of an official/recomended naming convention for Jade Databases. We are currently running 2 production and about 4 test and development systems at the moment.

To save on renaming INI files and other directorys would it be better to have then in folders like CurrentTestProdEquiv and NextTestProdEquiv for the current version and the latest version for testing?

Thank you,

by cnwjhp1 >> Thu, 29 May 2008 5:57:43 GMT

Most larger sites use the conventions from the JADECare toolset. I myself have used these conventions for years, and find them quite convenient.

The environment id (envid) is comprised of

<prefix><usage indicator><suffix>

The prefix is usually a company name. The suffix is the database name. The usage indicator is:

D development
P production
U uat
T test

Additional copies of an environment can choose a letter - L, W, whatever.

So you might have

coyDapp1
coyDapp2
coyUapp1
coyUapp2
coyPapp1
coyPapp2

In my opinion, the shorter codified names are easier to see at a glance what they are used for. For example, if there is a P in the name, be very careful not to kill it!

The environment is structured like this, with the highest level directory always being in the root of the drive.

f:\coyDapp1\server\c_bin
f:\coyDapp1\server\c_misc
f:\coyDapp1\server\c_system

The ini file(s) is in the c_bin folder, and named <envid>.ini, eg f:\coyDapp1\server\c_bin\coyDapp1.ini.

In my opinion, there is too much risk in NOT renaming ini files and environment names. Production ini files might have the details of SMTP servers, email addresses, etc that you don't want to use from dev or test. There are just a couple global replaces required in notepad to convert a coyPapp1.ini to a good coyUapp1.ini.

by Alan >> Thu, 29 May 2008 7:18:51 GMT

We used the structure described and it works well. In addition we have the INI files (named<envid>.ini,) in a separate "INIFiles" directory.
We have a separate "shortcuts" directory that includes a sub directory for each database (also named <envid>) .
We found by doing this the process of refreshing / copying systems and getting them up and running is slightly more simple - no need to remember to change INI files or shortcuts

by Aaron >> Fri, 30 May 2008 1:03:29 GMT

How would someone find the JadeCare Toolset?

by cnwjhp1 >> Fri, 30 May 2008 1:12:31 GMT

Go to http://www.jadeworld.com/, and click on the link at the bottom that says "Learn more about JADE Care".

by Aaron >> Fri, 30 May 2008 1:35:50 GMT

I have gone to that page but I am still unable to find any links to Documents that list the nameing convention?

by cnwjhp1 >> Fri, 30 May 2008 4:36:05 GMT

I have never seen it documented - but I have worked on such databases administered by others. I think what I provided was pretty much complete for the server side of things. There is a related thin client naming convention - without the \server folder - but I have used my own system for that, which is not suitable for production databases.