In this article, I'll be explaining in detail about the series of steps needs to be followed while configuring streaming server to FQDN in a dual nic environment, network pre-requisite to be adhered and files that can be validated after configuring the system. If you’re installing server in a dual nic card machine, installer identifies it automatically and displays only the ipaddress. You need to manually change the server components (FE/STE) name to machine name or FQDN by logging into console. Before doing that, you might need to validate list of things on your network and your server machine as given in network perquisite section before trying to change it.
In a dual nic machine, one network card will be configured with DNS QADNS.ParentServer.net and second network card will be configured with DNS Devdns.ChildServer.net. Out of this 2 network, machine will be added to one domain in this e.g., I took qadns.ParentServer.net. In order to configure the SWS FE/STE component VIA FQDN validate that
- Able to ping the Backend machine by host name and FQDN from the FE machine
- Able to ping the FE machine by host name and FQDN from the Backend machine
- Network binding order of all the machines should be same and whichever FQDN we are using, that nic should be in top of the binding order list. This ip-address should be the one we choose during the server installation.
- In the DNS Server, this ip-address should have a valid pointer with corresponding machine name in Forward lookup zone and Reverse lookup zone.
- From Backend machine nslookup < hostname> and nslookup <FQDN> of both BackEnd and FE machine should resolve to fully functional FQDN
- From Front-end machine nslookup <hostname> and nslookup <FQDN> of both FE and BE machine should resolve to fully functional FQDN
- From the Front-end machine nslookup <hostname> and nslookup <FQDN> of all the other FE (we planned to add to that STE) should resolve to fully functional FQDN
If the above mentioned points were validated and everything works as mentioned then configuring the FE and STE with hostname or FQDN will work fine
Steps to Configure Server with FQDN:-
After validating your network setup, before changing the components to FQDN make sure all the components were in “Green” colour. In the launch Server and streaming server basic configuration page, hostname/ipaddress filed should have ip-address you choose while install.
In the streamlet engine basic configuration page, if the hostname/ipaddress text box shows “All local Ips” check the as_component table for STE host_name and bind_address. It should have the proper ip-address and not 0.0.0.0. First change the entire Front component to FQDN and finally change the STE to FQDN.
Configuring Front End server to FQDN:-
To Configure Front-end server hostname to FQDN, you can change either the streaming server hostname or the LaunchServer host name. Since Launch server and Streaming server was grouped as Front-end component, changing hostname/bind address of one component will automatically change the other component.
To change Streaming Server hostname to FQDN, launch streaming console and navigate to Configuration | Streaming Server | Streaming Server Configuration page and click the Basic button. In the Streaming Server basic configuration page change the hostname and Bind address field to FQDN and save the changes. Saving the changes will prompt for restart of FE service, press OK button and restart the FrontEnd components from console. Follow the same process for all the FE's added in the System.
Files to be validated after configuring FE to FQDN:-
In the Front-end machine open following files and check hostname was updated properly to FQDN
<installFolder>\ server\bin\ AppstreamServerCfg.txt
<Connector port="80" address="Lilliac-vmr2.streethawk.com" server="appstream" maxThreads="300" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" useURIValidationHack="false" disableUploadTimeout="true" allowTrace="false" URIEncoding="UTF-8" astype="C and M Manipulated" />
You can also validate the same in the BackEnd machine by opening the below file.
Configuring Back End server to FQDN:-
To change the Streamlet Engine hostname to FQDN in the Streaming console goto Configuration | StreamletEngine | Streamlet Engine Basic configuration page and click Basic button. Edit the hostname or ip address filed with STE machine FQDN and save the changes. This will prompt a message box to restart the STE and press OK to that. This will automatically restart the STE service and once it's turn Green STE will communicating with all the components in FQDN.
Files to be validated after changing STE name to FQDN:-
In the BackEnd machine open the below files and check the following entries were updated properly with FQDN
- <InstallFolder>\Console\Conf\ConsoleConfig.xml file
# DCI config parameters:
service.name=AWE Streamlet Engine
<Connectorport="9832"address="x64gan-08.streethawk.com"maxThreads="250"maxHttpHeaderSize="8192"emptySessionPath="true"protocol="HTTP/1.1"enableLookups="false"redirectPort="8443"acceptCount="100"allowTrace="false"connectionTimeout="20000"disableUploadTimeout="true"astype="C and M Manipulated" />
5. <InstallFolder>\common\jboss-4.2.2\server\appstream\deploy\jms\jbossmq-httpil.sar\ META-INF\jboss-service.xml
<attribute name="URL">http://x64gan-08.streethawk.com:9832/jbossmq- httpil/HTTPServerILServlet</attribute>
After validating all the files in the backend we need to validate the STE host name in all the FrontEnd servers. Only if STE name was updated with FQDN in all the FE’s attached to that STE, communication will be proper between the components and FE will show up in green colour. To validate it go to console and look at below places.
Navigate to Configuration | StreamingServer | Streaming Server Basic Configuration page and check the HostName or Ip address value under Streamlet Engine Access section. This should have the STE name in FQDN format.
Streamlet Engine Access
Host Name or IP Address:
Under Data Access URL section, Primary Value should also have the STE in FQDN
Data Access URL
To validate the launch server settings in console goto Configuration | Launch Server | LaunchServer Basic configuration settings and check the Primary data access url value under Data Access URL. This should have the STE name in FQDN format.
Data Access URL
Configuring Stand Alone to FQDN:-
To configure the Standalone DA, launch streaming console and navigate to Configuration | Data Access Configuration page and click basic button. In the Standalone Data Access Basic Parameters page change the Hostname or Ip address and Bind address field with FQDN, save the data and restart the data from component status page. Wait till the status of DA service shows green colour in component status screen after restart.
Files to be validated after changing HostName to FQDN:-
In the Data Access machine open the below files and check the following entries were updated properly with FQDN
# DCI config parameters:
We also need to validate the DA host name was updated properly in all the Front End machines. To do so, launch streaming console and navigate to Configuration | StreamingServer | Streaming Server Basic Configuration page and check the data access url values in the secondary section. This should have the Stand Alone DA name in FQDN format.
Data Access URL
To validate the Stand Alone Data value for Launch server, navigate to Configuration |Launch Server | Launch Server Configuration and click basic button. In the Launch Server Basic parameter page, under data access url section, secondaries: should have the data access component url in FQDN
While validating the DA component host name, need to validate it in the entire Launch server/Streaming Server basic parameter page for the entire stand alone DA component. Secondary Data Access URL for all the FE’s should have the DA name in FQDN format.