1. Development environment jdk1.6+idea15.0.3+git
2. Explain that WebLogic still played when I was in school. Now it was given to the elderly before I changed jobs. At that time, after I cloned the project and configured weblogic, it was found that it could not be accessed. There is no way to install it in the directory D:\Oracle Modify the corresponding configuration in config.xml under \Middleware\user_projects\domains\base_domain\config, as follows, mainly source-path is specified to the corresponding directory
<app-deployment>
<name>test</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>D:\ideaCode\test\target\test</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
Although it will still report an error, it can be accessed normally after restarting. Later, when a newcomer came and installed it for the newcomer, it was found that there were still problems in many places. It's probably sorted out now, and it will continue to improve in the future.
3. Installation steps, select the development mode, when you start weblogi in production mode, you will be asked to enter the username and password. When some ideas start, you enter the username and the password is not prompted to execute, and then an error is reported.
1. Note that the selected jdk and the corresponding version of the project are the same.
2. Create a new data source (general data source), note that JNDI is not the same as your name, and an error will be reported. Select the database type, as shown below (oracle)
3. Service > jdbc > Persistent Storage; Service - Messaging - JMS Server - Select New, Persistent Storage Select just created, the target is AdminServer; Service - Messaging - JMS Module - click New, the target is also AdminServer; click Service - Messaging - JMS Module - Click in the module you just created - select the sub-deployment, the last step here is to select the JMS server you just created, not AdminServer.
4. Create a queue, pay attention to the uniqueness of JNDI, select the sub-deployment just created, and assign a JMS server; create a factory, also pay attention to the uniqueness of JNDI, depending on the name in your project. You can deploy by changing the corresponding weblogic username and password in the project. As mine is:
jndi.jms.jmsConnectionFactory=jndiConnectionFactory jndi.jms.jmsDestination = jndiQueueFourth, here is the configuration description of the idea. The main thing is to create a new Web Application:Exploded in Artifacts to specify the output directory of your project's compilation output. I have modified the default path. For details, you can refer to your own default path. The web:war exploded here is in the form of a non-jar package. In this way, adding the corresponding project under the weblogic service can start and run. Pay attention to the above step: some can run by default, some may not work if the path is changed, set according to the actual situation. At the same time, javax.naming.NameNotFoundException occurred when changing the name of the data source, just delete and reconfigure all weblogic configurations.