#查看系統自帶的jdk[root@localhost ~]# rpm -qa | grep jdkjava-1.7.0-openjdk-1.7.0.79-2.5.5.4.el6.x86_64java-1.6.0-openjdk-1.6.0.35-1.13.7.1.el6_6.x86_64#卸載系統自帶openjdk[root@localhost ~]# rpm -e --nodeps java-1.6.0-openjdk-1.6.0.35-1.13.7.1.el6_6.x86_64[root@localhost ~]# rpm -e --nodeps java-1.7.0-openjdk-1.7.0.79-2.5.5.4.el6.x86_64#查看jdk版本[root@localhost ~]# java -version-bash: /usr/bin/java: 沒有那個文件或目錄#ok,卸載成功！#下面安裝我們自己的jdk#自己去下載[root@localhost ~]# cd /usr/local/java/jdk#查看目錄文件[root@localhost java]# lsjdk-7u79-linux-x64.tar.gz#解壓[root@localhost jdk]# tar -zxvf jdk-7u79-linux-x64.tar.gz#授權[root@localhost jdk]# chmod +x jdk1.7.0_79/

#查看[root@localhost java]# ls tomcat/apache-tomcat-7.0.29.tar.gz#解壓[root@localhost tomcat]# tar -zxvf apache-tomcat-7.0.29.tar.gz #授權[root@localhost jdk]# chmod +x apache-tomcat-7.0.29

#編輯profile文件：vim /etc/profileexport JAVA_HOME=/usr/local/java/jdk/jdk1.7.0_79export CALSSPATH=$JAVA_HOME/lib/*.* export PATH=$PATH:$JAVA_HOME/bin export TOMCAT_HOME=/usr/local/java/tomcat/apache-tomcat-7.0.29export CATALINA_HOME=/usr/local/java/tomcat/apache-tomcat-7.0.29#保存文件并退出！

#使設置立即生效：[root@localhost jdk]# source /etc/profile#查看jdk是否安裝成功[root@localhost jdk]# java -versionjava version "1.7.0_79"Java(TM) SE Runtime Environment (build 1.7.0_79-b15)Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)#成功！#啟動tomcat[root@localhost bin]# sh /usr/local/java/tomcat/apache-tomcat-7.0.29/bin/startup.sh#查看啟動日志[root@localhost bin]# tail -f /usr/local/java/tomcat/apache-tomcat-7.0.29/logs/catalina.out#訪問tomcathttp://192.168.81.115:8080/#如果訪問不了，要開啟防火墻#打開防火墻端口命令#開啟8080端口[root@localhost bin]# /sbin/iptables -I INPUT -p tcp --dport 8080 -j ACCEPT#再次訪問tomcathttp://192.168.81.115:8080/

