Hi,
I have an issue with WorkManager 6.0 Order Push scenario on SMP2.3 and Agentry DEV server.
We want to push PM Workorders with priority VeryHigh to the device.
We have installed SMP2.3 SP03 PL01, WorkManager 6.0.
Client Device is a Windows 7 64Bit Laptop.
Development is done on Windows7, 64Bit Windows PC
Data processing works fine, either against SMP2.3 or directly with Agentry Dev server on local dev pc.
I went through the Setup and the Config guide to setup backend and server for WorkOrder Push.
As shown in the dev guide I did not change anything on the server - based on the setup guide the settings seem to be correct.
On the local server installation I did change the setting in JaveBE.ini file:
[PUSH_LOGON]
ENABLED=true
UID=<bckUser>
UPASSWORD=<bckPassword>
UPASSWORDENCODED=true
SHAREDCONNECTION=10
I can see in the startup log, that the connection to the backend works. As I was playing around and did enter a wrong password, it gave me an exception. So I think from that it takes these settings and it should work fine.
If I check entries in tables /SYCLO/PSH01 and /SYCLO/PSH05 I can see there are the correct order numbers shown.
But: in monitoring I am not able to see that anything gets pushed and the PURGE_PROC does not deliver any results either.
Running the PUSH_PROC_PROG did not solve the issue - I did that cause I thought I would give it a try.
If I try to connect to my local development server with a different client to the server using my username, it tells me I am already connected with a different client. And in SMP2.3 monitoring my user is shown as an active user. So from that my clients should be connected to the server as well.
I went through the config guide a few times and still I am not able to see what the issue might be.
So in simple words: what am I missing here? Is there a simple setting I am missing or do I have a complete missunderstanding of the process?