You can find them here: IBM Decision Optimization Center - Setting up the application server for SSL connections from Maximo Scheduler. Part 3 (of my instructions, anyway), which I call Configuring Secure Sockets Layer for DOC Server in WebSphere, has been written and posted by my colleague, Belinda Fuller. In Security settings, select the JAAS - J2C authentication alias you created earlier.Īnd you're done (with this section, anyway). Under Resources > JMS, click on Activation specifications Click New.Īccept Default messaging provider and click OK. Here it is Node=ctgCell01, Server=ODMEServer. Under Resources > JMS, click on Queue connection factoriesĬhange scope to the server. In Security settings, under Container-managed authentication alias, select the JAAS - J2C authentication data alias you created earlier. Accept Default messaging provider and click OK. Under Resources > JMS, click on Topic connection factories Change scope to the ODME server. Accept Default messaging provider and click OK.Ĭlick OK, then Save directly to the master configuration. Save directly to the master configuration. For Tune performance parameters, I accept the defaults. In this case, I will use a file store, but as with MIF message stores, our production recommendation is for data stores.Ĭlick Next. Select which type of message store you use. Under Topology, click on Bus Members.įrom the Server drop down, select the DOC server WebSphere application server.Ĭlick Next. On the Buses screen, click on the new OptimizationServerBus. At Confirm create of new bus, click Finish Click on New.Įnter OptimizationServerBus and uncheck Bus security. Set Up Bus, Topic, Connection Factories and Activation SpecificationĮxpand Service Integration on the left, then click on Buses. Click OK, then click Save directly to the master configuration.
#Docear add image password#
Under Related Items, click on JAAS – J2C authentication dataĬlick New… Use ODME (or some other name) for your Alias.įor User ID and Password, enter the main DOC database user and password you created earlier. Click Next, then click Finish.Ĭlick Save directly to the master configuration.Ĭlick on the new OptimizationServerDB data source. None of these entries can be changed now, but they will be later. The URL is of the database created above: that the helper class name is for Oracle 11g. In this case, it is C:\app\oracle\product\12.1.0\dbhome_1\jdbc\lib).Ĭlick Next. In this case, it is Oracle.Ĭhange Provider type to Oracle JDBC Driver.Ĭhange Implementation type to XA Data Source.Īccept defaults for Name and Description and click Next.įor Directory location for "ojdbc6.jar" which is saved as WebSphere variable $, select the location where you copied ojdbc6.jar (\server\configure-scripts - see above). If your database is not DB2, change database type to yours. Change the scope to the server you just created. Go to Resources > JDBC and click on Data sources. In Security > Global Security, check the Enable application security button under Application Security. Add wastim to the Administrative role in Global Security.Įven if you are not yet configuring LDAP (Active Directory or IBM Directory Services, you must enable application security. When completed, note that the odme-data-mgmt-ear.ear and optimserver-processor-ear-圆4_win64.ear files have been updated.Ĭreate a Decision Optimization Center Database in Oracle (Here Called MXODME)Ĭonfigure WebSphere with Basic (Non-Production) SecurityĬreate WebSphere users ( _odmesystem and wastim, password manage for both) and groups ( odmeadmins and odmeusers).Īdd _odmesystem user to the odmeadmins group.
Start command prompt in C:\IBM\ILOG\ODME38\Server\server\configure-scripts. You will need to supply them and rebuild two of the DOC ear files (using one script) with them.Ĭopy (default) C:\app\Administrator\product\11.2.0\dbhome_1\jdbc\lib\ojdbc6.jar to C:\IBM\ILOG\ODME38\Server\server\configure-scripts. Ignore this section if you are using IBM DB2 as your database.ĭOC does not ship with Microsoft SQL Server or Oracle database drivers.
#Docear add image drivers#
Repackage EAR files with Oracle or SQL server JDBC drivers
#Docear add image install#
Install Decision Optimization Server and Create Application Serverĭouble-click on it to install to default (C:\IBM\ILOG (default location is C:\Program Files\IBM\ILOG).ĭownload and install DOC 3.8 Fix Pack 2 from Fix Central to update your installation to 3.8.0.2: Installing and Configuring Decision Optimization Server 3.8 Okay! A long weekend for some folks last weekend, a long weekend for us coming up. Continued from Installing and Configuring Optimizer for Maximo Scheduler 7.6.2 (part 1).
0 kommentar(er)