apktool.jar下載#授權[root@localhost apktool]# chmod +x aapt#執行[root@localhost apktool]# ./aapt-bash: ./aapt: /lib/ld-linux.so.2: bad ELF interpreter: 沒有那個文件或目錄#那么在64位操作系統下去執行./aapt命令的話會報以上錯誤#我們需要安裝：glibc.i686，zlib.i686，libstdc++.i686#(1.)第一步[root@localhost apktool]# yum install glibc.i686[root@localhost apktool]# ./aapt#./aapt: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory#(2.)第二步[root@localhost apktool]# sudo yum install zlib.i686[root@localhost apktool]# ./aapt#./aapt: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory#(3.)第三步[root@localhost apktool]# sudo yum install libstdc++.i686#運行./aapt version看看是否安裝成功[root@localhost apktool]# ./aapt version#Android Asset Packaging Tool, v0.2#如果出現以上說明安裝成功，或者可以執行運行./aapt，如果出現一大坨和最下面的相同的東西說明成功；如果還是報錯，就繼續往下走#(4.)第四步[root@localhost apktool]# ./aapt#看最后一句#Protected multilib versions: libstdc++-4.4.7-17.el6.i686 != libstdc++-4.4.7-16.el6.x86_64#如果報錯的話需要升級 ！= 后面的版本，執行[root@localhost apktool]# yum update libstdc++-4.4.7-16.el6.x86_64[root@localhost apktool]# ./aapt#./aapt: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory#還是報錯，繼續#(5.)第五步[root@localhost apktool]# yum install libstdc++.so.6[root@localhost apktool]# ./aaptAndroid Asset Packaging ToolUsage:aapt l[ist] [-v] [-a] file.{zip,jar,apk}List contents of Zip-compatible archive.aapt d[ump] [--values] WHAT file.{apk} [asset [asset ...]]badging Print the label and icon for the app declared in APK.permissions Print the permissions from the APK.resources Print the resource table from the APK.configurations Print the configurations in the APK.xmltree Print the compiled xmls in the given assets.xmlstrings Print the strings of the given compiled xml assets.aapt p[ackage] [-d][-f][-m][-u][-v][-x][-z][-M AndroidManifest.xml] /[-0 extension [-0 extension ...]] [-g tolerance] [-j jarfile] /[--debug-mode] [--min-sdk-version VAL] [--target-sdk-version VAL] /[--app-version VAL] [--app-version-name TEXT] [--custom-package VAL] /[--rename-manifest-package PACKAGE] /[--rename-instrumentation-target-package PACKAGE] /[--utf16] [--auto-add-overlay] /[--max-res-version VAL] /[-I base-package [-I base-package ...]] /[-A asset-source-dir] [-G class-list-file] [-P public-definitions-file] /[-S resource-sources [-S resource-sources ...]] [-F apk-file] [-J R-file-dir] /[--product product1,product2,...] /[raw-files-dir [raw-files-dir] ...]Package the android resources. It will read assets and resources that aresupplied with the -M -A -S or raw-files-dir arguments. The -J -P -F and -Roptions control which files are output.aapt r[emove] [-v] file.{zip,jar,apk} file1 [file2 ...]Delete specified files from Zip-compatible archive.aapt a[dd] [-v] file.{zip,jar,apk} file1 [file2 ...]Add specified files to Zip-compatible archive.aapt v[ersion]Print program version.Modifiers:-a print Android-specific data (resources, manifest) when listing-c specify which configurations to include. The default is allconfigurations. The value of the parameter should be a commaseparated list of configuration values. Locales should be specifiedas either a language or language-region pair. Some examples:enport,enport,land,en_USIf you put the special locale, zz_ZZ on the list, it will performpseudolocalization on the default locale, modifying all of thestrings so you can look for strings that missed theinternationalization process. For example:port,land,zz_ZZ-d one or more device assets to include, separated by commas-f force overwrite of existing files-g specify a pixel tolerance to force images to grayscale, default 0-j specify a jar or zip file containing classes to include-k junk path of file(s) added-m make package directories under location specified by -J-u update existing packages (add new, replace older, remove deleted files)-v verbose output-x create extending (non-application) resource IDs-z require localization of resource attributes marked withlocalization="suggested"-A additional directory in which to find raw asset files-G A file to output proguard options into.-F specify the apk file to output-I add an existing package to base include set-J specify where to output R.java resource constant definitions-M specify full path to AndroidManifest.xml to include in zip-P specify where to output public resource definitions-S directory in which to find resources. Multiple directories will be scannedand the first match found (left to right) will take precedence.-0 specifies an additional extension for which such files will notbe stored compressed in the .apk. An empty string means to notcompress any files at all.--debug-modeinserts android:debuggable="true" in to the application node of themanifest, making the application debuggable even on production devices.--min-sdk-versioninserts android:minSdkVersion in to manifest. If the version is 7 orhigher, the default encoding for resources will be in UTF-8.--target-sdk-versioninserts android:targetSdkVersion in to manifest.--max-res-versionignores versioned resource directories above the given value.--valueswhen used with "dump resources" also includes resource values.--version-codeinserts android:versionCode in to manifest.--version-nameinserts android:versionName in to manifest.--custom-packagegenerates R.java into a different package.--auto-add-overlayAutomatically add resources that are only in overlays.--rename-manifest-packageRewrite the manifest so that its package name is the package namegiven here. Relative class names (for example .Foo) will bechanged to absolute names with the old package so that the codedoes not need to change.--rename-instrumentation-target-packageRewrite the manifest so that all of its instrumentationcomponents target the given package. Useful when used inconjunction with --rename-manifest-package to fix tests againsta package that has been renamed.--productSpecifies which variant to choose for strings that haveproduct variants--utf16changes default encoding for resources to UTF-16. Only useful when APIlevel is set to 7 or higher where the default encoding is UTF-8.--non-constant-idMake the resources ID non constant. This is required to make an R java classthat does not contain the final value but is used to make reusable compiledlibraries that need to access resources.