Cisco Cisco Application Extension Platform for SRE
Cisco Application eXtension Platform 1.0 Quick Start Guide
Packaging Applications on Cisco AXP
9
Cisco Application eXtension Platform 1.0 Quick Start Guide
OL-15669-01
Preparing the Cisco AXP SDK
Preparing Cisco AXP SDK: Example
To prepare the Cisco AXP SDK onto your development machine, perform the following steps.
Step 1
[root@fedora axp_1.0.1]# tar –xzf sdk.nme.1.0.1.tar.gz
<enter>
This command untars the Cisco AXP SDK file into the /opt/axp-sdk.1.0.1/ directory. The SDK file name
is sdk.nme.#.tar, where # is the version number of Cisco AXP SDK software. The version number of the
SDK you are using matches must match exactly with the Cisco AXP version number loaded onto the
Cisco AXP service module. This Quick Start guide assumes that you are working with Cisco AXP 1.0.1.
The Cisco AXP SDK directories are created in the /opt/axp-sdk.1.0.1/ directory.
is sdk.nme.#.tar, where # is the version number of Cisco AXP SDK software. The version number of the
SDK you are using matches must match exactly with the Cisco AXP version number loaded onto the
Cisco AXP service module. This Quick Start guide assumes that you are working with Cisco AXP 1.0.1.
The Cisco AXP SDK directories are created in the /opt/axp-sdk.1.0.1/ directory.
Step 2
Examine the SDK subdirectory structure.
Step 3
Before you begin running the packaging script, make sure that you have the appropriate certificates
loaded onto your system.
loaded onto your system.
This guide assumes that you placed the certificates in the /opt/axp-sdk.1.0.1/keys directory, however,
you can choose another directory.
you can choose another directory.
a.
Make a note of where you place the certificates, because the interactive installer will later ask
you for the location of the certificates.
you for the location of the certificates.
[root@fedora keys]# ls
<enter>
dev_authorization.sig dev_certificate.sig private.key
Step 4
Ensure that all three keys in step 3 are present in a readable directory. If you are missing any keys, you
cannot continue. Contact your Cisco representative to procure these files.
cannot continue. Contact your Cisco representative to procure these files.
Step 5
Create an output directory in the /opt directory (or directory of your choice) if you have not already
created it. This directory is used by the packaging tool to store the final package files (*.pkg, *.prt1).
created it. This directory is used by the packaging tool to store the final package files (*.pkg, *.prt1).
Step 6
Enter the chmod command to ensure the directory has the correct privileges:
[root@fedora opt]# mkdir output
<enter>
[root@fedora opt]# chmod 755 output
<enter>
Step 7
Invoke the package builder tool pkg_build.sh.
Table 4
Directory Structure in Examples
Directory Name
Definition
Example
sdk-directory
Directory where the developer untars the
Cisco AXP SDK.
Cisco AXP SDK.
/opt/axp-sdk.1.0.1/
source-directory
Parent directory where the unpackaged
application source files are stored.
application source files are stored.
/opt/tcptrace/
keys-directory
Directory where development
authorization, development certification,
and private key are stored.
authorization, development certification,
and private key are stored.
/opt/axp-sdk.1.0.1/keys/
project-directory Parent
directory where the Cisco AXP
package builder tool places execution
output (including packages to be installed
on the Cisco AXP service module).
output (including packages to be installed
on the Cisco AXP service module).
/opt/output/