Uploading a Large File
If a file to be uploaded is greater than the upper limit, you need to manually upload the file to the server.
Procedure
The following uses /opt as an example tool installation directory. Replace it with the actual directory.
- Obtain the file to be uploaded.
- Save the file to be uploaded in a subdirectory of the created user's directory. (Table 1 lists the possible directories.) The following describes how to use the devadmin user to upload an image file.
- Use an SFTP tool (for example WinSCP) to log in to the server OS as the root user.
- Upload the image file to the /opt/DevKit/workspace/devadmin/porting/sysmig/images/ directory.
Table 1 Directories to which files are manually uploaded Feature
Directory
Image
/opt/DevKit/workspace/devadmin/porting/sysmig/images/
Mounted volume
/opt/DevKit/workspace/devadmin/porting/sysmig/volumes/
Container layer
/opt/DevKit/workspace/devadmin/porting/sysmig/containers/
Redis data
/opt/DevKit/workspace/devadmin/porting/sysmig/data/
Source component package (application)
/opt/DevKit/workspace/devadmin/porting/sysmig/src/Application
Source component package (middleware)
/opt/DevKit/workspace/devadmin/porting/sysmig/src/${Component_name}
Target component package
/opt/DevKit/workspace/devadmin/porting/sysmig/target/${Component_name}
Note: Determine the paths to the source and target component packages as prompted.
If a feature directory does not exist, manually create it. For example, upload an image file as devadmin:
1 2 3
mkdir -p /opt/DevKit/workspace/devadmin/porting/sysmig/images/ chown -R devkit:devkit /opt/DevKit/workspace/devadmin/porting/ chmod -R 700 /opt/DevKit/workspace/devadmin/porting/
/opt is the default installation directory. Replace it with the actual one.