Release 20.0.1.1

AAE/README_migrate.md

@@ -29,6 +29,6 @@ Reuse the existing App Engine database. Update the database configuration inform
 
 ## Step 6: Migrate IBM Business Automation Navigator from 19.0.2 to 20.0.1 to verify your apps
 
-Following the IBM Business Automation Navigator migration instructions(We should add a link to the Navigator migration instructions,once navigator migration link is ready), migrate Business Automation Navigator from 19.0.2 to 20.0.1. Then, test your apps.
+Following the [IBM Business Automation Navigator migration instructions](../BAN/README_migrate.md), migrate Business Automation Navigator from 19.0.2 to 20.0.1. Then, test your apps.
 
 

AAE/configuration/sample_min_value.yaml

@@ -8,7 +8,7 @@ spec:
   application_engine_configuration:
   ## The application_engine_configuration is a list. You can deploy multiple instances of App Engine and assign different configurations for each instance.
   ## For each instance, application_engine_configuration.name and application_engine_configuration.name.hostname must have different values.
-  - name: ae_instance1
+  - name: ae-instance1
     hostname: <your external app engine host name>
     port: 443
     admin_secret_name: ae-secret-credential

ACA/README_upgrade.md

@@ -19,13 +19,12 @@ Upgrade from Content Analyzer 19.0.2 to 20.0.1 is not supported.
 - Back up your Content Analyzer's base database and tenant database.
 - Copy the `DB2` [folder](/~https://github.com/icp4a/cert-kubernetes/tree/master/ACA/configuration-ha) to the Db2 server.
 - Run the `UpgradeTenantDB.sh` from your database server as `db2inst1` user.
-- Set the ObjectType feature flag for the tenant by running this SQL in your Content Analyzer's base database. Replace the values of `<ontology>` and `<tenantID>`.
-```
-set schema <ontology>
-update tenantinfo set FEATUREFLAGS=(4 | (select FEATUREFLAGS from tenantinfo where TENANTID='<tenantId>' and ONTOLOGY='<ontology>')) where TENANTID='<tenantID>' and ONTOLOGY='<ontology>'
-```
-- Change the schema version of tenant to 1.4 by running this SQL in your Content Analyzer's base database. Replace the values of `<ontology>` and `<tenantID>`.
+- Set the ObjectType feature flag and change the schema version flag to 1.4 for the tenant by doing the following for your Content Analyzer's base database. 
+   1. Start the DB2 commandline by running the `db2` command.  
+   2. On the DB2 commandline, connect to your Content Analyzer base database as the base database user.  
+   3. On the DB2 commandline, run the following SQL statements (replace the values of `<ontology>` and `<tenantID>` with the actual values for your instance).
 ```
+update tenantinfo set FEATUREFLAGS=(4 | (select FEATUREFLAGS from tenantinfo where TENANTID='<tenantID>' and ONTOLOGY='<ontology>')) where TENANTID='<tenantID>' and ONTOLOGY='<ontology>'
 update tenantinfo set TENANTDBVERSION=1.4 where TENANTID='<tenantID>' and ONTOLOGY='<ontology>'
 ```
 - Fill out the CR yaml file supplied with 20.0.1 using the same values as the previous deployment. Note that you should use the same number of replicas for mongo/mongo-admin as was in 19.0.3 (e.g. 3).

FNCM/README_config.md

@@ -66,7 +66,7 @@ If you want to exclude any components from your deployment, leave the section fo
 
 All FileNet Content Manager components require that you deploy the Content Platform Engine container. For that reason, you must complete the values for that section in all deployment use cases.
 
-For a more focused YAML file that contains the default value for each FileNet Content Manager parameter, see the [fncm_ban_sample_cr.yaml](/fncm_ban_sample_cr.yaml). You can use this shorter sample resource file to compile all the values you need for your FileNet Content Manager environment, then copy the sections into the [ibm_cp4a_cr_template.yaml](../descriptors/ibm_cp4a_cr_template.yaml) file before you deploy.
+For a more focused YAML file that contains the default value for each FileNet Content Manager parameter, see the [fncm_ban_sample_cr.yaml](configuration/fncm_ban_sample_cr.yaml). You can use this shorter sample resource file to compile all the values you need for your FileNet Content Manager environment, then copy the sections into the [ibm_cp4a_cr_template.yaml](../descriptors/ibm_cp4a_cr_template.yaml) file before you deploy.
 
 A description of the configuration parameters is available in [Configuration reference for operators](https://www.ibm.com/support/knowledgecenter/SSYHZ8_19.0.x/com.ibm.dba.ref/k8s_topics/ref_cm_paramsop.html)
 

IAWS/configuration/sample_min_value.yaml

@@ -6,27 +6,28 @@ spec:
   appVersion: 20.0.1
   iaws_configuration:
     - name: instance1
-      wfs:
+      iaws_server:
         service_type: "Route"
+        workstream_server_secret: ibm-iaws-server-secret
         hostname:
         port: 443
         replicas: 1
         admin_user:
         image:
           repository: cp.icr.io/cp/cp4a/iaws/iaws-server
-          tag: 19.0.3
+          tag: 20.0.1
           pullPolicy: IfNotPresent
         pfs_bpd_database_init_job:
           repository: cp.icr.io/cp/cp4a/iaws/pfs-bpd-database-init-prod
-          tag: 19.0.3
+          tag: 20.0.1
           pullPolicy: IfNotPresent
         upgrade_job:
           repository: cp.icr.io/cp/cp4a/iaws/iaws-server-dbhandling
-          tag: 19.0.3
+          tag: 20.0.1
           pullPolicy: IfNotPresent
         ibm_workplace_job:
           repository:  cp.icr.io/cp/cp4a/iaws/iaws-ibm-workplace
-          tag: 19.0.3
+          tag: 20.0.1
           pull_policy: IfNotPresent
         database:
           ssl: false
@@ -47,7 +48,7 @@ spec:
         content_integration:
           init_job_image:
             repository: cp.icr.io/cp/cp4a/iaws/iaws-ps-content-integration
-            tag: 19.0.3
+            tag: 20.0.1
             pull_policy: IfNotPresent
         appengine:
           hostname:
@@ -59,7 +60,7 @@ spec:
         jms:
           image:
             repository: cp.icr.io/cp/cp4a/iaws/jms
-            tag: 19.0.3
+            tag: 20.0.1
             pull_policy: IfNotPresent
           tls:
             tls_secret_name: dummy-jms-tls-secret
@@ -107,7 +108,7 @@ spec:
       service_type: Route
       image:
         repository: cp.icr.io/cp/cp4a/iaws/pfs-prod
-        tag: 19.0.3
+        tag: 20.0.1
         pull_policy: IfNotPresent
       liveness_probe:
         initial_delay_seconds: 60
@@ -170,7 +171,7 @@ spec:
       dba_resource_registry:
         image:
           repository: cp.icr.io/cp/cp4a/aae/dba-etcd
-          tag: latest
+          tag: 20.0.1
           pull_policy: IfNotPresent
         lease_ttl: 120
         pfs_check_interval: 10
@@ -188,15 +189,15 @@ spec:
     elasticsearch:
       es_image:
         repository: cp.icr.io/cp/cp4a/iaws/pfs-elasticsearch-prod
-        tag: 19.0.3
+        tag: 20.0.1
         pull_policy: IfNotPresent
       pfs_init_image:
         repository: cp.icr.io/cp/cp4a/iaws/pfs-init-prod
-        tag: 19.0.3
+        tag: 20.0.1
         pull_policy: IfNotPresent
       nginx_image:
         repository: cp.icr.io/cp/cp4a/iaws/pfs-nginx-prod
-        tag: 19.0.3
+        tag: 20.0.1
         pull_policy: IfNotPresent
       replicas: 1
       service_type: NodePort