Install Rapid Fire Library

Previous page  •  Next page

Before you begin:

Notice: Rapid Fire uses commitment control to update its files. Therefore a journal must be attached to all Rapid Fire files. By default the Rapid Fire installer ensures that journaling is started for all Rapid Fire files. But in case that you have installed a high availability software, such as BUS/400, MIMIX or iTERA, that also use journals to keep track of object changes, you may need to install Rapid Fire without a journal, because that is attached by your HA software. Please uncheck "Start journaling Rapid Fire files" on the "Transfer Rapid Fire Library" dialog to transfer the Rapid Fire library without attaching a journal to the Rapid Fire files.

Before you proceed:

Notice: The Rapid Fire plug-in is a client-server application that utilizes SQL stored procedures and functions for retrieving data from the host and for executing actions on the host. All SQL procedures and functions are installed with the specific schema name that equals the name of the Rapid Fire product library. The default name is RAPIDFIRE. The library is shipped with program CRTDRPSQL that can be used for deleting and/or creating the procedures and functions. The procedures and functions are created automatically by the installer, when you use the "Transfer Rapid Fire library" dialog for installing the library. Please consider reading Uninstall Rapid Fire Library before installing it.

Follow these steps to install the Rapid Fire library from the host:

• Start WDSCi 7.0 or RDi 9.5.1.3+.
• Click on "Windows / Preferences".
• Expand item "Rapid Fire".
• Click "Library".
• In "Host name:" enter the name of an IBM i host system that is configured as a Remote System in the Remote System Explorer view.
  Review the "FTP port number" and the name of the "Rapid Fire library". The default FTP port is 21. The default library name is RAPIDFIRE.
  Note: You may use another library name, but be aware that this library will be deleted if it exists.
• Verify the ASP group. The name of the ASP group is used for parameter RSTASPDEV of command RSTLIB when restoring the Rapid Fire library. The possible values are:

  *NONE	-	The DLTLIB and RSTLIB commands are executed without the ASPDEV and RSTASPDEV parameters.
  asp-device-name	-	The DLTLIB command is executed with ASPDEV(*) and the RSTLIB command is extended with RSTASPDEV(asp-device-name).

• Click the [Transfer Rapid Fire library] button.
• Use the refresh button to retrieve the version of the Rapid Fire library. Once pressed, the version is automatically updated as the library name changes. Auto-update is disabled, when the host name is changed.

  

• In the "Sign on" popup, confirm the the name of your host system and enter the user and password to be used to connect to the host.

  

• Click the [OK] button to proceed.

• On the following "Transfer Rapid Fire library" dialog, specify whether to start journaling the Rapid Fire files and then click [Start Transfer] to start the FTP transfer.
  

  

• If the Rapid FIre library already exists, you will be asked to confirm that you want to delete it:

  

• The transfer will start and the steps will be displayed in the window as the transfer runs.
• At the end of the transfer request a [Print job log] button will appear:

  

• Review the contents of the window to check, whether the library has been successfully installed. If you need to report errors, use the context menu to copy all messages to the clipboard and click the [Print job log] button to print a job log on the host. Use the [Close] button to close the dialog.

  Alternatively you can use CTRL-A to select all messages and CTRL-C to copy the selected messages to the clipboard.

You can use the following SQL commands to display the installed Rapid Fire SQL procedures and functions to see what has been installed:

Replace libraryName with the name of your Rapid Fire product library.