You may contact Bottomline directly for Formscape support using one of the following methods:
Please have your company name and license number available. The license number can be obtained from your Formscape server’s web administration page (http://formscapeserver:24500).
While there is no direct equivalent of AIX’s mksysb utility to create bootable recovery media built into Red Hat Enterprise Linux, there are a number of commercial and open-source packages available that will be able to create system image backups.
In the event of a catastrophic system failure, our standard procedure is to perform a clean installation of the OS, install all updates, restore OS configuration files, and restore the database. While typically not as fast as an image-based restore, this process can be completed in a relatively short time (typically 2-4 hours), works on all any hardware, and ensures that your system is brought up to the latest build specifications.
References:
To change the default VNC password for the root user:
vncpasswd
No. Eclipse supports a single instance of Eclipse per server. By server, we’re referring to a single operating system instance, be it running on a virtual or physical server.
Yes, it’s technically possible to run multiple accounts on a single server, but doing so puts your server in an unsupported configuration. Exceptions are typically made only for non-production servers.
Eclipse is an intricate stack of software components designed to run best when operating in a dedicated environment. To run multiple Eclipse accounts on a single server, a number of workarounds or “hacks” that must be implemented (for example: updating VOC entries for non-standard database directory locations, non-standard fax feedback pipes, non-standard JBoss networking configurations, non-standard background users, etc.). These non-standard settings changes add unnecessary complexity and expose the system to configuration errors. More importantly, by running multiple accounts within the same OS instance, Eclipse accounts must share many system resources and software (for example: operating system, UniVerse database, VSIFAX, samba, networking, etc.), which means that any changes made to the shared resources will affect the other accounts. This can be especially problematic when a server hosts both production and non-production accounts alongside each other. For example, a new release of UniVerse cannot be certified against a development account with simultaneously affecting the production account running on the same server.
In the past, we have made exceptions to allow unsupported, non-production accounts to operate alongside production instances. This decision was largely based on the high cost with acquiring an additional IBM pSeries server or implementing IBM virtualization. Since the launch of support for the Red Hat Enterprise Linux platform, cost is no longer a barrier to adoption. We will continue to support our customers with existing multi-account configurations on the AIX and RHEL platforms, but we strongly advise customers seeking to create a new account or migrate to the RHEL platform to separate accounts on individual servers.
Operating non-production accounts on their own separate physical or virtual servers has many advantages, including an improved testing environment, removal of potential resource conflicts, and the ability for customers to “refresh” their own non-production accounts as necessary.
Below is an example of using ftp.
You can use graphical tools to help you transfer files such as:
If you are not using a graphical tool, you can use ftp from the command line.
Steps to FTP from the command line:
1. Get to the command line. From Eclipse, you may be able to shell out (F2/T, then type “sh”). (In Windows it is Start, Run, type in cmd, press enter)
2. Navigate to the desired directory. (The “cd” command will change directories)
3. Type in “ftp <ip.address>” (where ip.address is the IP address of the server that you want to transfer files to/from. (Example: ftp 192.168.1.150) You can also use the command “ftp <servername>” where servername is the name of the server that you want to transfer files to/from.
4. You will be prompted for a username and password. Enter the appropriate credentials. If you don’t have them, see your system administrator.
5. Unless you are transferring a plain text file, type “bin” <enter> for binary mode.
6. Navigate to the desired directory using the “cd” command.
7. The command “put <filename>” can be used to send a file from your local machine to the remote one. (Example: put test.pdf)
8. The command “get <filename>” can be used to get a file from the remote machine to your local machine. (Example: get test.pdf)
9. When you are done, type “quit” and press enter.