Content Comparison

...

The above link is the Data Center App Performance Toolkit User Guide for Jira.

In this document, it covers the use of the The Data Center App Performance Toolkit User Guide for Jira, available at this link, provides instructions for using the toolkit in two types of environments:

• Development environment

• Enterprise-scale environment

Follow Step 1 as described in the user guide. If Step 1 fails, proceed to Step 2.

New Data Center App Performance Toolkit version 8.3.2 with JMeter 5.6.3 support was released.
JMeter 5.6 has a bug which leads to broken .jmx file after opening JMeterUI 5.6.
Also, added pre-run hostname and license validations.Detailed release notes: https://github.com/atlassian/dc-app-performance-toolkit/releases . To get the latest version of the toolkit do git pull on the master branch. How to upgrade virtual env: pip install -r requirements.txt from your virtual env.
How to update docker image: docker pull atlassian/dcapt

Step 1:

For both types of environment need to environments, follow the same steps as mentioned outlined in the documentation. But while running the below command, if it fails we However, if the command mentioned below fails, you will need to run it manually.:

...

To execute the installation command for conf.tfvars using Docker and winpty, follow the steps below:

...

1. Set the environment name in the Git Bash:

   export ENVIRONMENT_NAME=your_environment_name

2. Run the following commands:

   docker run --pull=always --env-file ./app/util/k8s/aws_envs \ -e REGION1REGION=us-east-2 \ -e ENVIRONMENT_NAME=$ENVIRONMENT_NAME \ -v "/$PWD:/data-center-terraform/dc-app-performance-toolkit" \ -v "/$PWD/app/util/k8s/bzt_on_pod.sh:/data-center-terraform/bzt_on_pod.sh" \ -it atlassianlabs/terraform:2.7.1 bash

3. Configure AWS EKS:

   aws eks update-kubeconfig --name atlas-"$ENVIRONMENT_NAME"-cluster --region "$REGION"

4. Get the name of the execution environment pod:

   exec_pod_name=$(kubectl get pods -n atlassian -l=exec=true --no-headers -o custom-columns=":metadata.name") echo "INFO: Execution environment pod name: $exec_pod_name"

5. Execute a shell in the identified pod:

   kubectl exec -it "$exec_pod_name" -n atlassian -- bash

...

Note: Need to clear the instances running in the aws environment. Make sure check all the cases like volumes, groups, instances, EKS cluster, RDS database and General purpose buckets.

Step 2:

After pulling the Data Center App Performance Toolkit locally then follow the step 4. Setting up Jira Data Center enterprise-scale environment with "large" dataset. of documentation https://developer.atlassian.com/platform/marketplace/dc-apps-performance-toolkit-user-guide-jira

docker run --pull=always --env-file ./app/util/k8s/aws_envs \
-e REGION=us-east-2 \
-e ENVIRONMENT_NAME=$ENVIRONMENT_NAME \
-v "/$PWD:/data-center-terraform/dc-app-performance-toolkit" \
-v "/$PWD/app/util/k8s/bzt_on_pod.sh:/data-center-terraform/bzt_on_pod.sh" \
-it atlassianlabs/terraform:2.9.1 bash bzt_on_pod.sh jira.yml

Then we need to start execution by Navigate to dc-app-performance-toolkit folder. Before running the command need to add winpty before the command start as shown below

winpty docker run --pull=always --env-file aws_envs \
-v "/$PWD/dcapt.tfvars:/data-center-terraform/conf.tfvars" \
-v "/$PWD/dcapt-snapshots.json:/data-center-terraform/dcapt-snapshots.json" \
-v "/$PWD/logs:/data-center-terraform/logs" \
-it atlassianlabs/terraform:2.9.1 ./install.sh -c conf.tfvars

After completing Step 4 of the documentation, proceed to Step 5.

Ensure you add the application hostname without ‘http’ and ‘/jira’.

Continue following the steps as outlined in the documentation.

Before proceeding to Scenario 2: Scalability testing, you need to prepare the jira.jmx file. To do this, follow Step 3: Develop and test app-specific actions locally, using the JMeter app-specific action development example.

Once all runs are completed, generate the dependency tree and dependency check report.

1. Clone the repository.

2. Open a command prompt inside the repository folder and run:

   Code Block
   atlas-mvn clean atlas-mvn package

   This will generate the .jar and .obr files in the target folder.
   

3. Navigate to the dependency-check-8.3.1-release\dependency-check\bin directory and run:

   Code Block
   dependency-check.bat --scan BulkProfileImporter-1.8.jar --out . --format HTML

   This will generate the dependency check report in HTML format.
   

4. To get the dependency tree, use the following command:

   Code Block
   atlas-mvn dependency:tree -DoutputType=dot -DoutputFile=maven_dependency_tree.gv

If dependency tree command is not worked, then check in the below documentation if any update in the command of Open Web Application Security Project (OWASP)
https://developer.atlassian.com/platform/marketplace/dc-apps-security-scanner/