1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. Use Cases for Adding Profiles, Deployments, or Adding Resources to Individual Siebel Servers

Use Cases for Adding Profiles, Deployments, or Adding Resources to Individual Siebel Servers

This topic provides detailed information about changes to make to support use cases for adding profiles, deployments, or for adding resources to individual Siebel Servers. No restarts required in these use cases. This topic is part of Use Cases for Making Incremental Changes.

Use Cases for Adding Profiles or Deployments

Use Case/Notes Sample Data Format

1. Increase replicas (for ses, sai) or Change resources for individual Siebel Servers (not for sai servers)

Note: sesResources defined at the profile level for individual Siebel server takes higher precedence over the generic sesResources overridden in payload.

File:

siebel.yaml

Notes:

  • Edit siebel.yaml under:

    /home/opc/siebel/<env_id>/<Cloud manager repository name>/flux-crm/apps/base/siebel

  • Increase replicas under siebelServer for the respective pod, using these commands:

    git pull

    git add .

    git commit -m "<message>"

    git push

For cgw replica number value change, the siebel-gateway.yaml and siebel-config.yaml should be changed.

 
siebelServer:
  - profile: siebel
    replicas: 3
    sesResources:
      limits:
        cpu: 4
        memory: 24Gi
      requests:
        cpu: 1
        memory: 8Gi
    siebsrvr_prefix: edge
  - profile: siebel
    replicas: 3
    sesResources:
      limits:
        cpu: 4
        memory: 24Gi
      requests:
        cpu: 1
        memory: 8Gi
    siebsrvr_prefix: tibus
saiServer:
- profile: sai_lily
  replicas: 2
  sai_prefix: quantum
- profile: slc15zny95121
  replicas: 2
  sai_prefix: alchemist

2. Add a new Siebel Server profile

File:

New YAML file

Notes:

  • Create file name with prefix server_ (for example, server_lily.yaml).
  • Under the server name are:
    • component_groups has all comp group and comp details
    • parameters has server level parameters
    • deployment is used during server deployment
    • Profile is used to create server profile
  • Modify all occurrences of the following, according to your configuration:
    • <namespace>
    • <profile_name>
    • <username>
    • <password>
    • <guest username>
    • <guest password> 
server_lily:
  component_groups:
    CallCenter:
      components:
        SCCObjMgr_enu:
          definition:
            CC_ALIAS: SCCObjMgr_enu
            CC_RUNMODE: Interactive
            CG_ALIAS: CallCenter
            CT_ALIAS: AppObjMgr
          parameters:
          - basic_params:
            - PA_ALIAS: MaxTasks
              PA_VALUE: '200'
            url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/servers/server_name/components/SCCObjMgr_enu/parameters
          url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/servers/server_name/components/SCCObjMgr_enu
        SServiceObjMgr_enu:
          definition:
            CC_ALIAS: SServiceObjMgr_enu
            CC_RUNMODE: Interactive
            CG_ALIAS: CallCenter
            CT_ALIAS: AppObjMgr
          parameters: []
          url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/servers/server_name/components/SServiceObjMgr_enu
        eServiceObjMgr_enu:
          definition:
            CC_ALIAS: eServiceObjMgr_enu
            CC_RUNMODE: Interactive
            CG_ALIAS: CallCenter
            CT_ALIAS: AppObjMgr
          parameters:
          - basic_params:
            - PA_ALIAS: MaxTasks
              PA_VALUE: '222'
            url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/servers/server_name/components/eServiceObjMgr_enu/parameters
          url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/servers/server_name/components/eServiceObjMgr_enu
      url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/compgroups/CallCenter
 deployment:
    DeploymentInfo:
      ProfileName: <profile_name>
    ServerDeployParams:
      DeployedLanguage: enu
      PrimaryLanguage: ENU
  parameters:
  - basic_params:
    - PA_ALIAS: CFGEnableOLEAutomation
      PA_VALUE: 'False'
    - PA_ALIAS: MaxThreads
      PA_VALUE: '11'
    url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/servers/server_name/parameters
  - hidden_params: []
    url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/servers/server_name/parameters?hidden=true
  - advanced_params: []
    url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/enterprises/enterprise_name/servers/server_name/parameters?advanced=true
  profiles:
    Profile:
      LastUpdated: 
      ProfileName: <profile_name>
    ServerConfigParams:
      AnonLoginPassword: <guest password>
      AnonLoginUserName: <guest username>
      CACertFileName: null
      CertFileNameServer: null
      ClusteringEnvironmentSetup: NotClustered
      Db2InstHome: ''
      EnableCompGroupsSIA: CallCenter
      Encrypt: null
      LocalSynchMgrPort: '40400'
      ModifyServerAuth: null
      ModifyServerEncrypt: null
      NameserverHostName: siebelcgw-0
      NamesrvrPort: '8888'
      Password: <password>
      SCBPort: '2321'
      SiebelClusterGateway: null
      SiebelEnterprise: siebel
      SqlServerPort: null
      UseOracleConnector: 'true'
      Username: <username>
    url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/profiles/servers

3. Add a new Siebel Application Interface profile

File:

New YAML file

Notes:

  • Create file name with prefix sai_ (for example, sai_trust.yaml).

  • Under profiles, modify all occurrences of the following according to your configuration:

    • <namespace>

    • <profile_name>

    • <guest username>

    • <guest password> 

