ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Brohl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-9594) Perfect of Ofbiz
Date Thu, 05 Oct 2017 15:16:00 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-9594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193004#comment-16193004

Michael Brohl commented on OFBIZ-9594:

Hi [~medjo],

can you please answer the questions and provide more informations for your issue. Else I will
close this ticket as "Not a problem" in 7 days.


> Perfect of Ofbiz
> ----------------
>                 Key: OFBIZ-9594
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9594
>             Project: OFBiz
>          Issue Type: Bug
>          Components: ALL COMPONENTS
>    Affects Versions: 16.11.03
>         Environment: Hosting Environment: Web.config and database details externalize
the <service>
>            Reporter: Roger Mbiama
>            Assignee: Michael Brohl
>              Labels: features
> Log Rules for .NET 7.1.1
> Ofbiz Service configuration
> configuration and set-up tasks:
> Configure the Execution Service:
> You need to specify the deployment directory for the business object model (BOM) and
other DLLs needed to run the Execution Service, link the Execution Service to the Persistence
Service, and specify the required Windows Management Instrumentation (WMI) settings.
> Create an Execution Service client application:
> You need an application to host the Execution Service client. Any application can host
an Execution Service client.
> Deploy the execution environment:
> The execution environment is a directory specified by the ILOG.Rules.ExecutionServer.Execution.BaseDirectory
property in the Execution Service configuration file.
> Configure remote rule execution using Internet Information Services (IIS):
> You need only carry out this task if you want to use remote rule execution.

This message was sent by Atlassian JIRA

View raw message