completely disabling default applications

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

completely disabling default applications

Rex Posadas
To All,

 

Even though we can disable features thorough the permissions system, is
there a way to completely disable some of the default applications (
such as HR and Marketing ) so they do not even exist as part of the
system? Short of stripping out the code and dealing with all of the
issues associated that.

 

 

Thanks.

Rex

Reply | Threaded
Open this post in threaded view
|

Re: completely disabling default applications

Ruth Hoffman-2
Hi Rex:
There are a couple of things you could try:

First, you could try disabling the entire Component(s) of interest by
editing the "component-load.xml" file located in the ~applications
directory. Comment out the Components you are interested in disabling
and restart OFBiz. If you do this and are able to restart OFBiz without
fatal errors, then all is well.

If you find there are some dependencies on these Components (for example
some services are called by other parts of OFBiz), then you might try to
disable just the webapp(s) for the Component(s) of interest. Although
this does not disable any of the OFBiz services and/or other tools
available from these Components (because they are loaded on the
classpath at startup), disabling the webapp disables all the URL/URIs
configured for that application - so no browser access . You would do
this by commenting out the appropriate lines in the ofbiz-component.xml
file in the Component(s) of interest.

Of course, if you do this, then you need to be aware that if someone
navigates to one of the disabled URLs, they will get a nasty error message.

Good Luck.

Ruth Hoffman
http://www.myofbiz.com
http://www.aesolves.com

On 8/25/11 1:56 PM, Rex Posadas wrote:

> To All,
>
>
>
> Even though we can disable features thorough the permissions system, is
> there a way to completely disable some of the default applications (
> such as HR and Marketing ) so they do not even exist as part of the
> system? Short of stripping out the code and dealing with all of the
> issues associated that.
>
>
>
>
>
> Thanks.
>
> Rex
>
>
Reply | Threaded
Open this post in threaded view
|

RE: completely disabling default applications

Rex Posadas
Thank you, Ruth.

That worked for the applications I wanted to disable.

-----Original Message-----
From: Ruth Hoffman [mailto:[hidden email]]
Sent: Thursday, August 25, 2011 1:54 PM
To: [hidden email]
Subject: Re: completely disabling default applications

Hi Rex:
There are a couple of things you could try:

First, you could try disabling the entire Component(s) of interest by
editing the "component-load.xml" file located in the ~applications
directory. Comment out the Components you are interested in disabling
and restart OFBiz. If you do this and are able to restart OFBiz without
fatal errors, then all is well.

If you find there are some dependencies on these Components (for example

some services are called by other parts of OFBiz), then you might try to

disable just the webapp(s) for the Component(s) of interest. Although
this does not disable any of the OFBiz services and/or other tools
available from these Components (because they are loaded on the
classpath at startup), disabling the webapp disables all the URL/URIs
configured for that application - so no browser access . You would do
this by commenting out the appropriate lines in the ofbiz-component.xml
file in the Component(s) of interest.

Of course, if you do this, then you need to be aware that if someone
navigates to one of the disabled URLs, they will get a nasty error
message.

Good Luck.

Ruth Hoffman
http://www.myofbiz.com
http://www.aesolves.com

On 8/25/11 1:56 PM, Rex Posadas wrote:
> To All,
>
>
>
> Even though we can disable features thorough the permissions system,
is

> there a way to completely disable some of the default applications (
> such as HR and Marketing ) so they do not even exist as part of the
> system? Short of stripping out the code and dealing with all of the
> issues associated that.
>
>
>
>
>
> Thanks.
>
> Rex
>
>