To enable tracing
Before starting WebSphere, you can optionally configure it to enable tracing. Do this in WebSphere by adding
trace to the custom properties on the
Resource Adapters > Micro Focus Cobol Adapter (NoTx) > J2C connection factories > CCIMFCobol_v1.5 < Custom properties page. See your WebSphere documentation for details.
To start WebSphere server
Either start the server from the
Start menu, or run the startup script by entering the following command from the
bin directory of your WebSphere installation:
startserver myServer
To start WebSphere administrative console
- Start WebSphere server and WebSphere Administrative Console.
- In the left pane click
Resources > Resource Adapters
- Click
Install RAR on the page on the right, and follow the instructions on the screen.
When you are asked for the resource adapter file, specify the required
mfcobol*.rar file.
- The new resource adapter is now listed on the right. Click it to display its properties.
- Add a connection factory for the resource adapter. You might need to scroll to Additional Properties at the end and then click
J2C Connection Factories. Then click
New and follow the instructions on the screen to specify:
- CCIMFCobol_v1.5 as the reference name for the connection factory
- eis/MFCobol_v1.5 as the JNDI name for the connection factory
- Confirm that the new resource adapter is now listed on the right.
To deploy an EJB to WebSphere
- If you don't have an
.ear file containing your EJB, package the EJB into an
.ear file now. You will have a. ear if you generated a client and EJB together, and it will be in
myProject\repos\myservice.deploy.
- Start WebSphere server and WebSphere Administrative Console.
- In the Administrative Console, click
ApplicationsInstall New Application on the left
- Follow the instructions on the screen. Most of the information will default to information in the generated deployment descriptors and you do not need to change it. You will however need to specify the following:
- Path to ear file
- Specify the path to your
.ear file
- Deploy EJBs
- Check this
- JNDI name of EJB
- Specify any name you like, but it must match the JNDI name that other components of your application use when they refer your EJB
- Map EJB ref to an enterprise bean
- Specify the same JNDI name that you specified above
To stop WebSphere server
Either stop the server from the
Start menu or:
- Run the stop script by entering the following command from the
bin directory of your WebSphere installation:
stopserver myserver