How to identify the correct JDeveloper version for your JCS / PaaS

Working in JCS / PaaS, many times we would be in cross roads as to which JDeveloper version needs to be picked up for the development.

I was recently made aware of the perils of choosing the wrong JDev version by my teammates, before which I slightly turned a blind eye on what might become a grave mistake.

However it is always recommented to verify the version from the JCS itself, before proceeding to downloading the appropriate JDeveloper.

Simply login into your JCS console ( i.e, Weblogic console ) and verify the version at the bottom left corner.

Also to check if your JDev is at the correct version level. Check the version from Help --> About.

Though this seems to be a trivial matter, if advanced version Jdev ( more than current JCS version ) is used to develop an application, it can never be downgraded to a lower version.
This would mean a complete re-work of the application in a lower version JDev.

Thanks for reading,
Srikanth

Deploying Oracle JET application ( .war file ) to Weblogic/ JCS

These steps are tested for Oracle JET 4.X release as well.

I was searching for the details on how to generate WAR file out of JET application and then deploy it to JCS / Weblogic.

I have found some really nice articles, however i would like to present the same in the way I understood them.

Not demeaning the content from those posts, I would like to condense the steps a little bit, so that it would be a reference to me as well. So here we go : 

a. Install the grunt-war using below command : 

         npm install grunt-war --save-dev

b. Verify if the directory "/grunt-war" is generated in the node_modules directory.

c. Create a javascript file as below in scripts folder : 

The file content is as below :

/*******************************************************************************/

module.exports =  {

  /*
   * Build a WAR (web archive) without Maven or the JVM installed.
   *
   * Template strings in the <%= %> tags are set in the data section of Gruntfile.js,
   *  or you can hardcode the strings here instead
   */
      
        target: {
          options: {
            war_dist_folder: '<%= distdir %>',      /* Folder to generate the WAR into, set in data section of Gruntfile.js */
            war_name: '<%= appname %>',            /* The name for the WAR file (.war will be the extension) */
            webxml_webapp_version: '2.5', /* I needed this older version for JCS-SX */  
            war_extras: [ {filename: 'grunt-war-credits.txt', data: 'This line will appear in the file!\n see http://likeahouseafire.com/2017/08/09/updated-using-grunt-to-create-war-jet3x/ '}, 
                          {filename: 'WEB-INF/weblogic.xml', data: '<?xml version="1.0" encoding="UTF-8"?>\n<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">\n  <jsp-descriptor>\n    <keepgenerated>true</keepgenerated>\n    <debug>true</debug>\n  </jsp-descriptor>\n  <context-root>/<%= appname %></context-root>\n</weblogic-web-app>'}],
                                          /* the war_extras are extra files to be generated, needed since grunt-war doesn't create a weblogic.xml */                                          /* also notice that we're using the <%= appname %> variable in there */  
            webxml_welcome: 'index.html', /* to point web.xml to the default page */
            webxml_webapp_extras: [ '<login-config />\n', '<session-config>\n    <session-timeout>\n    30\n    </session-timeout>\n</session-config>\n' ]  
                                          /* some extra settings for web.xml to work with JCS-SX */

          },
          files: [
            {
              expand: true,
              cwd: '<%= appdir %>',             /* find the source files for the WAR in the /web folder, set in Gruntfile.js */
              src: ['**'],
              dest: ''
            }
          ]
        }
};

/*******************************************************************************/

Deploying an ADF application from JDev to JCS weblogic server directly

Hi,

I would like to share the steps to deploy the ADF application from JDEv to JCS Weblogic ( or any standalone weblogic server ).

1. Create an Application Server connection from the JDev by giving Hostname, Port, Credentials , Weblogic Domain from below navigation.

 

a. Select Standalone server as below : 

                                           b. Give connection name :

c. Give server credentials with which you login to weblogic console.

                                         d. Give hostname, ports, domain name

                                          e. Next click on Test. The Test status would be shown as below

f. If all the tests are successfull, click on finish.

2. Select the required deployment profile from below menu :

    Application ==> Deploy

                     

               

The log will show the status of the deployment.
If the application context names are already use in server, the deployment might fail.
In such case, change the J2EE context of the application and redeploy.

3. Verify the deployment from JCS.

Thanks for reading,
Srikanth