Jump to content
The ibi Community has moved to a new platform: Please Sign In and choose Forgot Password to continue
  • Welcome!

    We are so excited to have you here.

    Join now to access our forum discussions on all things ibi - products, solutions, how-to's, knowledgebase, peer support and more.

    Please register or login to take part. (If you had a previous community account simply click > Sign In > Forgot Password)


  • Our picks View All

    • The first ibi Summit event in Boston, MA is under way.

      We have had a fantastic turn out for today's event. Here is an image of Dan Ortolani (VP of Support) presenting to the attendees.  (Panel includes: Angie Hildack and Porter Thorndike)

      If you were not able to get to Boston today, make sure to book your spot for next upcoming in-person event ibi Summit Arlington VA in May.

      You can see all the details here

      • 2 replies
        • Like
    • Registration for the second stop on the ibi Summit Roadshow in Arlington, VA is now live!

      Join us for this in-person event on May 14th, 2024 from 8:00 AM - 5:00 PM EDT, for a full day of product training, hands-on-labs, and an open Expert Room.

      Follow this link to save your spot. We can't wait to see you there.
      • 0 replies
        • Like
    • One of the more highly discussed features we hear and see being discussed in the industry today is the ability for users to customize their experience. There is a pretty strong desire in the tools we use in our every day lives to make it look and work the way we want to fit our own preferences. It makes it feel more personal and frankly more usable when it feels like our own. We are looking for some of your own personal thoughts on this subject with respect to tools you use for work. Is personalization something that's important to you? We want to know.
      • 8 replies
        • Like
    • We are pleased to announce that in the Dresner Advisory Services, LLC Technology Innovation Awards, the ibi portfolio has placed across three categories: Analytical Platforms, Cloud Computing + BI, and Master Data Management. Check out more in the release here.
      • 0 replies
        • Like

Welcome to the ibi Community