sai_trust:
  profiles:
  - ConfigParam:
      Applications:
      - AnonUserPool: 0
        AppDisplayName: ''
        AppDisplayOrder: 0
        AppIcon: ''
        AuthenticationProperties:
          AnonPassword: <guest password>
          AnonUserName: <guest username>
          GuestSessionTimeout: 300
          MaxTabs: 1
          SessionTimeout: 900
          SessionTimeoutWLCommand: HeartBeat
          SessionTimeoutWLMethod: UpdatePrefMsg
          SessionTimeoutWarning: 60
          SessionTokenMaxAge: 2880
          SessionTokenTimeout: 900
          SingleSignOn: false
          TrustToken: ''
          UserSpec: ''
AvailableInSiebelMobile: false
        EAISOAPMaxRetry: 0
        EAISOAPNoSessInPref: false
        EnableExtServiceOnly: false
        Language: enu
        Name: callcenter
        ObjectManager: sccobjmgr_enu
        StartCommand: ''
        UseAnonPool: false
      ConnMgmt:
        CACertFileName: ''
        CertFileName: ''
        KeyFileName: ''
        KeyFilePassword: ''
        PeerAuth: false
        PeerCertValidation: false
      DAV:
        LogProperties:
          LogLevel: ERROR
      EAI:
        LogProperties:
          LogLevel: ERROR
GatewayIdentity:
        AuthToken: null
        GatewayHost: siebelcgw-0
         GatewayPort: '8888'
 RESTInBound:
        Baseuri: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/
        LogProperties:
          LogLevel: ERROR
        MaxConnections: 20
        ObjectManager: sccobjmgr_enu
        RESTAuthenticationProperties:
          AnonPassword: <guest password>
          AnonUserName: <guest username>
          AuthenticationType: Basic
          OAuthEndPoint: ''
          SessKeepAlive: 120
          TrustToken: ''
          UserSpec: ''
          ValidateCertificate: true
        RESTResourceParamList: []
      RESTInBoundResource: []
      RESTOutBound:
        LogProperties:
          LogLevel: ERROR
      SOAPOutBound:
        LogProperties:
          LogLevel: ERROR
      UI:
        LogProperties:
          LogLevel: ERROR
      defaults:
        AuthenticationProperties:
          AnonPassword: <guest password>
          AnonUserName: <guest username>
          GuestSessionTimeout: 300
          MaxTabs: 1
          SessionTimeout: 900
          SessionTimeoutWLCommand: HeartBeat
          SessionTimeoutWLMethod: UpdatePrefMsg
          SessionTimeoutWarning: 60
          SessionTokenMaxAge: 2880
          SessionTokenTimeout: 900
          SingleSignOn: false
          TrustToken: ''
          UserSpec: ''
        DoCompression: false
        EnableFQDN: false
        FQDN: ''
 swe:
        AllowStats: true
        Language: ENU
        MaxQueryStringLength: -1
        SeedFile: ''
        SessionMonitor: false
    Profile:
      AccessPermission: ReadWrite
      LastUpdated: 
      ProfileName: <profile name>
  url: https://smc-0.smc.<namespace>.svc.cluster.local:4430/siebel/v1.0/cloudgateway/profiles/swsm

4. Deploying a Siebel Server

File:

siebel.yaml

Notes:

  • Ensure that the status of the configure job that is launched when the Siebel Server profile is added is "Completed".

    source /home/opc/siebel/<env_id>/k8sprofile

    kubectl -n <namespace> get po -l batch.kubernetes.io/job-name=configure

    If the status of configure job is "Running", the deployment will fail and the SES profile will not appear in SMC even if the pod status is "Running".

  • Edit siebel.yaml under:

    /home/opc/siebel/<env_id>/<Cloud manager repository name>/flux-crm/apps/base/siebel

  • Add a new ses section under siebelServer.

  • If you do not see the deployment in SMC, check pod logs to find progress or error information.

  • The <server prefix> must be unique and be the same as the profile filename suffix: for server_lily.yaml, <server prefix> would be lily. 

siebelServer:
- profile: <siebserver profile name>
  replicas: 1
  siebsrvr_prefix: <server prefix>
  sesResources:
    limits: 
	  cpu: 4
	  memory: 24Gi
	requests:
	  cpu: 1
	  memory: 6Gi

5. Deploying a Siebel Application Interface

File:

siebel.yaml

Notes:

  • Before you begin the deployment, ensure that the status of the configure job that is launched when the Siebel Application Interface profile is added is "Completed":

    source /home/opc/siebel/<env_id>/k8sprofile

    kubectl -n <namespace> get po -l batch.kubernetes.io/job-name=configure

    If the status of configure job is "Running", the deployment will fail and the SAI profile will not appear in SMC even if the pod status is "Running".

  • Edit siebel.yaml under:

    /home/opc/siebel/<env_id>/<Cloud manager repository name>/flux-crm/apps/base/siebel

  • Add a new sai section under saiServer.

  • If you do not see the deployment in SMC, check pod logs to find progress or error information.

  • The <sai prefix> must be unique and be the same as the profile filename suffix: for sai_trust.yaml, <server prefix> would be trust. 

 saiServer:
    - profile:<sai profile name>
      replicas: 1
      sai_prefix: <sai prefix>