WebLogic to JBoss migration - jboss

In my application I have few things which are specific for WebLogic. Is there any tool which can tell me these specification while migrating the application to JBoss?

If you are doing migrations to JBoss you should look at the Windup tool. It will point out all the places in your code that may need attention and give you a score based on how many things you will need to look at. The reports are nice and categorized and they definitely cover your usage of vendor specific code and suggests hints as to what to convert to.
http://windup.jboss.org/
There is also a maven plugin that you can add to your pom and run reports periodically as you go.
Good Luck!

Related

Is Oracle ADF Essential and OEPE Eclipse is discouraged by Oracle?

Based on search in internet web sites, Whenever I tried to find a sample or advanced Task Flow based ADF Application created purely using Oracle Enterprise Pack for Eclipse and Glassfish I only end up with a blog entry 5 year old.
When I try to read any ebook, I end up with JDeveloper and weblogic.
When I try to read the tutorial videos from the official oracle website and oracle official YouTube channels I end up with JDeveloper and weblogic.
Does this means that there will be no support provided by oracle for OEPE and ADF Essentials?
Also the basic tutorial for OEPE is too old. Few basic Unbounded Task flow techniques are not working with OEPE and ADF Essentials.
Unfortunately the state of things is exactly as you described.
It looks like there's some sort of development occasionally going on the OEPE repository with the last change being made on 2016-12-19.
I think that some level of support will probably be provided, and frankly it's pretty much the same level of support that has been available for years - low.
Anyone that needs to make a choice (or has a choice for that matter) should take a long, hard look at the situation as it is.

How to include war in play 2 app?

I have a play 2 Scala application and my customer wants to add a blog solution in a subfolder of this application. I came accross this java blog solution called Apache Roller.
The issue is that I am not able to find it as a jar on maven repo to download it with sbt as we do with other libs because it comes as a war. Is there any way to use a war INSIDE a play 2 app? If yes, where to put it?
I'm on the Apache Roller team and thanks for considering our product. Roller is meant to be a stand-alone web application, just configure your database, drop the WAR into Tomcat and you're set. If desired, Roller offers an LDAP authentication option so users won't need a second set of passwords. [Incidentally, while not yet released, our 5.1-SNAPSHOT is already considerably ahead of our current production 5.0.4 and is expected to be released "soon", so you may wish to consider that option.] Trying to merge WARs will take an exceedingly long time and probably result in a buggy solution, so I would first confirm that your customers will not approve a separate application before trying to integrate blogging software. The Roller User's Mailing List is available if you have any questions.
There is another Java solution, JBake, as it's not a standalone blog server like Roller you may find it more integratable in your web application. (I have not worked with the product so am unsure.) You may end up needing to create the blog entry edit screens, however, prior to feeding the results to JBake.

Grails Multiple Applications as Plugins

I need a bit of clarity regarding whats possible with grails plugins before committing my self to a corner a month or two down the line,
We have two applications built in Grails what share the same model, however we are looking at creating a single application which will control the ACL and add the two Grails applications as plugins.
Now the two applications are very extensive and they have their own controllers, views and routing.
Is it still viable to integrate the two applications as grails plugins or is there another better way of doing it. In the past I have found that following a quick simple guide / tutorial on how to create a grails plugin for instance, might not really explain the other issues I might encounter as I take the two big applications which use plugins of their own and try to convert them to plugins...
Any heads up information would be appreciated.
Everyone's needs are different. I'll simply explain what we've done on a current project and then you can use that to help make your decision.
We have a "common" grails plugin. This plugin contains all of our domains, controllers, layouts, views, css, images, and js that are shared throughout our grails applications. The common plugin has the spring-security-core plugin installed since the security domains are, well, common to all the other applications. However, each application that uses are common plugin still specifies its own security. It uses the domains from common as well as the spring-security-core plugin installed in common, but each application can control its own access points and lock down the URLs that need locked down.
We have an admin application
We have a customer facing application which has both secured and un-secure content.
And we have a couple other internal only applications that use our common plugin.
We've been at this for 6 months and haven't noticed any drawbacks to this approach.

How should I create an automated deployment script?

I need to create some way to get a local WAR file deployed on a Linux server. What I have been doing until now is the following process:
Upload WAR using WinSCP.
SSH into server using PuTTY.
Move/Rename/Delete certain files folders to prepare for WAR explosion.
Explode WAR.
Send email notifying users of restart.
Stop Tomcat server.
Use tail to make sure server stopped correctly.
Change symlink to point to exploded WAR.
Start Tomcat.
Use tail to make sure server started correctly.
Send email notifying users of completed restart.
This stuff is all relatively straightforward. And I'm sure there are a million and one different ways to do it. Id like to hear about some options. My first thought was a Bash script. I have very little experience with scripting in general but thought this would be a good way to learn. I would also be interested in doing this with Ruby/Python or something current like this as I have little to no experience with these languages. I think as a young developer, I should definitely get some sort of scripting language under my belt. I may also be interested in some sort of software solution that could do this stuff for me, although I think scripting would be a better way to go for the sake of ease and customizability (I might have just made that word up).
Some actual questions for those that made it this far. What language would you recommend to automate the process I've listed above? Would this be a good opportunity for me to learn Bash/Ruby/Python/something else, or should I simply take the 10 minutes to do this by hand 2-3 times a week? I would think the answer to this is obviously no. Can I automate these things from my computer, or will I need to setup the scripts to run within the Linux server? Is the email something I can automate or am I better off doing that part myself?
More questions will almost certainly come up as I do this so thanks to all in advance.
UPDATE
I should mention, I am using Maven to build the WAR. So if I can do all of this with Maven please let me know.
This might be too heavy duty for your needs, but have you looked at build automation tools such as CruiseControl or Hudson? You might also want to look at Integrity, which is more lightweight and written in Ruby (instead of Java like the other two I mentioned). These tools can do everything you said you needed in your question plus way, way more.
Edit
Since you want this to be more of a learning exercise in scripting languages than a practical solution, here's an idea for you. Instead of manually uploading your WAR each time to your server, set up a Mercurial repository on your server and create a hook (see here, here, and especially here) that executes a Ruby (or ant, or maven) script each time a changeset is pushed from a remote computer (i.e. your local workstation). You would write the script so it does all the action items in your list above. That way, you will get to learn three new things: a distributed version control paradigm, how to customize said tool, and how to write Ruby scripts to interact with your operating system (since your actions are very filesystem heavy).
The most common in my experience is ant, it's worth learning, it's all pretty simple, and very usefull.
You should definately automate it, and you should aim to have it happen in 1 step.
What are you using to build the WAR file itself? There's some advantage to using the same tool for build and deployment. On several projects I've used Ant to build a Java project and deploy it to the servers.

MOSS Site Definitions, Features and the moving site collections

The general consensus is that devlopment of MOSS publishing sites, should be done using site definitions, Solutions, Features but due to project timescales we had to do all list/site column/content type/master page development using the SharePoint UI and SPD. We then used the contentdeployment wizard to migrate everything from devlopment.
Having done this, the future plan is to possibly, given the budget, change what has been built to use a site definition and features to get in line with best practices.
Has anyone done anything similar or have any tips on how best to plan for this?
Kind Regards
This is somewhat dependent on how large and complex your solution is. I was in the same situation with a project I started to work in. They initially started to do everything in SharePoint Designer. But when I was thrown in to the project, I decided to scrap all those changes, starting from the requirements and build up everything as site definitions/solutions/features in Visual Studio. In this case, it was feasible since the customizations were not too complex.
You can take a look at the SharePoint Solutions Generator, to see if that could help you as well. It can give you at least a good starting point.