Configuration

In the values.yaml file, under the microexecutors field define the AS/400 Proxy deployment as follows, especially specifying the AS/400 connection parameters.

For additional configurations, refer to MicroExecutor Specification.

name: me-java-as400proxy
replicaCount: 1
image:
    name: 100076361442.dkr.ecr.eu-south-1.amazonaws.com/kokos-java-as400proxy
    tag: latest
internalPort: 8001
resources: {}
env:
    # AS/400 id
    A4P_SUFFIX_ID: 
    # AS/400 server
    A4P_SERVER: 
    # AS/400 user
    A4P_USER: 
    # AS/400 password
    A4P_PASSWORD:
    # Concurrent fun that can be handled
    A4P_CONC_FUN:

Login

The legacy login is enabled through specific configurations for the Kokos environment, whereas the AS/400 environment is specified in the service parameters. Each instance of the microexecutor connects to a single AS/400 server, as specified in the Kubernetes deployment. At startup, it uses a service account for initial authentication. When a user logs into their preferred environment, the microexecutor creates a session for that user. Below is an example:

ges_demo:
  libs:
  - kokos-dsl-smeup-legacy-srvlab01-develop
  authentication:
    customAuthentication:
      enabled: true
      serviceName: WE_110_04
      serviceParams: ENVIRONMENT(GES_DEMO) CCSID(1144)

Service Routing

# Micro Executor List
handlers: 
  me-java-as400proxy:
    url: http://me-java-as400proxy  
    default: true

# Services
services:
  names:
    SRV_001:
      handler: me-java-as400proxy

Since we've set the me-java-as400proxy as the default microexecutor, any services without a designated handler will automatically be redirected to it. This means you only need to specify services that are handled by a different microexecutor if you want them to be processed here (SRV_001 in the example). Additionally, with the KokosFallbackService, any services not listed in the registry.yaml file will, by default, be managed by this class, which routes them to the AS/400 backend.