What does the SDK/J "end of support" mean for the future of my SDK/J xlet or servlet?

The SDK/J platform is now fully deprecated, and has reached the final phase of its end of support. This is in alignment with the global end of support for software products that require Java module. For RiDP offerings, the following phased approach for deprecation was in effect:

See the attached SDK/J Discontinuation Plan document for details about these phases.

This has the following implications for current and future SDK/J development:

• No new SDK/J ready devices are being released.
• Existing SDK/J ready devices no longer arrive with the SDK/J platform installed as a default configuration.
  • Ricoh Service may be able to apply the SDK/J platform to devices on a case-by-case basis.
• SDK/J device firmware and APIs are no longer maintained.
  • Any firmware or API fixes, even in the case of critical or security issues, will be evaluated on a case-by-case basis.
  • The latest CVM downloads will continue to be archived on this site.
• RiDP continues to offer limited support for existing SDK/J build tools, utilities, APIs, and SDKs.
  • Assistance will be limited to basic assistance with the development tooling, APIs, and SDKs.
  • This limited support will be offered at our discretion.
  • No effort will be made to ensure SDK/J tools, APIs, or SDKs work on modern programming environments.
  • While we strive to assist how we can, our limited ability to access legacy tooling may result in an inability to assist with technical issues related to the SDK/J platform.
• RiDP no longer offers any Compatibility Testing services for SDK/J applications.
  • RiDP and Ricoh Test has retired most SDK/J testing hardware.
• No new SDK/J application (xlets or servlets) development is permitted.
  • This means no new Product IDs can be generated.
  • Existing Product IDs will continue to work, and can still be re-branded if necessary.
• RiDP is no longer updating the SDK/J development kit. This includes all APIs and all DSDKs.
  • The DSDKs will remain at the version they are today.
    • The current DSDKs will continue work with the latest firmware and CVM releases.
  • Development kit documentation is no longer maintained beyond occasional compatibility note updates when firmware or CVMs are updated.
• Upon reaching the final phase (Phase 4, January 1, 2025) of deprecation all technical support for the SDK/J platform, APIs, and SDKs has officially ended.
  • RiDP will continue to provide a selection of online tools for managing those Product IDs.
  • RiDP will provide production signatures on a case-by-case basis.
  • RiDP will continue to provide the development and demo self-help signing servlets.
  • At some point after the final phase of deprecation all remaining SDK/J signing services and online tools will also be fully deprecated and removed from the site.
• Xlets and servlets will continue to run on existing SDK/J devices for the immediate future.
  • For security reasons changes may be required for some devices in 2025 that will disable all Java functionality.
  • If this impacts your customers they will need to reach out to Ricoh Customer Support in their region to coordinate device management.

Partners are encouraged to plan for this deprecation and migrate customers to the new SmartSDK platform.