Additional information regarding Version 2

Signed-off-by: worksofliam <mrliamallan@live.co.uk>

Author: worksofliam

src/content/docs/developing/debug/index.mdx

@@ -1,7 +1,7 @@
 ---
 title: Debugging 
 ---
-import { Aside, CardGrid, Card, Icon } from '@astrojs/starlight/components';
+import { Aside, CardGrid, Card, Icon, Tabs, TabItem } from '@astrojs/starlight/components';
 
 # ILE Debugging
 
@@ -57,20 +57,35 @@ To debug a program from the Object Browser, right-click on the program object an
 
 * PTFs
 * Certificates setup on the server
-   * created in `/QIBM/UserData/IBMiDebugService/certs`
+   * created in `/QIBM/UserData/IBMiDebugService/certs` by default
 * IBM i Debug extension
    * installed into Visual Studio Code
-* Local client certificate (**optional**)
+* Local client certificate
    * can be imported with the 'Import local certificate' command
 
 ## Required PTFs
 
 To make use of the Debug Service, you need the following PTFs:
 
+<Tabs>
+<TabItem label="Version 1">
+
 * Host debugger in 5770SS1:
    * IBM i 7.5 PTF SI83666 and SI81035
    * IBM i 7.4 PTF SI83683 and SI81031
    * IBM i 7.3 PTF SI83692 and SI80858
+* Java 8 is required
+   * `/QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit`
+
+</TabItem>
+<TabItem label="Version 2">
+
+* *Version 2 not yet released.*
+* Java 11 is required
+   * `/QOpenSys/QIBM/ProdData/JavaVM/jdk11/64bit`
+
+</TabItem>
+</Tabs>
 
 After you have installed the PTFs, the connection inside of Visual Studio Code will need to be restarted.
 
@@ -88,12 +103,12 @@ After connecting to a system in Code for IBM i, if the PTFs are installed but th
 
 </Card></CardGrid>
 
----
-
 <Aside type="tip">
-   There only needs to be one instance of the Debug Service running. All developers share the Debug Service.
+   There only needs to be one instance of the Debug Service running and therefore the certificates should only be generated once. All developers share the Debug Service.
 </Aside>
 
+---
+
 ### Generating certificates
 
 <CardGrid>
@@ -104,6 +119,8 @@ This Walkthrough can easily configure the Debug Service and start it up. The las
 
 *It will ask you to confirm the initialisation.*
 
+If certificates already exist on the server, you may see a slightly different message as Code for IBM i will not replace existing certificates.
+
 </Card><Card>
 
 ![](./setup2_a.png)
@@ -118,7 +135,7 @@ This Walkthrough can easily configure the Debug Service and start it up. The las
 
 <Card>
 
-The 'Start debug service' button will spin up the Debug Service. If the Debug Service is already running, it will ask you if you want to end the existing instance before starting a new one - this is a requirement. It is not recommended to run two instances of the Debug Service at once.
+The 'Start debug service' button will spin up the Debug Service. If the Debug Service is already running, it will ask you if you want to end the existing instance before starting a new one - this is a requirement if you have generated new certificates on the server. It is not recommended to run two instances of the Debug Service at once.
 
 </Card><Card>
 
@@ -142,19 +159,23 @@ You can also start the Debug Service through the command palette:
 
 ## Debug Service ports
 
-The Debug Service depends on two ports by default:
+The Debug Service depends on three ports by default:
 
 * Port 8001 (unsecure port)
    * this port is not used for anything in regards to debugging, though it is required to start and stop the Debug Service
 * Port 8005 (secure port)
    * this port is used by all debugging clients and is required to start the Debug Service.
+* Port 8008
+   * this port is used for Service Entry Breakpoint (*only applies to version 2 of the Debug Service*)
+
+While you can configure the ports in the Connection Settings, it is recommended the defaults are used for consistency.
 
-These ports can be changed in `/QIBM/ProdData/IBMiDebugService/bin/DebugService.env`, both `DBGSRV_PORT` and `DBGSRV_SECURED_PORT` respectively.
+{/* These ports can be changed in `/QIBM/ProdData/IBMiDebugService/bin/DebugService.env`, both `DBGSRV_PORT` and `DBGSRV_SECURED_PORT` respectively.
 
 If `DBGSRV_SECURED_PORT` is changed, make sure to:
 
 * restart the Debug Service
-* change the Debug Service port number in the connection settings to your new port (`DBGSRV_SECURED_PORT`). **Every user will need to do this step.**
+* change the Debug Service port number in the connection settings to your new port (`DBGSRV_SECURED_PORT`). **Every user will need to do this step.** */}
 
 # FAQ