Post installation required fixes
Complete a few additional tasks after you install IBM® InfoSphere® Information Server with optional Information Enterprise Search to make sure that you are ready for your first use of the newly installed software.
Procedure
- For an IBM
InfoSphere Information Server installation
with IBM
WebSphere® Application Server Network Deployment,
configure the domain names so the Launchpad on the Enterprise Search node can correctly redirect to
the InfoSphere Information Server node URLs.
- To set the domain names on the Information Server node, run the following
command:
<Installation Directory>/ASBServer/bin/iisAdmin.sh -set -key com.ibm.iis.isf.security.AllowedRefererDomainNames -value <Domain Name or comma-separated Domain Names>
- To check the domain name setting on the Information Server node, run the following
command:
<Installation Directory>/ASBServer/bin/iisAdmin.sh -display -key com.ibm.iis.isf.security.AllowedRefererDomainNames
- To set the domain names on the Information Server node, run the following
command:
- For an IBM
InfoSphere Information Server installation
with IBM
WebSphere Application Server Liberty Profile,
configure the certificates for Data Flow Designer.
- Run the following command to accept the certificate from the Enterprise Search node on
the Information Server node:
<Installation Directory>/ASBNode/bin/UpdateSignerCerts.sh -url https://<Information Server Enterprise Search node>:443 -user <IS Admin User ID> -password <IS Admin Password>
- Restart the Data Flow Designer service on the Information Server node by running the
following commands:
cd <Installation Directory>/ASBNode/CognitiveDesignerEngine stopCognitiveDesignerServer.sh startCognitiveDesignerServer.sh
- Run the following command to accept the certificate from the Enterprise Search node on
the Information Server node:
- Enable the automatic purge of Elastic Search logs on the Enterprise Search node.
- Expose the Elastic Search port in the Kubernetes service file by running the following
command:
sed -i.bak -e "s/# nodePort: 32555/nodePort: 32555/;s/#type: NodePort/type: NodePort/" /home/mykubeadm1/elasticsearch.yaml
- Apply the changes that were made to the Elastic Search configuration file by running
the following command:
kubectl apply -f /home/mykubeadm1/elasticsearch.yaml
- Validate that the Elastic Search ports are exposed by running the following
command:
kubectl get svc | grep elasticsearch
- Append the following lines to the file /etc/crontab to purge logs
that are older than seven days at midnight on a daily schedule:
0 0 * * * /usr/bin/bash /opt/IBM/UGinstall/esLogPurge.sh >> /var/log/es_purge.log
- Expose the Elastic Search port in the Kubernetes service file by running the following
command: