Go to the file manager and find the APK file. It is normally found in download folder. Then, Tap on it. If you are new to this installation procedure, then you would be asked to allow unknown sources or allow this source option. Kindly allow it. Again go to the APK file location and Install Vanced Manager APK on your android device. Standalone Installation Wizard for Communication Manager 6.0.1. This standalone version of the CM 6.0 / CM 6.0.1 Installation Wizard runs on Windows XP and allows an Electronic Pre-installation Worksheet (EPW file) to be created off-line prior to installing a Communication Manager 6.0 / 6.0.1 template.
After you issue the agentadmin command and acceptthe license agreement (if necessary) the installation program appears, promptingyou for information.
The steps in the installation program are displayed in this sectionin an example interaction. Your answers to prompts can differ slightly orgreatly from this example depending upon your specific deployment. In theexample, most of the defaults have been accepted. This example is providedfor your reference and does not necessarily indicate the precise informationyou should enter.
The following bulleted list provides key points about the installationprogram.
Each step in the installation program includes an explanationthat is followed by a more succinct prompt.
For most of the steps you can type any of the following charactersto get the results described:
- ?
Type the question mark to display Help information for thatspecific step.
- <
Type the left arrow symbol to go back to the previous interaction.
- !
Type the exclamation point to exit the program.
Most of the steps provide a default value that can be acceptedor replaced. If a default value is correct for your site, accept it. If itis not correct, enter the correct value.
About Installation Prompts in Agent for Apache Tomcat 6.0
The following list provides information about specific prompts in theinstallation. Often the prompt is self explanatory. However, at other timesyou might find the extra information presented here to be very helpful. Thisextra information is often not obvious. Study this section carefully beforeissuing the agentadmin --install command.
The deployment URI for the agent application is required forthe agent to perform necessary housekeeping tasks such as registering policyand session notifications, legacy browser support, and CDSSO support. Accept /agentapp as the default value for this interaction. Once the installationis completed, browse the directory PolicyAgent-base/etc. Use the agentapp.war file to deploy theagent application in the application container. Please note that the deploymentURI for agent application during install time should match the deploymentURI for the same application when deployed in the J2EE container.
This key is used to encrypt sensitive information such thepasswords. The key should be at least 12 characters long. A key is generatedrandomly and provided as the default. You can accept the random key generatedby the installer or create your own using the .agentadmin --getEncryptKey command.
For information about creating a new encryption key, see agentadmin --getEncryptKey.
An agent profile should have been created as a pre-installationstep. The creation of the agent profile is mentioned in that section. Forthe pre-installation steps, see Preparing to Install Agent for Apache Tomcat 6.0. For the actual information on creatingan agent profile, see Creating a J2EE Agent Profile.
In summary, the J2EE agent communicates with Access Manager with a specificID and password created through an agent profile using Access Manager Console.For J2EE agents, the creation of an agent profile is mandatory. Access Manager usesthe agent profile to authenticate an agent. This is part of the security infrastructure.
The J2EE password file should have been created as a pre-installationstep. For the pre-installation steps, see Preparing to Install Agent for Apache Tomcat 6.0.
When the installation program prompts you for the password for the agent,enter the fully qualified path to this password file.
After you have completed all the steps, a summary of your responsesappears followed by options that allow you to navigate through those responsesto accept or reject them.
When the summary appears, note the agent instance name, such as agent-001. You might be prompted for this name during the configuration process.
About the options, the default option is 1, Continue with Installation.
If you are satisfied with the summary, choose 1 (the default).
If you want to edit input from the last interaction, choose2.
If you want to edit input starting at the beginning of theinstallation program, choose 3.
If you want to exit the installation program without installing,choose 4.
You can edit your responses as necessary, return to the options list,and choose option 1 to finally process your responses.
Example of Installation Program Interaction in Agentfor Apache Tomcat 6.0
The following example is a sample installation snapshot of Policy Agent 2.2 for Apache Tomcat 6.0.By no means does this sample represent a real deployment scenario.
The section following this example, Implications of Specific Deployment Scenarios in Agent for Apache Tomcat 6.0, providesa short explanation about installing a J2EE agent on multiple Apache Tomcat 6.0 instances.If your deployment includes multiple instances of the deployment container,you might want to review that section before proceeding with the agent installation.See Installing a J2EE Agent on Multiple Apache Tomcat 6.0 Instances.
Implications of Specific Deployment Scenarios inAgent for Apache Tomcat 6.0
The following section refers to a specific deployment scenario involving Policy Agent 2.2 for Apache Tomcat 6.0.
Installing a J2EE Agent on Multiple Apache Tomcat 6.0 Instances
Once a J2EE agent is installed for a particular Apache Tomcat 6.0 instance,you can install the agent on another instance on the same machine by runningthe agentadmin --install command. Onceprompted to enter the appropriate server instance name, enter the server configurationdirectory and unique instance name that will enable the agent to distinguishthe first instance from consecutive instances.
Summary of a J2EE Agent Installation in Policy Agent 2.2
At the end of the installation process, the installation program printsthe status of the installation along with the installed J2EE agent information.The information that the program displays can be very useful. For example,the program displays the agent instance name, which is needed when configuringa remote instance. The program also displays the location of specific files,which can be of great importance. In fact, you might want to view the installationlog file once the installation is complete, before performing the post-installationsteps as described in Chapter 4, Post-Installation Tasks of Policy Agent 2.2 for Apache Tomcat 6.0.
The location of directories displayed by the installer are specific.However, throughout this guide and specifically in Summary of Agent Installationshown in this section, PolicyAgent-base is usedto describe the directory where the distribution files are stored for a specificJ2EE agent.
The following example serves as a quick description of the locationof the J2EE agent base directory (PolicyAgent-base)of Policy Agent 2.2 for Apache Tomcat 6.0.
Example 3–1 Policy Agent Base Directory of Agent for Apache Tomcat 6.0
The following directory represents PolicyAgent-base ofAgent for Apache Tomcat 6.0:
where Agent-HomeDirectory is the directoryyou choose in which to unpack the J2EE agent binaries.
Information regarding the location of the J2EE agent base directoryis explained in detail in Location of the J2EE Agent Base Directory in Policy Agent 2.2.
The following type of information is printed by the installer:
Once the agent is installed, the directories shown in the precedingexample are created in the agent_00x directory, whichfor this example is specifically Agent_001. Those directoriesand files are briefly described in the following paragraphs.
Location of the J2EE agent AMAgent.properties configurationfile for the agent instance. Every instance of a J2EE agent has a unique copyof this file. You can configure this file to meet your site's requirements.For more information, see the following sections:
Location of the J2EE agent local audit trail.
Location of all debug files required to debug an agent installationor configuration issue.
Location of the file that has the agent install file location.If the installation failed for any reason, you can look at this file to diagnosethe issue.
Update the system packages:
Install the depencies:
Note, that the EMSM needs at least Python 3.2 to run.
Install the EMSM Python package from PyPi:
This will also install all EMSM Python depencies.
Create the user, that should run the EMSM:
Create the instance folder. This folder will later contain all worlds andserver executables:
Create the
/opt/minecraft/minecraft.pyEMSM launcher and add it tothe global PATH:Make sure the
/opt/minecraft/directory is owned by the minecraftuser:Execute the EMSM:
That’s it. Your instance directory should now look like this:
You probably want to use some plugins like the guard,initd or backups plugin. So don’tforget to take a look at their documentation later.
Troubleshooting¶
WrongUserError¶
Aperto Installation Manager 6.0 Free
If you run the application under another user than minecraft, youhave to edit the conf/main.conf configuration file before you call theEMSM the first time otherwise you will get a WrongUserError: