design. develop. deploy.
The RXOP deliverable contains two servlet packages intended for use on the deprecated SDK/J platform: rxconfServlet and rxspServlet. At least one of these has a dependency on the BouncyCastle Provider library bcprov-jdk14-152.jar.
Sometimes an automated scan or manual inspection of this library will reveal that, as of RXOP v3.8.9, there are a number of known security issues with this dependency.
RXOP development often requires an "ACL file" which allows the RXOP application access to specific internal Service Program (SP) settings.
Since there are hundreds of SP settings that are accessible via RXOP, RiDP requires that RXOP application vendors request the minimal settings required for the application. An ACL request is simply a formatted pure text file (i.e., not a UTF-8 or binary file) containing key-value pairs that provides input to an automated process that will generate the ACL file used by the application.
An example file might look like this:
There are reports of a previously working RXOP application throwing a java.lang.SecurityException (wrapped inside a ricoh.rxop.rxcommon.RxopException) and failing to connect to a remote device.
The stacktrace will look something like this:
RicohJavaDevice provides methods for retrieving the device model name, but it can be observed that the model name is often empty [or "unavailable" if you use the RicohJavaDevice#debug() interface to log all the known device info]. Why is the device model name sometimes empty?
How to create an SOP app shortcut icon using RXOP
The following code sample shows how to create an application icon using RXOP
Notes:
import java.io.IOException;
import ricoh.rxop.rxconf.Configurator;
public class TestIconInstall {
How to reboot Ricoh MFP programmatically using RXOP.
RXOP library version 3.5.3 or higher is required. The recommendation is to reboot both the controller and the smart operation panel, choosing this option ensures the Android app stays in sync with the controller.
Note for the value " both(true) " it means to reboot the SOP and the controller. If false, only the panel will be rebooted.
===========
import ricoh.rxop.rxcommon.RxopException;
import ricoh.rxop.rxinst.RicohJavaDevice;
public class test {
How to create ACL file for RXOP usage
The ACL file is used by RXOP; RXSP’s component to be more specific; to change System Program modes programmatically. These modes are commonly referred as SP modes, the SP modes are used to set specific device configurations needed by applications. Example: setting SP modes for custom authentication.
The Access Control List (ACL) relied on device hex codes to identify a specific device to set the different SP modes.
Example:
IM 350 àHex code is 990003 (using the last 6 hex digits as listed on device info PDF file)
Below are the steps for updating the ROC client Tool as new revisions of the RXOP library are released:
* instructions refer to a generic RXOP version, the versioning may change, replace file versions accordingly
1. Under \[root dir]\roc-ridp-x\lib - Replace the rxop.jar from the \[root dir]\RXOP-3.x.x\lib
2. Under \[root dir]\roc-ridp-x\lib - Replace the rxcommon.jar from the \[root dir]\RXOP-3.x.x\lib\ dep-libs
3. Under \[root dir]\RXOP-3.x.x\lib\components, extract the rxspServletPackage.zip file.
From RXOP 3.3+ the device looking feature was introduced and an operation may fail if RXOP is not able to lock the device to perform the remote operation.
One reason for failure can be due to SSL being turned on on the device. The locking feature was implemented because of the need for locking a device when updating an application during times when customers are accessing the devices.
So if this doesn't really pertain to your customers environment you can disable this feature with a call to: --lock-off In the code.
e.g.: