Deploy the EOS project to weblogic12c and the eos project weblogic12c

Deploy the EOS project to weblogic12c and the eos project weblogic12c

EOS Platform supports standard EAR and can run on weblogic Server. However, EOS Platform 7.2 does not support weblogic12c for the time being. You need to manually modify some configurations before successful deployment.

1. Configure the data source

The default data source of EOS Platform points to the data source whose jndi is defadatasource datasource. When no configuration changes are made to the data source in the project, you need to create a data source whose jndi is defadatasource datasource on weblogic, and specify the target to the current service.

2. Modify the weblogic. xml file

The current weblogic. xml configuration file of EOS Platform 7.2 has some problems, so you need to modify it.

Set the installation directory of EOS Platform 7.2 To EOS_HOME. The modified weblogic. the xml file is in % EOS_HOME % \ ide \ eclipse \ dropins \ PLATFORM_7.2.0.0 \ plugins \ com. primeton. studio. ear. core_7.1.0.0 \ template \ ear \ weblogic \ war \ WEB-INF.

Delete the configuration of JDBCConnectionTimeoutSecs and delete the following content:

<session-param>    <param-name>JDBCConnectionTimeoutSecs</param-name>    <param-value>120</param-value></session-param>

Add http-proxy-caching-of-cookies, encode-session-id-in-query-params, and sharing-enabled configurations as follows:

<session-param>    <param-name>http-proxy-caching-of-cookies</param-name>    <param-value>true</param-value></session-param><session-param>    <param-name>encode-session-id-in-query-params</param-name>    <param-value>false</param-value></session-param><session-param>    <param-name>sharing-enabled</param-name>    <param-value>false</param-value></session-param>

3. Export the EAR package

1. Right-click the project and click Export"

2. on the export page, select "EOS"> "Export EAR" and click "Next"

3. Configure the application name, export directory, and license file in the export EAR wizard.

You can use the default Application name.

You can select a directory by browsing the exported directory.

The license file must be specified in the xml configuration file. Otherwise, an error will be reported during application deployment. My license file is:

<?xml version="1.0" encoding="UTF-8" standalone="no"?><licenses>    <license-group embed="true" format="1.0" productFamily="Primeton Platform" release="7.3">        <license edition="DE" licensee="Primeton Customer" sign="03c9b6a746c565676ecdbf33c88d85d634e8c0686a55034aa681998097250238d6891c8121326709f3dc13da4643027bf5dc3abe6ba8f9b692789c7aeed979bc2bdf2e8bbfd44dcdd356b4c8eff885008db915b0f27d958d53d384dfd638a40a3b05f56be03784f3f5d1ffb02e71779a3278b49c1d40ee3081e501d265ab6372" type="PERM">            <license-element key="cpus" privilege="false" value="unlimited"/>            <license-element key="db" value="unlimited"/>            <license-element key="as" value="unlimited"/>            <license-element key="os" value="unlimited"/>            <license-element key="expiration" value="unlimited"/>            <license-element key="ip" value="mWfR3bjmDIhEL1iKfDoy53jDaNaDGCBXVg=="/>            <license-element key="mac" value="fnZ24/mV095C5gzxDW3p5AE5vurU0yiSzA=="/>            <license-element key="server" value="true">            </license-element>            <license-element key="richweb" value="true">            </license-element>            <license-element key="workflow" value="true">            </license-element>            <license-element key="managermodel" value="single"/>            <license-element key="cluster" value="false"/>            <license-element key="international" value="unlimited"/>            <license-element key="concurrency" value="5"/>            <license-element key="distributed" value="true"/>            <license-element key="scaAssembly" value="true"/>            <license-element key="scaCaller" value="true"/>            <license-element key="wsBinding" value="true"/>            <license-element key="wsCaller" value="true"/>            <license-element dynamic="true" key="ProcessComposer" value="true"/>            <license-element dynamic="true" key="SegmentDeployment" value="false"/>            <license-element dynamic="true" key="BFSProcessForm" value="false"/>            <license-element dynamic="true" key="ProcessStatistics" value="false"/>            <license-element dynamic="true" key="Multitenancy" value="false"/>            <license-element dynamic="true" key="portal" value="false"/>            <license-element dynamic="true" key="portal_portlet" value="false"/>        </license>    </license-group></licenses>

Click "Next ".

4. Select Weblogic as the server type. You do not need to modify the version number.

Click "finish" to start exporting the EAR package. When "build successful" is printed on the console, it indicates that the export is SUCCESSFUL. An ear package exists in the "Export directory" specified in step 1.

4 Deployment

On the weblogic console, install the exported ear package.

Keep clicking "Next" and complete the installation. Then, you can access the default page through http: // localhost: 7001/default/(the default name used by my application name, if not, change the application name ).