After you install microservices for the first time or you've created a new cluster to be used with the existing application server and database combination, you must configure the installed microservices.
Before you begin
Microservices infrastructure has been created.
Procedure
-
Set the following configuration settings:
AppInstanceID - The Services App Instance ID that will be used by all services within the Service Registry.
KafkaServer - The Hostname(s) and Listener Port for that all services will use to register with Kafka.
ServicesProxy - The URl for Services Proxy.
SolrContentServer - The Solr Content Server URL that will be used by all SolrServices.
SolrStatementsServer - The Solr Statement Server URL that will be used by all SolrServices.
ZookeeperServer - The Hostname(s) and Listener Port that all services will use to register with Zookeeper. -
Use the sample script below to update these values for use with the SQL server.
Sample script
You can update these values using the AcceleratorKMS user interface (UI), however, adding them in the UI can lead to inadvertently adding trailing spaces and causing issues with the application not being able to access SOLR and other microservices..
The following example script would be if using AWS and followed the instructions included. If you're using another method, the values will be similar, however, you must search the newly created microservices cluster to access the value for each microservice.
Basic installation method:
update configuration set value = '/Akms/customerName' where [key] = 'AppInstanceId';
update configuration set value = 'customerNamekafka1.customerName-microservices.local:29092'
where [key] = 'KafkaServer';
update configuration set value = 'http://internal-customerName-ReverseProxy-xxxxxx.us-east-1.elb.amazonaws.com/Services/'
where [key] = 'ServicesProxy';
update configuration set value = 'http://customerName-LoadB-xxxx.elb.us-east-1.amazonaws.com:8983/solr/Akms_Content'
where [key] = 'SolrContentServer';
update configuration set value = 'http://customerName-LoadB-xxxx-.elb.us-east-1.amazonaws.com:8983/solr/Akms_Statements'
where [key] = 'SolrStatementsServer';
update configuration set value = 'customerNamezoo1.customerName-microservices.local:2181' where [key] = 'ZookeeperServer';
High availability method:
You should change the ZookeeperServer and KafkaServer values to reflect the high availability approach. Each instance or host is separated by a comma. Here's an example:
update configuration set value = 'customerNamekafka1.customerName-microservices.local:29092,customerNamekafka2.customerName-microservices.local:29092,customerNamekafka3.customerName-microservices.local:29092'
where [key] = 'KafkaServer';
update configuration set value = 'customerNamezoo1.customerName-microservices.local:2181,customerNamezoo2.customerName-microservices.local:2181,customerNamezoo3.customerName-microservices.local:2181' where [key] = 'ZookeeperServer';
If you need to change any of the above values, you must restart each microservice so that they use the new setting. You must also restart IIS for each application server.