Sponsored Content
Operating Systems HP-UX Migrating from HP UX to LINUX/SOLARIS- which one is more preferable? Post 302522363 by methyl on Saturday 14th of May 2011 09:10:13 PM
Old 05-14-2011
Assuming decent scale I'd modernise the hardware and software and continue with HP-UX. Porting a large-scale application written in a low-level language to another platform is very high risk.
If this is a trivial application, the platform is largely immaterial providing that you have good programmers.
Whatever the decision, trial the application on sample new platforms and test throughly before making the change.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Migrating from HP to Solaris

My company is considering migrating from HP unix to Solaris just to get two more years of support for a particular software product. My question is just how much of an effort is it to do this migration? Are you aware of any migration tools to assist us in this migration? Thanks (1 Reply)
Discussion started by: jkuchar747
1 Replies

2. UNIX for Advanced & Expert Users

Migrating Solaris 9 to different hardware

Hi, I am new to this forum and hope someone can help. Does anyone know how to restore a Solaris 9 backup tape from server A to a completely different server B hardware. Both boxes are sun 64bit. Your help is much appreciated. Thank you Jan. (5 Replies)
Discussion started by: snerta
5 Replies

3. Linux

Migrating from SENDMAIL on SUN SOLARIS to POSTFIX on Linux

Migrating from sendmail on SUN Solaris to POSTFIX on Linux. I have been asked to migrate our sendmail to postfix on Linux and would appreciate and information. Hints and tips on the process involved. Perhaps any links to useful site or documentation that you may know about. Many Thanks (2 Replies)
Discussion started by: Andrek
2 Replies

4. Ubuntu

Migrating from Unix to Linux

Is there a way to migrate username password from Freebsd 6.1 to Linux Ubuntu 8.04. I am using the server as a email server running postfix and using imap. Is there a way to transfer the usernames and password. I have transferred all the Maildirs but I am getting uid errors and gid errors even after... (2 Replies)
Discussion started by: rbizzell
2 Replies

5. Linux

Migrating RCS from HP-UX to Linux

Hello all, We would be migrating from HP-UX 11 to Red Hat Linux 5 shortly. On HP-UX we've been using RCS (Revision Control system). On RHEL I think there is an equivilant utility called Subversion..Is there a way to export the current contents from RCS in HP-UX and import it into Linux's... (2 Replies)
Discussion started by: luft
2 Replies

6. Shell Programming and Scripting

Migrating Oracle on Solaris Sparc to Linux RHEL 7 VM

Hi Gurus, We are migrating Oracle from Solaris to RHEL 7 and looking for Solaris equivalent commands for Linux. we are using lot of korn shell scripts built on Solaris so, i am looking for equivalent commands which are using in Solaris.. Could you please help me here by proving any info... (1 Reply)
Discussion started by: mssprince
1 Replies

7. Red Hat

Migrating Oracle on Solaris Sparc to Linux RHEL 7 VM

Hi Gurus, We are migrating Oracle from Solaris to RHEL 7 and looking for Solaris equivalent commands for Linux. we are using lot of korn shell scripts built on Solaris so, i am looking for equivalent commands which are using in Solaris.. Could you please help me here by proving any info ... (4 Replies)
Discussion started by: mssprince
4 Replies
appmgr(8)																 appmgr(8)

