[nikesh mohanlal]

Hi All,

Urgent:Yes

I have changed a logic in a 'XSessionBean.java',located under 'business' folder.I compiled all the java files in the folder and also deployed it.Should I have to do anything.Any 'codegen' command is to be run again,before compiling and deploying?

Please let me know.

Regards,
Nikesh.

[chrisplough]

Nikesh,

I understand what you're referring to, because of the code work I did on OTM (then GC3), but very few organizations outside of Oracle have access to the OTM source code. I believe you'll have to run codegen again at this point, but haven't worked with the build process since the G-Log days and don't know how it's changed since v5.5 GA was released.

For more information, I recommend getting in contact with your development manager or possibly Paul Franz at Oracle -- as they have a better grasp on the OTM build process.

Thanks,
Chris

[bmj_23]

Nikesh, why are you having to modify the OTM source code ? Does the standard OTM functionality not meet your requirements ? Just curious as to why you would be involved in that development exercise...

[satya_m]

Nikesh,

Before the compilation / deployment, you will have to do a codegen. The process is something like this.

1. Codegen on your specific folder --> This will generate the necessary gen files based on the entries in the .gen file in your folder.

2. Compile --- > This will compile all the generated files.

3. deploy ----- > create the necessary jars and copy them into the deployment folder of your app server.

Since you are working on one of the core folders, i suggest you remove all the other entries ( except your session bean's entries) from the .gen file and then do a codegen. This will will only generate the gen files for your session beans and will be faster while compiling and deploying.

Regards,
Satya

[nikesh mohanlal]

Hi All,

Urgent:Yes

Thanks a lot for the information.Actaully, I just need to change the business logic in one of the customised sessionbean(which client are using in 5.0) and needs to be modifed in 5.5,to suit their new requirement.Also I have code gen,compiled n deployed.

It will be great if anyone could let me know what is the procedure to add the created '.jar' file(created in 'weblogic\config\gc3domain\applications folder') to the 'Gc3App.ear' file of the patch creation and also necessary changes to be done(if any) or procedure while installing the patch on the client machine.

Actually I am installing the patch for the first time.

Anticipating for a positive reply.

Thanking and regards,
Nikesh.

[chrisplough]

Nikesh,

Typically the process is to add the class files with their fully-qualified package names (as directories) to the $OTM_HOME/glog/gc3webapp/classes directory. This directory is deleted with each CU applied, which is what you'd want - as the patches would need to be re-tested and possibly modified with each OTM patch.

FYI - this is also how G-Log quick-patches worked.

The problem with modifying the gc3app.ear file is that, you're modifying the OTM application's EAR file, which can cause serious issues if edited incorrectly.

[EDITED]
Strike that -- I had a brain fart. Since you're working with session beans and not just general Java classes, you'll definitely need to add them to the gc3app.ear file in order to get WebLogic to deploy them. In that case, here are some directions for modifying EAR files:

Packaging EJBs for the WebLogic Server Container


--Chris