Freeflow Core not sending response to uStore

[TheChainer]

As an update, they pushed our update to 8.6 without letting me know - However upon testing the callbacks are working correctly and jobs are moving appropriately.

So, problem solved.

Thanks as always, Javier!

[JavierM-Xerox]

There were some changes made to JMF to better align with CIP4. That caused a small ilily issue with uStore which XMPie corrected. 

I don't know too much about it on the uStore end. I would ask your XMPie Rep. 

[TheChainer]

Forgot to follow up with this, almost. 

I was 'hinted' toward the fact that 5.0.0.2 has an issue with communicating back to 8.3 when a job is completed - and that the issue is more on the side of uStore.

We will be getting out upgrade to 8.6 shortly, and I was told that should fix the communication issues.

Food for thought, I suppose.

[JavierM-Xerox]

That's a question that only XMPie can answer. They test our releases to determine whether the release can be supported with their upcoming versions of software. 

[TheChainer]

Javier,

Is 5.0.0.2 compatible with uStore 8.3? Spoke with our contact for XMPIE and they suggested it may be something along that line.

Thanks!

[JavierM-Xerox]

If there's question about what FFCore is doing I would suggest engaging the hotline for FFCore.

[TheChainer]

Checking the mantis debug logs, it looks like the response is being sent via localhost:5522 and other seemingly random ports on the Core side.

I've initiated with XMPIE as well with a fail to receive or parse JDF being the pertinant item I'm seeing in the uStore logs.

Thanks Javier!

Karl

[JavierM-Xerox]

The client would be uStore.

9090 is the port used by Alces. 

The port that you need to open would be based on what uStore requires. I do not know that port number.

[TheChainer]

Defined by which client? Do you mean uStore or Freeflow Core?

In the case of 9090 being the port for the status signal - I would need to open that port up in the fire wall to communicate with uStore, correct?

[JavierM-Xerox]

JMF Status signals are sent to the URL defined by the client.

For example:

<?xml version="1.0" encoding="utf-8"?>
<JMF SenderID="JDFEmitter" TimeStamp="2014-04-24T15:34:35-04:00" Version="1.4" xmlns="http://www.CIP4.org/JDFSchema_1_1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Query ID="JMF_877558998" Type="Status" xsi:type="QueryStatus">
<StatusQuParams DeviceDetails="None" JobDetails="None" QueueInfo="false" />

<Subscription URL="http://localhost:9090/alces/jmf" />
</Query>
</JMF>

In the above case, the port number would be 9090. As such, the port number is defined by uStore.

If you are unsure about how the JMF subscription URL is configured, I would suggest asking your XMPie.