NAME
appmgr - Tool to manage applications and platforms SYNOPSIS
appmgr list [--no-versions] appmgr add NAME DESC [--hr=no | --hr=fine | --hr=coarse] [--beta] [--weight=NUM] [--target_nresults=NUM] appmgr delete NAME [--version=VER] [--platform=NAME] [--plan_class=NAME] appmgr update NAME [--hr=no | --hr=fine | --hr=coarse] [--beta | --no-beta] [--weight=NUM] [--target_nresults=NUM] [--user_friendly_name=DESC] [--min_version=VER] [--deprecated | --no-deprecated] appmgr update_appver NAME [--version=VER] [--platform=NAME] [--plan_class=NAME] [--deprecated | --no-deprecated] [--min_core_version=VER] [--max_core_version=VER] appmgr list_platform [--short] appmgr add_platform NAME DESC appmgr delete_platform NAME [--force] appmgr update_platform NAME [--user_friendly_name=DESC] [--deprecated | --no-deprecated] appmgr add_standard_platforms appmgr {-h | --help} DESCRIPTION
appmgr is a tool to manage platforms, applications and application versions from the command-line. Note: application refers to data in the app table; application version refers to data in the app_version table and in the file system. COMMANDS
The generic syntax is: appmgr COMMAND [command arguments] Note that command-specific options must came after the command, never before. Here is a short list of the available commands. The follow- ing sections describe the commands in detail. list List the installed applications and application versions. add Add a new application. delete Delete an application or application version. update Update the properties of an application. update_appver Update the properties of an application version. list_platform List the platforms known to the project. add_platform Add a new platform. delete_platform Delete a platform. update_platform Update the properties of a platform. add_standard_platforms Add all standard platforms to the project. LIST List the installed applications and application versions, together with any non-default properties (beta, deprecated, min. core version etc.). If the --no-versions option is specified, then the list of application versions is omitted and just the application definitions are listed. ADD Add a new application. NAME is the short name of the application as used in the file system. DESC is the user-friendly name that is dis- played to users. The following options can also be specified: --hr=no, --hr=fine, --hr=coarse Set the homogeneous redundancy class. no means all hosts are equivalent, fine means fine-grained classification of 80 classes, coarse means coarse classification of 4 classes. --beta Indicate that this is application is in beta testing. Users can select if they are willing to test applications marked as beta in their preferences; see the wiki section "Beta-test applications" about how to enable this on the web interface. --weight=NUM Specify the weight of this application if the feeder is run with the -allapps option. NUM is a floating-point value, the default is 1. --target_nresults=NUM Set the number of replicas when an otherwise unreplicated work unit is sent to a host that is not trusted. See the wiki section "Adaptive replication" for details. DELETE Delete applications or application versions. This command deletes both the database records and the files under the download and apps di- rectories, so use with care. The following options can be specified: --version=VER Select only application versions with the version number VER. The version number must be specified as major.minor. --platform=NAME Select only application versions for the platform NAME. --plan_class=NAME Select only application versions having the plan class NAME. If more than one of the options --version, --platform and --plan_class are specified, then only application versions matching all the cri- teria are deleted. If none of these options are specified, then the application is also deleted. Note that if one or more of these options are specified then the application is not deleted even if there are no more application versions remaining. UPDATE Update the properties of an application. The following properties can be modified: --hr=no, --hr=fine, --hr=coarse Set the homogeneous redundancy class. no means all hosts are equivalent, fine means fine-grained classification of 80 classes, coarse means coarse classification of 4 classes. Warning Do not change the homogeneous redundancy class while there are jobs in progress! --beta Indicate that this is application is in beta testing. Users can select if they are willing to test applications marked as beta in their preferences; see the wiki about how to enable this on the web interface. --no-beta Indicate that the application is no more in beta testing. --weight=NUM Specify the weight of this application if the feeder is run with the -allapps option. NUM is a floating-point value, the default is 1. --target_nresults=NUM Set the number of replicas when an otherwise unreplicated work unit is sent to a host that is not trusted. See the wiki article on "Adaptive replication" for details. --user_friendly_name=DESC Update the user-friendly description of the application. --min_version=VER Set the min. version of the application that the scheduler accepts. This is checked only if the client uses the anonymous platform. The version number must be specified as major.minor. --deprecated Indicate that the application is deprecated. The feeder will then ignore this application when looking for new work. --no-deprecated Remove the deprecation mark from the application. UPDATE_APPVER Update the properties of an application version. The version(s) to operate on can be specified with the --version, --platform and --plan_class options, as described at the DELETE command. The following properties can be modified: --min_core_version=VER Set the min. version of the core client that is required to run this application version. The version number must be specified as major.minor. The 3rd component (the patch level) of the core client version is ignored. --max_core_version=VER Set the max. version of the core client that is allowed to run this application. Note that the scheduler ignores this setting cur- rently. --deprecated Indicate that the application version is deprecated. The feeder will then ignore this version when looking for new work. --no-deprecated Remove the deprecation mark from the application version. LIST_PLATFORM List the platforms known to the project. If the --short option is specified, then only the short names of the platforms are listed. ADD_PLATFORM Add a new platform. NAME is the short name of the platform that is used in the scheduler requests. DESC is the user-friendly name that is displayed to users. DELETE_PLATFORM Delete a platform. If the --force option is specified, the command deletes all application versions for this platform. Otherwise, if there are such application versions, the command will fail. UPDATE_PLATFORM Update the properties of a platform. The following properties can be modified: --user_friendly_name=DESC Update the user-friendly description of the platform. --deprecated Indicate that the platform is deprecated. The feeder will then ignore this platform when looking for new work. --no-deprecated Remove the deprecation mark from the platform. ADD_STANDARD_PLATFORMS Add all the standard platform definitions to the database that do not exist yet. August 27, 2009 appmgr(8)
All times are GMT -4. The time now is 09:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy