We have recently installed Loftware Spectrum on a new server and are currently working on integrating it with the DSI application server using the Loftware Print Agent deployed at the remote site.
As part of our initial validation, we have confirmed that network connectivity between the involved servers is functioning correctly:
Successful ping communication between the DSI application server and the Spectrum server.
Successful telnet connectivity verification on the required ports between both servers.
Communication between the servers appears to be established without any network-related issues.
Additionally, when we submit a print job directly from Loftware Spectrum, the job is processed successfully and the labels are printed as expected.
However, we are encountering an issue when initiating label printing from the DSI application through the EnterpriseOne XML Connector:
The Function Test within the XML Connector returns a successful result.
No errors are reported during the test execution.
Despite the successful response, the labels are not printed.
The print job does not appear in the Spectrum Job Status/History, indicating that the request may not be reaching the Spectrum server for processing.
At this point, we would like to understand whether anyone has experienced a similar issue with the DSI EnterpriseOne XML Connector and Loftware Spectrum integration. We would appreciate any guidance on the following:
How to verify whether the XML requests are actually reaching the Spectrum server.
Relevant logs on the DSI, XML Connector, or Spectrum side that should be reviewed for troubleshooting.
Any known configuration requirements or integration parameters that must be validated for EnterpriseOne XML Connector communication with Spectrum.
Recommended troubleshooting steps to ensure print jobs are successfully submitted and processed by Spectrum.
Any suggestions or insights would be greatly appreciated.
The MEPEnterpriseOne XML Connector is intended for integrations with JDE E1 / EnterpriseOne systems, and is not a generic XML connector, so I would not expect it to be able to integrate directly with a Loftware Spectrum server. Additionally, our MEP Printing Agent does not currently support direct integrations with Loftware Spectrum.
There are two methods I’m currently aware of for MEP to Loftware Spectrum integrations, but we don’t have any standardized/sample guides specifically detailing either.
Implementing a NiceLabel 10 server w/ an LPS Trigger automation, configured to route request data to a Loftware Spectrum RESTful API endpoint.
We don’t have any documentation outlining this exact scenario, but I have a guide outlining the MEP Printing Agent to NiceLabel 10 print server here, Printing Agent to NiceLabel 10.3. You can reference this guide for most of the integration, but change the NiceLabel automation to send the PAS request data that MEP generates to the Spectrum server, instead of printing the labels itself.
Create MEP service definitions to send the print requests to Loftware Spectrum through web service calls.
The MEP Application Studio service definitions allows developers to create custom web service integrations that can be used in your MEP apps or subapps. You can pass the XML request data through a simple #rawtext input.
I hope this information helps get you on track toward a solution.
To help us understand the implementation approach better, could you please share any sample custom web service integration created using MEP Application Studio Service Definitions that can be used in MEP applications or subapps?
Specifically, we would appreciate:
A sample service definition configuration.
An example of passing XML request data through the #rawtext input parameter.
A sample web service call (request/response format).
Any example integration with an external system similar to Loftware Spectrum.
Having a sample implementation would help us validate the design and accelerate development of the print request integration with Loftware Spectrum.
Unfortunately, I don’t have any direct experience or samples for implementing service definitions integrating with Loftware Spectrum, and there are no standardized MEP application objects for Loftware Spectrum printing to share; especially for MEP 8.5 SP4, which is a very old MEP version. I would definitely recommend you plan to upgrade to a newer MEP version.
The below screenshot is an example of an ‘EPP_SendLabel’ service definition from MEP 9.7, used to send print requests to our EPP print server product. I assume this could be similarly implemented for a Loftware Spectrum endpoint, but I’m not familiar with the Spectrum API options and requirements.
We do have details about the MEP service definitions published in our docs pages.
Select the help icon from any MEP page and navigate to ‘Platform Manager > Develop > Application Studio > Service Definitions’.