Pro Applications: Entering serial number after migrating causes the application to stop responding
After using Migration Assistant in Mac OS X v10.6.x to migrate data and applications, you may be prompted to enter the serial number when opening a migrated application from any of the following products: Aperture 3 Final Cut Studio (2009) Logic Studio (2009) Logic Express 9 After entering the serial number and clicking OK, the application may not respond.
Hi Experts.
i have been stuck up with an issue.
i have connected my Solaris 8 , Sun fire V445 on serial port by using Teraterm.
Initially i was able to login and executed some tasks.
After executing some commands (mainly Control +c), i am not able to type any key or not able to do anything at... (2 Replies)
Hi Experts.
i have been stuck up with an issue.
i have connected my Solaris 8 , Sun fire V445 on serial port by using Teraterm.
Initially i was able to login and executed some tasks.
After executing some commands (mainly Control +c), i am not able to type any key or not able to do anything at... (2 Replies)
Hello!
I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
Hi All,
I am currently facing new problem of migrating C(c language) application from AIX machine to Linux machine. We are using GCC to compile the source code..
But facing with the compilation issues, with lot of GCC C libs differing between AIX box to Linux box...
Pls help me... (3 Replies)
hi everybody, this is my first visit here.
i have a sco unixware 7.1 box. terminals are connected thru digi multiserial devices. some users are also connected over the lan from pc stations running terminal emulation programs.
in few last weeks periodically ( almost every other day ) happens... (2 Replies)
asupgrade(1m) Application Server Utility asupgrade(1m)NAME
asupgrade - migrates the configuration of a previously installed Sun Java System Application Server
SYNOPSIS
asupgrade [-c | --console] [-V--version] [-h | --help]-s | -source applicationserver7.x_installation -t--target application-
server8.x_installation [-d | --domain domain_name -n | --nsspwdfile NSS_password_filepath -j | --jkspwdfile JKS_password_filepath -p |
--capwdfile CA_password_filepath]
Use the asupgrade utility to migrate the server configration and its persisted state, J2EE services, and deployed J2EE applications. The
configuration of an installed Sun Java System Application Server 7 is migrated to the Sun Java System Application Server 8 Application
Server installation. If the domain contains information about a deployed application and the installed application components do not agree
with the configuration information, the configuration is migrated as is without any attempt to reconfigure the incorrect configurations.
asupgrade migrates the configuration and deployed applications of a previous version of the Application Server; however, the runtime bina-
ries of the server are not updated. Database migrations or conversions are beyond the scope of the asupgrade command.
Only those instances that do not use the Sun Java System Web Server specific features will be upgraded seamlessly. Configration files
related to HTTP path, CGI bin, SHTML, and NSAPI plugins will not be upgraded.
The upgrade process can also be initiated automatically at installation time using the Upgrade checkbox in the Application Server install-
er. After completion of the upgrade, use the Application Server 7 Uninstaller to remove the previous version of the Application Server.
Application archives (.ear) and component archives (.jar, .war, .rar) that are deployed in the Application Server 7 environment do not
require any modification to run on Application Server 8. However applications and components deployed in the source server are repackaged
into new J2EE archives in the target server's autodeploy directory and are deployed upon server startup. Applications that do not deploy
successfully, must use Migrationtool (asmigrate) on the application and then manually redeploy the application.
You must specify the source and target directories for the upgrade. If the upgrade includes certificates, you must also provide the pass-
words for the source PKCS12 file and the target JKS keyfile for each domain that contains certificates to be migrated. Since Application
Server 7 uses a different certificate store format (NSS) than Application Server 8 (JSSE), the migration keys and certificates are con-
verted to the new format. Upon successful upgrade, an upgrate report is generated listing successfully migrated items along with a list of
the items that could not be migrated.
OPTIONS -c --console launches the upgrade command line utility.
-V--version displays the version of the UpgradeTool.
-h--help displays the arguments for launching the UpgradeTool.
-s--source identifies the installation directory for Sun Java System Application Server 7.
-t--target identifies the installation directory for Sun Java System Application Server 8.
-d--domain identifies the destination domain name for the migrated certificates.
-n--nsspwdfile identifies the path to the NSS password file.
-j--jkspwdfile identifies the path to the JKS password file.
-p--capwdfile identifies the path to the CA certificate password file.
EXAMPLES
Example 1: Using asupgrade
example% upgrade -s /home/sunas7 -t /home/sunas8
SEE ALSO asmigrate(1M)Sun Java System Application Server March 2004 asupgrade(1m)
