(Android™) S3 Complete a Multipart Upload

This operation completes a multipart upload by assembling previously uploaded parts.

Processing of a Complete Multipart Upload request could take several minutes to complete. After Amazon S3 begins processing the request, it sends an HTTP response header that specifies a 200 OK response. While processing is in progress, Amazon S3 periodically sends whitespace characters to keep the connection from timing out. Because a request could fail after the initial 200 OK response has been sent, it is important that you check the response body to determine whether the request succeeded.

This example sends a POST request to complete a multipart upload, which looks like this:

POST /ObjectName?uploadId=UploadId HTTP/1.1
Host: BucketName.s3.amazonaws.com
Date: Date
Content-Length: Size
Authorization: authorization string

<CompleteMultipartUpload>
  <Part>
    <PartNumber>PartNumber</PartNumber>
    <ETag>ETag</ETag>
  </Part>
  ...
</CompleteMultipartUpload>

Chilkat Android™ Downloads Android™ Java Libraries Android C/C++ Libraries

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    // This example requires the Chilkat API to have been previously unlocked.
    // See Global Unlock Sample for sample code.

    // The 1st step in an S3 multipart upload is to initiate it,
    // as shown here: Initiate S3 Multipart Upload

    // The 2nd step is to upload the parts
    // as shown here: S3 Upload Parts

    // The 3rd and final step (this example) is to complete the multipart upload.

    // Other S3 Multipart Upload Examples:
    // Abort Multipart Upload
    // List Parts

    // When the multipart upload was initiated, an UploadId was provided in the XML response, and it 
    // was saved to a file.  Steps 2 and 3 begin by loading the XML and getting
    // the Upload ID.

    CkXml xmlInit = new CkXml();
    boolean success = xmlInit.LoadXmlFile("s3_multipart_uploads/initiate.xml");
    if (success != true) {
        Log.i(TAG, "Did not find the initiate.xml XML file.");
        return;
        }

    String uploadId = xmlInit.getChildContent("UploadId");
    Log.i(TAG, "UploadId = " + uploadId);

    // We'll also need the XML file that contains a record of the parts
    // with part numbers and ETags.  (This file was produced when parts were being uploaded.)
    CkXml xmlPartsList = new CkXml();
    success = xmlPartsList.LoadXmlFile("s3_multipart_uploads/partsList.xml");
    if (success != true) {
        Log.i(TAG, "Did not find the partsList.xml XML file.");
        return;
        }

    CkRest rest = new CkRest();

    // Connect to the Amazon AWS REST server.
    boolean bTls = true;
    int port = 443;
    boolean bAutoReconnect = true;
    success = rest.Connect("s3.amazonaws.com",port,bTls,bAutoReconnect);

    // ----------------------------------------------------------------------------
    // Important: For buckets created in regions outside us-east-1,
    // there are three important changes that need to be made.
    // See Working with S3 Buckets in Non-us-east-1 Regions for the details.
    // ----------------------------------------------------------------------------

    // Provide AWS credentials for the REST call.
    CkAuthAws authAws = new CkAuthAws();
    authAws.put_AccessKey("AWS_ACCESS_KEY");
    authAws.put_SecretKey("AWS_SECRET_KEY");
    authAws.put_ServiceName("s3");

    success = rest.SetAuthAws(authAws);

    // Set the bucket name via the HOST header.
    // In this case, the bucket name is "chilkat100".
    rest.put_Host("chilkat100.s3.amazonaws.com");

    // The "uploadId=UploadId" must be added as a query parameter.  This allows it to be 
    // incorporated into the AWS signature calculation, which is a requirement.
    // Therefore, we use AddQueryParam:
    rest.AddQueryParam("uploadId",uploadId);

    // Our ObjectName in this case is "somethingBig.zip".
    String responseXml = rest.fullRequestString("POST","/somethingBig.zip",xmlPartsList.getXml());
    if (rest.get_LastMethodSuccess() != true) {
        Log.i(TAG, rest.lastErrorText());
        return;
        }

    // When successful, the S3 Storage service will respond with a 200 response code,
    // with an XML body.  
    if (rest.get_ResponseStatusCode() != 200) {
        // Examine the request/response to see what happened.
        Log.i(TAG, "response status code = " + String.valueOf(rest.get_ResponseStatusCode()));
        Log.i(TAG, "response status text = " + rest.responseStatusText());
        Log.i(TAG, "response header: " + rest.responseHeader());
        Log.i(TAG, "response body: " + responseXml);
        Log.i(TAG, "---");
        Log.i(TAG, "LastRequestStartLine: " + rest.lastRequestStartLine());
        Log.i(TAG, "LastRequestHeader: " + rest.lastRequestHeader());
        }

    // Load the XML response into Chilkat XMl and emit via GetXml to see the XML in a pretty-printed (indented) readable format.
    CkXml xml = new CkXml();
    xml.LoadXml(responseXml);
    Log.i(TAG, xml.getXml());
    Log.i(TAG, "----");

    Log.i(TAG, "Multipart upload completed.");

  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}