There are issues with the application's development, including small glitches and errors. We're in the process of continuously fixing to address these issues, and once resolved, the application will be ready. I've worked on this internal system application, and I'll give you an example of our specific challenge. There was an issue involving a complex query where data was stored and retrieved from the database. 

The application also had a reporting component that wasn't generating reports or collecting the required information for Excel reports. To address this, I made changes to the query. I focused on the data format issue encountered in the implementation class. However, when implementing these changes under a specific thread, the application server showed an exception. I also made adjustments to resolve the issue.

The product's high price is an area of concern where improvements are required.

Integration with Oracle products is well-supported. The same should be provided for other products that are used in most organizations, like PeopleSoft, CA, etc. 

I find this is pretty mature product. Mature in the sense that I’m getting the same Java in the cloud that I get with a locally installed version. So far, the only issue I have is with the storage cloud. The user needs to use the external REST API to set up the storage cloud servers. A developer that knows the REST API can easily do this. Other options, like the Java Cloud Service or Database Cloud Service, do have a UI option from the web application itself, where you can go and create an instance.

We've had some issues when Oracle released updates and patched the JCS environments without our knowledge. The proposition of Oracle JCS is that Oracle is going to give you the infrastructure, manage it, patch it, and upgrade it themselves. You just deploy your solutions on top of it and execute. Some of the automated platform patches broke our existing functionality and we were not notified about it. 

This means you're at Oracle's mercy, but again, we improved that process because Java Cloud Services as a service is maturing itself, and that's one of the problems that we had. 

There were a lot of configurations that we had to do to extend JCS with the FMW platform that we used, which was very manual and often error prone. We would like to have Oracle think about how can all the ongoing configurations that are applied on JCS be automated, or whether Oracle has a way to make sure the configuration drift is captured and there is a way to revert the environment back to its original state once something goes wrong.

Another area of improvement is to provide support for all critical components of the FMW platform such as WebLogic, SOA Suite and BPM Suite. When we started using JCS,  WebLogic 12.2.1 and BPM Suite 12.2.1 was supported on it but not SOA Suite 12.2.1. This makes adoption and usage of JCS harder in enterprises because when an enterprise wants to go to JCS, they want to either deploy one or all solutions particularly when they are integrated together. 

For instance, you will hardly see an enterprise which has BPM and not SOA, or SOA and not WebLogic. How do I move just my BPM on JCS and not SOA? That's what has been so difficult about it.

Integration with other Oracle/non-Oracle products.

I think there should be improvement with the speed and it should offer a more diverse selection of the suites that I can use.

It has been built on Java technology but requires more integration with other APIs and CI tools.

I would like to see more monitors for standard edition

Since most of our applications are Oracle ADF based on WebCenter, supporting a complete lift and shift of such complex Java EE would help us become completely cloud-based for our web channels.

Customer service could be improved.

The product is satisfactory but we need more training on managing the machine itself. For example, how do we add more storage, how do we extend a specific portion? I would like to see videos illustrating some of the technical tasks that we often need to do.

It needs to have the ability to create a service with the same name as another one when the initial creation failed as sometimes it's necessary to have a service with exact name. As far as I know, this problem is indicated as a "known issue" by Oracle, but this point is really needed sometimes.

Most of the features provided are well designed and implemented. I'd like to learn more about WebLogic Server for solutions to help identify and resolve stuck threads.

I feel like everything's running perfectly, so I don't have any improvements at the moment. But in terms of future features I would like it to be more helpful on the social media and marketing side.