nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CMS directory

shirinp

Hello,

I have been using the sdk for a while now, but I can't remember what the CMS directory is used for and I can't seem to locate it's purpose in the documentation

SessionFactory->setCmsDir(CmsDir);

Can someone tell me what it's used for, and if I should be setting a specific path for it? Up until now, I've been just setting it to my own path... Should it be taking a specific path?

Thanks!

Find more posts tagged with

Comments

Migrateduser

I do not remember seeing a SessionFactory class in Java WOM, probably you are talking about WOMCOM. Please read-on anyway; the following info might be useful.

I set the cms.dir java system property so that the WOM can get to a couple of CMS files it requires. The directory pointed to by cms.dir varibale should have a sub directory 'config' and 'config' dir need to contain 'code' and 'log' sub directories from your '

cms-server-install-dir/config' directory. So the directory structure on client side would be

cms.dir[indent]config[indent]code
log
[/indent][/indent]'code' directory contains some error codes info used by WOM exceptions. 'log' directory contains the log4j configuration data used by WOM. When you run your SDK client program, WOM will create its logs under /logs/ directory.

Hope that helps.

shirinp

Well, I'm using the WOMCOM... I see that if you do set the path to the install directory, that it updates the log files, etc. So, I guess I'm faced with a few questions.

1) How do I obtain the installation directory? Should I be getting it from a registry key?

2) What do I do if the client I create using the womCOM is not on the same machine as the server? What are the implications of setting it to another directory?

Any help on this will be much appreciated!

I do not remember seeing a SessionFactory class in Java WOM, probably you are talking about WOMCOM. Please read-on anyway; the following info might be useful.

I set the cms.dir java system property so that the WOM can get to a couple of CMS files it requires. The directory pointed to by cms.dir varibale should have a sub directory 'config' and 'config' dir need to contain 'code' and 'log' sub directories from your 'cms-server-install-dir/config' directory. So the directory structure on client side would be

cms.dir[indent]config[indent]code
log
[/indent][/indent]'code' directory contains some error codes info used by WOM exceptions. 'log' directory contains the log4j configuration data used by WOM. When you run your SDK client program, WOM will create its logs under /logs/ directory.

Hope that helps.

Migrateduser

Here are my suggestions:

If you are writing a custom WOMCOM program, i would recommend to create a new cms.dir and copy the directories/files mentioned below from your cms server installation. Please package your cms.dir along with your program.
The answer #1 above should take care of this issue.

Please let me know if it does not answer your questions completely.

-bijoy

shirinp

So, I guess I'm still wondering if it's necessary to do all of this. I'm assuming that the only purpose of this is to log transactions between the Server and output error messages. Is that correct? Since I'm not too concerned with either, especially since the clients that I'm creating will probably not be on the same machine, is it necessary for me to do all of this? Is it ok if I still designate some temporary folder that is not configured to the actual installation directory of the server?

Migrateduser

It may not be necessary depending on how things go. If your client throws up some errors which you might what IWOV support to look into, these logs might be the first thing they would ask. (It is like the extra forms to fill in to receive the free product warranty. :-) Believe me, I never do it, because I cannot anticipate the product failure when I open the package and throw the warranty card into trash. When the product fails, the warranty card is sure needed and I will have to jump few hoops before I can get the manufacturer take care of it)

Note that this directory just needs to be present (with config sub dir and its contens as described below) in the client system. I would package it with the client program.