See recent community activity

  • In this demo, we begin with the default setup of WebFOCUS CE 1.2.0 (WF 9.2), and proceed to assign a Fully Qualified Domain Name (FQDN) to the host running this WF-CE setup. We then install an ingress controller to allow access to the Application Server via standard port 80, rather than the default port 31080. The video concludes with installing an SSL Certificate to secure the Application Server's endpoint with TLS.

    High-level steps : 
    - Begin by deploying the standard configuration of WebFOCUS CE as provided. - Ensure that the setup is accessible via Port 31080, which is the default port. - Deploy an Ingress controller and create an Ingress resource within the webfocus namespace to facilitate access over Port 80. - Incorporate a secret containing a TLS/SSL certificate into the webfocus namespace and modify the Ingress resource to utilize this secret for secure connections. - Access the WebFOCUS configuration securely over HTTPS (Port 443). - (Optional) Consider deactivating Port 31080 to prevent access through the unsecured port.

    Out-of-the-box setup : 
    Once the WebFOCUS CE setup completes deploying all components - you should be able to access the WF App server using port 31080

    If the above succeeds, you can also access the WebFOCUS App server GUI over the browser by going to the URL: http://x.1.10.96:31080 
    Install NGINX ingress controller.
    In the previous topic, we saw we have to access WebFOCUS using port 31080; what if we want to just access it over port 80 or not provide a port at all? 
    For that, we need to install an Ingress controller in the K8s cluster; in this case, we will use NGINX.  
    Let's install the Ingress controller in the kubernetes cluster - you can use the commands below. 
    # Lable all Nodes to allow Ingress controller to run kubectl label nodes --all ingress-ready=true # Install NGINX Ingress controller that will attach Controller POD to port 80 and 443 on Node kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/kind/deploy.yaml # Wait for all Ingress controller pods to come up kubectl wait --namespace ingress-nginx --for=condition=ready pod --selector=app.kubernetes.io/component=controller --timeout=90s After the Ingress controller is running, if you run the nc  command again to see if Port 80 is open or not 
    nc -zv x.1.10.96 80 
    If the above command succeeds, we know NGINX ingress is running fine on port 80 - now the next thing we need to do is create an Ingress Object in the webfocus namespace so we can access WebFOCUS on port 80 
    Now onwards, we're going to access the above Machine with its FQDN name - in this example, it is wfce02.ibi.systems  - we assume you have something similar in your case; if not, ask your system admin to configure FQDN for your VM/Machine.
    So, in our case, if I re-run the above command as 
    # Use nc to check if port 80 is open now nc -zv wfce02.ibi.systems 80 >> Connection to wfce02.ibi.systems (x.241.1.29) 80 port [tcp/http] succeeded! In the above, we assume the FQDN name "wfce02.ibi.systems" points to the correct IP of the machine where WF CE is running ( in this case, IP x.241.1.29) 
    If the "nc" command returns with success, we are good to go to the next step 
    Create Ingress Object in webfocus namespace 

    Save the text below as an "appserver-ingress.yaml" file; as you can see, we are now using the FQDN of wfce02.ibi.systems to set up Ingress rules.
    This file also assumes your WF-CE setup is running in Namespace "webfocus." 
    Note: make changes as needed before you apply it 
    apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: kubernetes.io/ingress.class: nginx meta.helm.sh/release-name: appserver meta.helm.sh/release-namespace: webfocus nginx.ingress.kubernetes.io/affinity: cookie nginx.ingress.kubernetes.io/affinity-mode: persistent nginx.ingress.kubernetes.io/app-root: /webfocus nginx.ingress.kubernetes.io/client-body-buffer-size: 64k nginx.ingress.kubernetes.io/force-ssl-redirect: "false" nginx.ingress.kubernetes.io/proxy-body-size: 200m nginx.ingress.kubernetes.io/proxy-connect-timeout: "300" nginx.ingress.kubernetes.io/proxy-read-timeout: "300" nginx.ingress.kubernetes.io/rewrite-target: / nginx.ingress.kubernetes.io/session-cookie-change-on-failure: "true" nginx.ingress.kubernetes.io/session-cookie-expires: "28800" nginx.ingress.kubernetes.io/session-cookie-max-age: "28800" nginx.ingress.kubernetes.io/session-cookie-name: sticknesscookie nginx.ingress.kubernetes.io/whitelist-source-range: labels: app.kubernetes.io/instance: appserver app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: appserver app.kubernetes.io/version: "1.0" helm.sh/chart: appserver-0.1.0 name: appserver namespace: webfocus spec: rules: - host: wfce02.ibi.systems http: paths: - backend: service: name: appserver port: name: port8080 path: / pathType: ImplementationSpecific Apply the above file to the step 
    This should create an Ingress rule in the ingress controller that sends any HTTP request incoming on port 80 with the HTTP Host header set to "wfce02.ibi.systems" - I will forward that request to the kubernetes service named "appserver" over port 8080. 
    Now you should be able to access the WebFOCUS App server GUI via the URL: http://wfce02.ibi.systems 

    Securing endpoint with SSL 
    As you can see, the above URL is http://  that is not secure - we want to enable SSL so that we can access WebFOCUS GUI over SSL  - such as URLs starting with https://  
    For this, we need to get certificates generated for our FQDN - in the above case  'wfce02.ibi.systems'; typically, you will get two PEM files - one named "privkey.pem" and the other "fullchain.pem"
    You can inspect the "fullchain.pem" file to see if it is indeed issued for the FQDN you use (a wild card is also okay). For this, you will need the OpenSSL tool installed on your machine. 

    You will need two files—one with the key file and the other with a certificate file. First, we create a Kubernetes secret with these two files in the same 'webfocus' namespace.  
    Once the secret has been created, the only thing left to do is to update the Ingress object in the webfocus namespace to use this secret to enable TLS/SSL. 
    Now, let's update the appserver-ingress.yaml  file to use this secret (wfce02-ibi-tls ) that we created above 

    Add the below lines at the end. 
    Re-apply this file to the cluster - this will update the ingress object to now support SSL (port 443) 
    If all goes as expected - now you should be able to access WebFOCUS over HTTPS -  https://wfce02.ibi.systems
    (Optional) Disable Port 31080 port 
    Since we now have a secure way to access the WebFOCUS App server over SSL - we don't need to access the App server over port 31080 - so edit the service for the App server and change it from NodePort to Cluster IP type of service. 

    At the beginning of this demo, we saw that we could access the WebFOCUS App server GUI over port 31080 - but now that is unnecessary as we can access the App server over secure port 443.
    So it makes sense to disable port 31080 - for that, we need to change appserver - Service (svc) to type ClusterIP from NodePort - below command to do that.

  • Users may receive an error after executing a procedure or HTML file from ibi WebFOCUS® App Studio when using Google Chrome or Microsoft Edge.
    Web browsers receive updates, and when a new version of Chrome or Edge browser is available, a new version of the selenium driver is also required to execute procedures and HTML files from ibi WebFOCUS App Studio.

    Currently, there is not an automatic way to update the Chrome and Edge drivers. However, users can manually update these drivers. 
    Make sure that you are on the latest version of Chrome or Edge. To find this information:  For Chrome: Click the ellipses on the top-right of the browser window to expand the drop-down menu. Then click Help > About Google Chrome. For Edge: Click the ellipses on the top-right of the browser window to expand the drop-down menu. Then click Help and feedback > About Microsoft Edge. Navigate to the following sites to download the WebDriver for Chrome or Edge: For Chrome: https://chromedriver.chromium.org/downloads For Edge: https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/ Select the WebDriver version that corresponds to the browser version that you are on and download the WebDriver. See the following images for an example. 
    In the downloaded zip file, locate the chromedriver.exe file for Chrome or the msedgedriver.exe file for Edge. These are the WebDriver files. Shut down App Studio and copy the WebDriver files to the bin directory of the App Studio installation, for example, <drive>:ibiAppStudio90bin or <drive>:ibiAppStudio82bin. Start App Studio to test the browser setup. Navigate to Application Menu > Output Viewer Settings. Select the desired browser, and then click Test browser setup. If successful, App Studio will open up the selected browser and display the message Webdriver test status Success, as shown in the following image. Once this message displays, you have successfully updated the browser's WebDriver.
  • If you are interested in the FOCUS language, whether you are using ibi FOCUS or ibi WebFOCUS products, FOCUS Fridays is a monthly user group that centers around the FOCUS language.

    You can expect basic FOCUS concepts from all parts of the language: TABLE, MODIFY, MATCH. GRAPH, Dialogue Manager, JOIN, MAINTAIN; advanced FOCUS language techniques to enhance functionality and performance in WebFOCUS and FOCUS; and coverage of new features as they appear in the products.  

    These sessions all come with the live, freewheeling discussion, demonstrations, and Q&A with three of the FOCUS/WebFOCUS language gurus - Walter Blood and Walter Brengel  - representing together more than 70 years of experience. Join us for the basics, to get the techniques you need, and to tell us how you use the language. We love active participation, so join us for FOCUS Fridays!

    Browse the event schedule or watch recorded sessions on demand.
  • When planning your ibi WebFOCUS upgrade, please consider the most recent release of ibi WebFOCUS. ibi WebFOCUS v9.0 is now available on the ibi Product Download site (edelivery.ibi.com) and includes significant enhancements and innovations across the product. For complete details of all features, see our ibi WebFOCUS Product Documentation. 

    As a valued customer, we want you to benefit from WebFOCUS v.9.0 as well as the robust capabilities available via the ibi WebFOCUS Edition product package. So we are offering the ibi WebFOCUS Technology Refresh program, a new service to ensure a smooth transition to this latest, feature-rich release.

    For further information, please visit the ibi WebFOCUS Technology Refresh Program site.
  • Create New...