Read these instructions completely before you begin.
This document provides specific instructions on how to convert Robot Network using the HelpSystems Product Loader. For general information about the HelpSystems Product Loader, see Using the HelpSystems Product Loader.
|DATABASE||QIBM_QZDA_SQL1 and QIBM_QZDA_SQL2|
Robot Network also uses the DDM and TELNET TCP/IP servers.
|4443||Send/Receive data from the node system|
|4444||Send/Receive data from the host system|
|7473||Send/Receive data on the node system|
|7474||Send/Receive data on the primary host system|
We recommend that the exit points and ports listed above be open to the RBTUSER, RBTADMIN, RBTNETPT, and user profiles logging on to the Robot Network Explorer.
If you're running Robot Network 9, you must convert to Robot Network 10 before converting to Robot Network 12. Robot Network 12 doesn't support any Robot Network 9 nodes.
Due to the dependencies between Robot Products, Robot Network, Robot Console, Robot Schedule and Robot Schedule Enterprise must all be converted at the same time. Allow enough time to complete updates to all products.
Robot Network doesn't support mirroring. Do not mirror the RBTNETLIB library, the RBTNETNODE library, the RBTNETPT user profile, or the Robot Network IFS directory (Help Systems/Robot Network).
You cannot convert to Robot Network 12 while your system is in restricted state.
You must convert the Robot Network 10 or 11 host to Robot Network 12 before you convert any of its nodes.
You don't have to convert your Robot Network 10 or 11 nodes at the same time that you convert your Robot Network 10 or 11 host.
Note: You must convert the host and the alternate host before you convert any of the remote nodes.
Make sure that no one is using Robot Network.
The MIB for Robot Network 10 and 11 did not change for version 12.
Back up your current RBTNETLIB, RBTNETNODE, and RBTSYSLIB libraries, as well as the Help Systems IFS directory on all systems—the conversion process updates these libraries.
If the current system is part of a Robot Save data center, you must end the Robot Save monitors on all of the systems that are part of the data center before you start the conversion.
To run Robot Network 12 with any of the following Robot products, you need the indicated release/modification levels (or higher) for these products:
|Product||Minimum Release/Modification Level|
To display the release and modification levels of these products, type RBTSYSLIB/RSLVER and press Enter.
Note: If you have the following products on the system they need to be converted at the same time in the following order:Robot Network
The Robot Network 12 user profile, RBTNETPT, which is reset during the conversion, uses the group profile RBTUSER to communicate between systems in the network.
The Robot Network conversion process creates or changes two user profiles, RBTUSER and RBTADMIN. These profiles were created for the following reasons:
They satisfy requests from corporate auditors that our objects be owned differently from IBM objects.
They allow us to build a secure product for your environment.
They isolate The Robot products from IBM changes to the QPGMR or QSECOFR profile defaults.
Note: If you've made any manual changes to the RBTUSER or RBTADMIN user profiles or their authorities, these changes will be lost with any product installation or conversion.
Before loading Robot Network, we check if RBTSYSLIB needs to be updated. If it does, you’ll be asked to bring down the subsystem RBTSLEEPER. This ends all Robot products running on your system. When the update completes, the subsystem will restart automatically.
When you’re finished, read the After You Are Done section for additional information.
Robot NETWORK 12 uses TCP host servers and Java to communicate between a host and a node. You may have to change your initial startup program to allow more time for these services to start before starting the RBTSLEEPER subsystem. For example, you might need to delay the job several minutes (DLYJOB) between the time the TCP host servers start and the time the RBTSLEEPER subsystem is started.
To use Robot Network 12, you must have the following software installed on your IBM i server:
|OS Level||Required Software|
QSHELL - product option 30
Portable App Solutions Environment, product option 33
Java SE 8 32-bit 5770JV1, option 16 or
Java SE 8 64-bit 5770JV1, option 17 or
Java SE 7 32-bit 5770JV1, option 14 (recommended) or
Java SE 7 64-bit 5770JV1, option 15
Java SE 8 32-bit 5770JV1, option 16 or
Java SE 8 64-bit 5770JV1, option 17 or
Java SE 7 32-bit 5770JV1, option 14 or
Java SE 7 64-bit 5770JV1, option 15 or
* Robot Network 12 is supported for IBM i V7R2 and higher.
Robot Network 10 and higher requires the following minimum requirements:
|Host or Node||Minimum Hardware Requirements|
|Robot Network host||CPU: ¼ processor *
Memory: 400MB in memory pool for Robot Network **
|Robot Network node||CPU: ¼ processor *
Memory: 200MB in memory pool for Robot Network
* The CPU on the NETHOST3 and NETNODE2 jobs can vary depending on the activity.
** The host will need more memory as you add more nodes and functions of Robot Network.
Note: The minimum requirements are relative to the size of the system, other processes that are running, the number of nodes in your network, and the features and functions used within Robot Network. This information is given as a baseline.
For successful network communications, Robot Network 12 requires a fully qualified TCP/IP host name in the format of system_name.domain_name to be in the local directory and/or the DNS server. You can use the command CFGTCP and options 10 and 12 to set up host names. For more information, contact your system administrator or Technical Support.
Before you convert Robot Network, you can run a pre-installation utility to determine whether the process will complete successfully. Download the setupNetwork12PreChecker.exe file and use the Product Maintenance Wizard. For more details, see “Robot Network Pre-Checker.”
If you don’t want to download a separate .exe file, you can also do the following:
Use the Converting Robot Network instructions to download everything to your PC.
When you reach the Product Load Options panel, select Staged Load (step 5b below) and wait until the processing completes.
On the IBM i, execute the following command to display the Work with Loads panel:
Enter option 2, Run pre-checker, next to the Load Name for Robot Network and press Enter.
Review the information on the Check Install Network 11 panel. Select *UPGRADE for the installation and indicate whether this will be your host system, then press Enter.
Note: A pre-checker automatically runs during the first part of the Robot Network conversion process, but we recommend you run it in advance to identify any potential problems before attempting a full conversion.
Use these instructions to convert Robot Network. This process downloads everything to your PC and loads the objects on the IBM i. Read the following steps carefully to proceed.
Download the Robot Network installer (setupNetwork12.exe) from My Account on our website. Double-click it to start it.
On the Choose Components panel, select which components you want to load. You can choose the Software for Windows (the GUI and the Manuals) and the Software for IBM i. Click Next.
If you’re only installing the Software for Windows, the process completes and the installer closes. The Software for Windows has been installed. You can skip the rest of these steps.
Note: The manuals were installed at the following location.
C:\Program Files (x86)\Help Systems\Robot NETWORK 12\manuals
If you’re loading the Software for IBM i (with or without the Software for Windows), continue to step 4.
On the Choose a Destination IBM i panel:
Select or enter the IBM i where you want to load Robot Network.
Enter a user profile and password that’s a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ, *SECADM, *JOBCTL, and *IOSYSCFG. The user profile should have Limit capabilities set to *NO. This profile will be used to restore and copy objects, and for product maintenance on the IBM i.
(Optional) In the Advanced Settings section:
Enter a port number or use the arrows if you want to change the FTP port number to something other than the default of 21.
Select Secure File Transfer if you want to use FTPS (FTP over SSL) during the file transfer. The default FTPS secure port is 990, but it can be changed to the required secure port for your environment.
In the Timeout (seconds) field, enter the number of seconds the session should be kept active during an FTP transfer. You can choose anywhere between 25 and 1800 seconds (30 minutes).
Note: If the transfer takes longer than the amount of time specified, the session will expire.
You have two options on the Product Load Options panel:
Click Immediate Load if you’d like to load the product on the IBM i now.
Note: This ends Robot Network until the product load completes. After you are done, we’ll restart the product.
Note: See “Loading Staged Objects on the IBM i” below for instructions on how to load the staged objects on your selected IBM i system.
The Product Load Progress panel for Robot Network launches. When the processing is complete, you have two choices:
If this is the only conversion of Robot Network that you're doing, click Finish.
If you have conversions to do on other IBM i systems, click Restart. Then, return to step 4.
Note: If the Product Load Progress panel ends with an overall Failed message, the product upload could not complete properly. To find the reason the upload failed, click View Logs and review your logs. You can also use Download at the top of the logs to save the information for future review.
If you chose to stage your objects during step 5b of the conversion process, do the following to manually load them on the IBM i you identified above.
Execute the following command to make sure no users are signed on to the product you’re converting:
WRKOBJLCK OBJ(RBTNETLIB) OBJTYPE(*LIB)
Remove the RBTNETLIB and RBTNETNODE libraries from all library lists. The conversion program must be able to rename these libraries. To ensure there are no locks, enter the following commands:
WRKOBJLCK RBTNETLIB *LIB
WRKOBJLCK RBTNETNODE *LIB
Execute the following command to display the Work with Loads panel:
Enter option 1, Load, next to the Load Name for Robot Network and press Enter. Select Robot Network Host if it is the Host system (it will install Host and Node). Select Robot Network Node if it is a Node system.
After the conversion completes, execute the WRKSPLF command to check the spooled files for any errors that may have occurred. If you have any questions, contact Technical Support.
The conversion process creates two libraries, RBTHOSTV10 and RBTNODEV10 and creates backup directories in the Help Systems directory. After you’re satisfied that the conversion was a success, you can delete these libraries and IFS directory. You can delete the version 10 directories /Help Systems/Robot NETWORK.V10 and /Help Systems/installs/NET.V10.
If you didn't install the manuals on your PC in the above procedure, you can access the Robot Network User Guide and other documentation from our website.
Three libraries were restored to your system for use during the conversion process: HSLOADMGR, HSLOADMGRW, and RBTCDRLIB. We don't remove them from your system in case you're doing multiple conversions. You can delete them when you're finished.
Note: You can move the library HSLOADMGR to a different system on the IBM i and use it to complete additional conversions. For more information, see “Using the HelpSystems Product Loader.”
Still have questions? We can help. Submit a case to Technical Support.