Compatibility Testing

VMware Submission Process

The process of sending VMware images for testing will be discontinued in favor of a new process. To perform the compatibility test of solutions in RiDP Test environment, Ricoh will require developers to upload, install, configure and test the application server software onto a Windows based system remotely. In order for Ricoh to have on-site access to 3rd party back-end servers, developers will configure a server on a VMware image running at Ricoh.

Instructions for implementation of the VMware Submission Process:

In situations when you can’t setup your Virtual machine remotely, you’ll have to revert to the old format of sending USB sticks.

Two separate images need to be sent. One for PTEC (New Jersey) and another for RiDP (California). Below are the addresses for each location.
VMware Shipping Addresses:

1. Mail 1st set of USB Memory Stick(s) to:
Ricoh Americas Corporation
Attn: Vasantha Yerneni
5 Dedrick Place
West Caldwell, NJ 07006

The performance compliance cycle for Web BrowserNX application is as follows:

To develop your Web BrowserNX application

- Obtain a developer access token

To submit your application for CT (compliance testing)

- Follow same CT submission for testing

- We will create a production token that will be valid for every Ricoh's SmartSDK enabled device

- Production token will be embedded into your application while we test your solution

- Upon compliton of CT, PTEC will release "production" token for your application usage.

Here are 3 recommendations for providing virtual machines for both PTEC and the RiDP support staff: