Page tree
Skip to end of metadata
Go to start of metadata

Typically, card operations in 3.8 - Nexus PRIME are performed on the client machine. However, there are use cases where it is necessary to perform card operations on the server-side, executing encodings with the JPKIEncoder or Nexus Card SDK. Examples are card operations using a Nexus IDBox, card encodings using a tunneling server or card operations for network smart cards. Any created certificates are persisted in PRIME exactly as with client-side card operations. The card operation can be triggered by a user or a BPMN timer.

Configure PRIME

The Card SDK needs the PRIME URL in order to make sure its JPKIEncoder is up to date. A JPKIEncoder running as an external process (through Card SDK or standalone) needs the PRIME URL in order to request certificates from the Certificate Authority (CA).

To configured it:

  1. Log in to PRIME Explorer as an administrator.
  2. In PRIME Explorer, go to Admin > Configure System Properties > serverContext > PRIME Server URL.
  3. Set this to PRIME's base URL, for example, https://example.com:8443/prime_explorer
  4. Log in to PRIME Designer as an admin user and create a new process as described in 3.8 - Set up process.
  5. Add a new Service Task to your process, and go to its edit menu:
    1. Set the Delegate Expression to "${serverSideCardOperationTask}
    2. Add a parameter named "encodingName" with the name of the encoding as a value.
    3. Optional: Add a parameter named "cardSDK". Set it to "true" if you want to use the Card SDK for card operations. By default the internal encoder is used.

Configure production component

The Card SDK URL defaults to http://localhost:54880. You can change that in system.properties to, for example, the default HTTPS port of Card SDK (54881):

system.properties

cardSdkService.url = https://localhost:54881

This article is valid from Nexus PRIME 3.8.

Related information

  • No labels