Create a keystore on the IBM i platform - InterFormNG2 Manual

Create a keystore on the IBM i platform

You might need to create a keystore on the IBM i platform, e.g., for the preview client or the remote client. The steps below explain how to do this in detail.

WarningDo NOT place the keystore file inside any of the InterFormNG2 data or program directories, as a future upgrade might delete or move the keystore file.

1) Start a command crompt on IBM i

  • Find a command prompt on IBM i.

  • Run the following command to start QShell:

STRQSH

2) Create the keystore file

Run one of the following commands:

For the keystore supporting the strongest encryption

keytool -genkeypair -alias previewclient -keyalg RSA -keysize 2048 -storetype PKCS12 -keystore /iformng2/previewclient.jks -validity 3650

​

Alternative: If PKCS12 keystore is not supported on IBM i

If the PKCS12 keystore is not supported, use this command instead:

keytool -genkeypair -alias previewclient -keyalg RSA -keysize 2048 -storetype JKS -keystore /iformng2/previewclient.jks -validity 3650

3) Respond to keystore prompts

  NG2Keystore0002

​

  • You will be asked multiple questions about the keystore.

  • Finally, confirm the creation by typing:

yes

After this, a new keystore file named:

remoteprint.jks

will be created in the /IFORMNG2 directory in the IFS (Integrated File System).

4) Copy the keystore file & note the password

  • Copy the keystore file from the host to the remote client.

  • Make a note of the keystore password, as you will need it when configuring:

    • InterFormNG2 host

    • Preview clients

5) Referencing the keystore in InterFormNG2

The host system configuration can refer to the keystore file like so:

​

  NG2Keystore0003

6) Continue with the preview client setup

Now that the keystore file has been created and configured, you can proceed with the setup of your preview client.

    Notice: Help Center Transition Update

    As of January 13, 2025, we are excited to announce that our new Help Center is in the final stages of development. While the Knowledge Base is already accessible, our current JIRA system will continue to manage support tickets during this transition period. For assistance with InterForm Output Management Software, please refer to the Support for InterForm Output Management Software.

    We appreciate your patience and understanding as we work to enhance your support experience. If you have any questions or encounter any issues, please do not hesitate to reach out via the existing support channels.

    Best regards,
    The InterForm Support Team


      • Related Articles

      • Create a keystore on the Windows platform

        You might need to create a keystore on the Windows platform, e.g., for the preview client or the remote client. The steps below explain how to do this in detail. 1) Open a Command Prompt Start a command prompt. You can do this by searching for an app ...

      • Create a keystore for the preview client

        Please note: The remote preview client application has been decommissioned in version 3.5.1 and all related settings have been removed. It is only available for previous versions. The articles will be removed soon. The section below describes how you ...

      • Connecting to AS400 from another platform

        Connecting to AS400 from another platform : The section below describes the steps to go through, if you want to monitor output queues with spooled files on the IBM i platform from an InterFormNG2 installation on another platform e.g. Windows or ...

      • Create PDF file

        The Create PDF file workflow component is found under Basic and create document. This component accepts an XML file as input. The component creates a PDF file and stores it directly in the file system. The output payload is the same as the input ...

      • Move InterfoNG2 from IBM i to another platform

        This section is meant as an aid for the customers, that already has InterFormNG2 running on the IBM i platform, but want to move core InterFormNG2 onto another platform. The reasons for doing that can e.g. be: •Free up resources on the IBM i and move ...