Does the ESCI Client really use the admin user to execute and log it job........

Submitted by Guest on Tue, 18/06/2013 - 12:27

General developer's discussion

Probably need to either create a SYSTEM user that doesnt appear in the user list or do this some other way.

I didnt want a random unused user account on our system so I removed it. No error is generated when your using the system, but these errors pepper the logs.
	  
 17 Jun 2013 17:30:00,031 ERROR JobRunShell,scheduler_Worker-5:225 - Job DEFAULT.esciDispatcherJob threw an unhandled Exception:
java.lang.IllegalArgumentException: User 'admin' does not correspond to a valid user
    at org.openvpms.esci.adapter.dispatcher.quartz.ESCIDispatcherJob.initSecurityContext(ESCIDispatcherJob.java:135)
    at org.openvpms.esci.adapter.dispatcher.quartz.ESCIDispatcherJob.execute(ESCIDispatcherJob.java:111)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)  

Re: Does the ESCI Client really use the admin user to ...

Submitted by tanderson on Tue, 18/06/2013 - 13:33.

ESCI periodically checks your supplier for invoices and order responses.

It needs to be executed as a user with sufficient permissions to create deliveries, update orders, and create system messages.

Currently, the user is configured via the openvpms-esci.xml file in WEB-INF/ using the runAs attribute i.e:

     <bean id="scheduler" class="org.springframework.scheduling.quartz.SchedulerFactoryBean">
        <property name="jobFactory">
            <bean class="org.springframework.scheduling.quartz.SpringBeanJobFactory"/>
        </property>
        <property name="schedulerContextAsMap">
            <map>
                <entry key="ESCIDispatcher" value-ref="esciDispatcher"/>
                <entry key="ArchetypeService" value-ref="archetypeRuleService"/>
                <entry key="runAs" value="admin"/>
                <!-- change this to a valid user -->
            </map>
        </property>
        <property name="triggers">
            <list>
                <ref bean="esciDispatcherCronTrigger"/>
            </list>
        </property>
        <property name="quartzProperties">
            <props>
                <prop key="org.quartz.plugin.jobHistory.class">org.quartz.plugins.history.LoggingJobHistoryPlugin</prop>
            </props>
        </property>
    </bean>

-Tim