web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Building and running the BES examples Building and running the BES examples Note Note Many of the BES examples have their own readme.html files located in: /examples To build a BES example: 1 Open a command line window. 2 Set the current directory to an example directory. The “Hello World” example located at /examples/j2ee/hello is a good place to start. 3 On the command line, enter “ant”. The example should build automatically. The server does not have to be running to build the example. However, deployment and undeployment require that the server be operational. Executing an example requires that the Partition be running. Deploying the example 1 Make sure that a server is running. 2 On the command line, enter ant deploy. This will deploy the example to the Hub, Configuration, and Partition set in the \examples\deploy.properties file. If you wish to deploy to a different combination of Hub/Configuration/Partition, you can either edit the deploy.properties file to change the settings, or use -D options on the command line to override the deploy.properties settings. For example, to use a Hub named “myhub”, use the command: ant -Dhub.name=myhub deploy This will override the default Hub name in deploy.properties with the value myhub. Running the example 1 Make sure that the Partition is running. 2 On the command line, enter ant execute. The precise response depends on the particular example. Undeploying the example 1 Make sure that a server is running. 2 On the command line, enter undeploy. Troubleshooting 1 Make sure that the /bin directory is on your path and precedes the path to any alternative Ant installations. 2 Before calling the ant execute command, make sure that the server and the Partition are running. Chapter 28: BES Ant tasks and running BES examples 291
Building and running the BES examples 3 The \examples\deploy.properties contains default settings for the Hub, Configuration, Partition, and Management Port. These default properties include: ■ ■ ■ ■ ■ ■ hub.name=your_machine_name cfg.name=j2ee partition.name=standard realm.name=ServerRealm server.user.name=admin server.user.pwd=admin where your_machine_name is the machine name designated at installation. You can reset these values as needed or specify them on the Ant command line using the -D option. 292 BES Developer’s Guide
- Page 251 and 252: 240 BES Developer’s Guide
- Page 253 and 254: Creating the Interceptor Class For
- Page 255 and 256: Creating the JAR file Creating the
- Page 257 and 258: Components Components The Connector
- Page 259 and 260: System Contracts Connection Managem
- Page 261 and 262: System Contracts Security Managemen
- Page 263 and 264: Common Client Interface (CCI) Conne
- Page 265 and 266: Packaging and Deployment Figure 26.
- Page 267 and 268: Resource Adapters Resource Adapters
- Page 269 and 270: Connection management Connection ma
- Page 271 and 272: Security management with the Securi
- Page 273 and 274: Security management with the Securi
- Page 275 and 276: Resource Adapter overview Note Reso
- Page 277 and 278: Deployment Descriptors for the Reso
- Page 279 and 280: Developing the Resource Adapter Con
- Page 281 and 282: Deploying the Resource Adapter Pack
- Page 283 and 284: Application development overview 8
- Page 285 and 286: Application development overview //
- Page 287 and 288: Application development overview
- Page 289 and 290: Other Considerations Other Consider
- Page 291 and 292: Other Considerations To illustrate,
- Page 293 and 294: Other Considerations } } { cf = new
- Page 295 and 296: General syntax and usage General sy
- Page 297 and 298: Syntax and usage for iastool Table
- Page 299 and 300: Syntax and usage for java2iiop Exam
- Page 301: Syntax and usage for appclient Tabl
- Page 305 and 306: Using the iastool command-line tool
- Page 307 and 308: Using the iastool command-line tool
- Page 309 and 310: Using the iastool command-line tool
- Page 311 and 312: Using the iastool command-line tool
- Page 313 and 314: Using the iastool command-line tool
- Page 315 and 316: Using the iastool command-line tool
- Page 317 and 318: Using the iastool command-line tool
- Page 319 and 320: Using the iastool command-line tool
- Page 321 and 322: Using the iastool command-line tool
- Page 323 and 324: Using the iastool command-line tool
- Page 325 and 326: Using the iastool command-line tool
- Page 327 and 328: Using the iastool command-line tool
- Page 329 and 330: Using the iastool command-line tool
- Page 331 and 332: Using the iastool command-line tool
- Page 333 and 334: Executing iastool command-line tool
- Page 335 and 336: 324 BES Developer’s Guide
- Page 337 and 338: element ■ ■ ■ element The
- Page 339 and 340: element The Partition statistics ag
- Page 341 and 342: element element The services eleme
- Page 343 and 344: element element The archive elemen
- Page 345 and 346: EJB Container-level Properties Tabl
- Page 347 and 348: EJB Container-level Properties Tabl
- Page 349 and 350: EJB Customization Properties: Deplo
- Page 351 and 352: Complete Index of EJB Properties Co
Building and running the BES examples<br />
Building and running the BES examples<br />
Note<br />
Note<br />
Many of the BES examples have their own readme.html files located in:<br />
/examples<br />
To build a BES example:<br />
1 Open a command line window.<br />
2 Set the current directory to an example directory. The “Hello World” example located<br />
at /examples/j2ee/hello is a good place to start.<br />
3 On the command line, enter “ant”.<br />
The example should build automatically.<br />
The <strong>server</strong> does not have to be running to build the example. However, deployment<br />
and undeployment require that the <strong>server</strong> be operational. Executing an example<br />
requires that the Partition be running.<br />
Deploying the example<br />
1 Make sure that a <strong>server</strong> is running.<br />
2 On the command line, enter ant deploy.<br />
This will deploy the example to the Hub, Configuration, and Partition set in the<br />
\examples\deploy.properties file.<br />
If you wish to deploy to a different combination of Hub/Configuration/Partition, you can<br />
either edit the deploy.properties file to change the settings, or use -D options on the<br />
command line to override the deploy.properties settings.<br />
For example, to use a Hub named “myhub”, use the command:<br />
ant -Dhub.name=myhub deploy<br />
This will override the default Hub name in deploy.properties with the value myhub.<br />
Running the example<br />
1 Make sure that the Partition is running.<br />
2 On the command line, enter ant execute.<br />
The precise response depends on the particular example.<br />
Undeploying the example<br />
1 Make sure that a <strong>server</strong> is running.<br />
2 On the command line, enter undeploy.<br />
Troubleshooting<br />
1 Make sure that the /bin directory is on your path and precedes the<br />
path to any alternative Ant installations.<br />
2 Before calling the ant execute command, make sure that the <strong>server</strong> and the Partition<br />
are running.<br />
Chapter 28: BES Ant tasks and running BES examples 291