Installing BMC Impact Integration Web Services server

The BMC Impact Integration Web Services server installation program installs a stand-alone Tomcat server and Axis2 components.

Preparing to install BMC Impact Integration Web Services server

Starting and stopping the BMC Impact Integration Web Services server Open link

To install the BMC Impact Integration Web Services server

Use one of the following methods to access the installation program:
- DVD — Insert the installation DVD.
- BMC Software EPD website (https://webepd.bmc.com/epd) — For more information about downloading the Infrastructure Management software, see Downloading the Infrastructure Management installation files. Extract the contents of the zipped distribution file to an appropriate directory.
Launch the installation wizard:
- Windows
  In the <installLocation>\Windows\Impact_Web_Service directory, double-click setup_IIWS.exe.
- Linux
  In the <installLocation>/Linux/Impact_Web_Service directory, run setup_IIWS.bin.
- Solaris
  In the <installLocation>/Solaris/Impact_Web_Service directory, run setup_IIWS.bin.
On the Welcome page, click Next.
On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and click Next.
If you do not agree to the terms of the license agreement, the installation process will not continue.
The Directory Selection window is displayed.
Perform one of the following actions, then click Next to continue:
- Accept the default directory in the Destination Directory box.
  Note
  
  If you are installing BMC Impact Integration Web Services on the same computer in which the BMC TrueSight Infrastructure Management Server is installed, do not choose the directory in which Infrastructure Management is installed as the destination directory. Install BMC Impact Integration Web Services in a separate directory.
- Click Browse to search for another directory path on the file system.
- Enter a custom directory path in the Destination Directory box.
On the HTTP/HTTPS port selection window, accept the default port number values or specify your own, and click Next.
Review the installation details.
- To change any details, click Previous to view previous screens and change the relevant details.
- If the details are correct, click Install.
On the Installation Summary page, you can click View Log to view the installation logs or click Done to exit the installation wizard.

BMC Impact Integration Web Services server installation directory contents

The installation installs a stand-alone Tomcat server and Axis2 components.

The BMC Impact Integration Web Services components are installed under $IIWS_HOME/Tomcat/webapps/imws/WEB-INF/.

The following table describes the directory contents of the BMC Impact Integration Web Services installation package.

Directory contents

Directory	File	Description
**$IIWS_HOME/Tomcat/webapps/ imws/WEB-INF/services**	ImpactManager.aar	The Axis archive file for the BMC Impact Integration Web Services server includes the jar files and class files; the wsdl and xsd files; and the web service configuration file.
**$IIWS_HOME/Tomcat/webapps/ imws/WEB-INF/etc**	mcell.dir ImWebServices. conf iiws.selector	The mcell.dir file Defines the BMC Impact Manager cells with which the BMC Impact Integration Web Services component communicates Defines the IIWSGatewayServer server entry that opens a gateway server to accept events that propagate from BMC Impact Manager cells The ImWebServices.conf configuration file for BMC Impact Integration Web Services configuration parameters The iiws.selector file defines the selectors that receive events from the BMC Impact Manager cells
**$IIWS_HOME/Tomcat/webapps/imws/WEB-INF/classes**	log4j.properties	Defines the logging properties for BMC Impact Integration Web Services. The BMC Impact Integration Web Services trace log is created under the $IIWS_HOME/Tomcat/logs/iiws.log directory, by default.
**$IIWS_HOME/Tomcat/webapps/imws/WEB-INF/security**	iiwsssl.jks iiwscacerts.jks iiwsssl.cer	The keystore files for running HTTPS for BMC Impact Integration Web Services server.
**$IIWS_HOME/Tomcat/webapps/imws/client_samples**		Provides the sample code for developing the BMC Impact Integration Web Services client.
**$IIWS_HOME/Tomcat/webapps/ imws/WEB-INF/log**		A directory that is created when you run BMC Impact Integration Web Services that contains the persistent files for BMC Impact Integration Web Services.

To verify the installation

After installing and starting the server, you can verify that the BMC Impact Integration Web Services server wsdl file is installed through the following example URLs (where host name represents the name of the host where BMC Impact Integration Web Services is installed, and port is the port number assigned to BMC Impact Integration Web Services):

http://hostname:port/imws/services/ImpactManager?wsdl

The default port is 9080.

https://hostname:port/imws/services/ImpactManager?wsdl

The default port is 9443.

To troubleshoot installation issues

To troubleshoot installation issues, you can view the installation logs.

Windows log files are located at: \Temp\iiws_install_log.txt.
UNIX log files are located at: $TMPDIR/iiws_install_log.txt or $IATMPDIR/iiws_install_log.txt.
On UNIX systems, if more than one Java Virtual Machine (JVM) is installed on the computer, you must uninstall BMC Impact Integration Web Services by running the ./setup_IIWS.bin LAX_VM "<java_path>" command, where <java_path> is the location in which Java is installed.

To troubleshoot the connection handle issue

If the IIWS logs display an error "Invalid connection handle <handle number>. This occurs because the IIWS client uses the cached connections. To troubleshoot this issue, do the following:

Open a new connection in IIWS.
Use the valid connectHandle value returned from the Connect operation.

Where to go from here

Register BMC Impact Integration Web Services with the BMC Atrium Core UDDI Registry server.