diff --git a/support/docs/IBMi_userguide.md b/support/docs/IBMi_userguide.md new file mode 100644 index 0000000..84a6c07 --- /dev/null +++ b/support/docs/IBMi_userguide.md @@ -0,0 +1,107 @@ +# IBM® i User Guide + +Welcome to the IBM® i User Guide for IBM® Power® Access Cloud. This guide walks you through deploying an IBM® i instance and accessing it via SSH and 5250 console. + +--- + +## 1. Phase 1: Deployment via Power Access Cloud + +**Steps:** + +### Access Catalog +1. Log in to your Power Access Cloud portal. +2. Navigate to the **Catalog** by clicking on the "Catalog" button or "Go to Catalog". + +### Select Image +1. Locate the IBM i base image (or the specific version required for your workload). + +### Configure & Deploy +1. Click on the **Deploy** button. +2. Enter the name for your Virtual Machine and click **Submit** to start provisioning. + +### Monitor Status +1. Go to the **Services** tab on the Home page. +2. The status will initially show as **Deploying**. +3. Wait for the status to transition to **Active**. + +--- + +## 2. Phase 2: The IPL and Boot Process + +**Important Note:** + +Once the status shows **Active**, an External IP address will be assigned to your machine. However, the OS is not immediately reachable. + +**For IBM i-based VMs**, the system must undergo an Initial Program Load (IPL) and several internal boot-up sequences. It typically takes **30–40 minutes** after the status turns "Active" before the SSHD (SSH Daemon) starts and the machine becomes accessible via the network. + +--- + +## 3. Phase 3: Initial Remote Access + +**Steps:** + +After 30-40 minutes of waiting, you can establish your first connection using the default administrative profile. + +1. **Retrieve IP:** Copy the External IP from the service details page. +2. **Connect via SSH:** Open your local terminal (PowerShell, Command Prompt, or Terminal) and run: + ```bash + ssh PAC@ + ``` + +--- + +## 4. Accessing 5250 Console via SSH-Key Tunneling + +**Prerequisites:** You have successfully enabled SSH-key based login. + +Follow these steps to establish your 5250 console: + +### Step 1: Set IBM i User Password + +SSH keys handle the secure "handshake" for the tunnel, but the 5250 sign-on screen still requires a standard IBM i password. + +``` +system "CHGUSRPRF USRPRF(*USER) PASSWORD(YourSecurePassword)" +``` + +**Note:** Replace `*USER` with your specific PAC user profile. + +### Step 2: Enable Telnet Service + +The 5250 session runs over Telnet (Port 23), which must be active on the system to accept the tunneled connection. + +``` +system "STRTCPSVR *TELNET" +``` + +### Step 3: Establish the SSH Tunnel + +On your local workstation (Laptop/PC), open a terminal or command prompt to create the secure bridge. This command maps a local port to the IBM i Telnet port. + +```bash +ssh -L 50000:localhost:23 PAC@powervs_public_ip +``` + +**Parameters:** +- `-L`: Maps local port 50000 to the remote localhost port 23. + +**Important:** Keep this terminal window open; closing it kills the connection to the 5250 console. + +### Step 4: Configure ACS 5250 Session + +With the tunnel active, configure your IBM i Access Client Solutions (ACS) tool to point at the local end of the tunnel. + +1. Open the **ACS Tool**. +2. Go to the **5250 Session Manager**. +3. Select **New Display Session**. +4. In the settings, enter the following: + - **Destination:** `localhost` + - **Port:** `50000` (This must match the port used in your SSH tunnel command). +5. Click **OK** or **Connect**. + +### Step 5: Sign On to 5250 + +The classic IBM i "Sign On" display will appear. + +1. Enter your **User ID** (PAC). +2. Enter the **Password** you created in Step 1. \ No newline at end of file diff --git a/web/src/components/ServicesForHome.jsx b/web/src/components/ServicesForHome.jsx index 9fc00a7..ba4ee8c 100644 --- a/web/src/components/ServicesForHome.jsx +++ b/web/src/components/ServicesForHome.jsx @@ -13,12 +13,13 @@ import { OverflowMenu, OverflowMenuItem, Button, - Tooltip + Tooltip, + InlineNotification } from "@carbon/react"; import { useNavigate } from "react-router-dom"; import { flattenArrayOfObject } from "./commonUtils"; import UserService from "../services/UserService"; -import { CheckmarkFilled,Pending,InProgress, Information, Renew,ErrorFilled } from "@carbon/icons-react"; +import { CheckmarkFilled,Pending,InProgress, Information, Renew,ErrorFilled, Launch } from "@carbon/icons-react"; import DeleteService from "./PopUp/DeleteService"; import ServiceExtend from "./PopUp/ServiceExtend"; import ServiceDetails from './PopUp/ServiceDetails'; @@ -113,13 +114,6 @@ const ServicesForHome=({groups})=> { setServicesRows(data?.payload); setLoading(false); }; - // useEffect(()=>{ - // fetchServicesData(); - // const intervalId = setInterval(() => { - // fetchServicesData(); // Fetch data every 1 minutes - // }, 60000); - // return () => clearInterval(intervalId); - // },[actionProps]) useEffect(()=>{ fetchServicesData(); @@ -223,11 +217,33 @@ const ServicesForHome=({groups})=> { + + {/* --- IBMI OPEN NOTE --- */} + + Once the status is Active, the system requires 35-40 minutes to fully initialize before SSH access is available. The default username is PAC. For more reference,{' '} + + go to link + + + } + style={{ marginBottom: '1rem', marginTop: '1rem', maxWidth: '100%' }} + /> - {((rows.length>0)&& + {((rows.length>0)&&
{headers.map((header) => ( @@ -241,13 +257,12 @@ const ServicesForHome=({groups})=> { {rows.map((row) => ( {row.cells.map((cell,i) => (cell.value && - // {cell.value} ((i!==2)?{cell.value}:{row.cells[i].value==="PENDING EXTENSION"&&<> - - + + @@ -296,8 +311,6 @@ const ServicesForHome=({groups})=> { ))} - { - }
)}