web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Security management with the Security Map The following examples illustrate the use of ResourceVaultGen: Example 1: java -Dborland.enterprise.licenseDir=/opt/BES/var -Dserver.instance.root=/opt/BES/var/servers/servername - Dpartition.name=standard com.borland.enterprise.visiconnect.tools.ResourceVaultGen -rolename administrator -username red -password balloon -vaultfile /opt/BES/var/servers/servername/adm/properties/partitions/standard/ resourcevault -vpwd lock This usage generates a resource vault named resourcevault to /opt/BES/var/servers/ servername/adm/properties/partitions/standard, with a role administrator associated with a Password Credential with username red and password balloon. The vault file itself is password protected, using the password lock. For VisiConnect to use this vault, the following properties must be set for it: -Dvisiconnect.resource.security.vaultpwd=lock -Dvisiconnect.resource.security.login=resourcevault Example 2: java -Dborland.enterprise.licenseDir=/opt/BES/var/domains/base/configurations/ /mos//adm/properties/ management_vbroker.properties> -Dserver.instance.root=/opt/BES/var/domains/base/configurations/ /mos//adm/properties/ management_vbroker.properties> -Dpartition.name=petstore com.borland.enterprise.visiconnect.tools.ResourceVaultGen -rolename manager accounts -username mickey daffy -password mouse duck -vpwd goofy This usage generates a default resource vault (named resource_vault) to /opt/BES/var/ servers/servername/adm/properties/partitions/petstore, with a role manager associated with a Password Credential with username mickey and password mouse, and another role accounts associated with a Password Credential with username daffy and password duck. The vault file itself is password protected, using the password goofy. For VisiConnect to use this vault, the following properties must be set for it: -Dvisiconnect.resource.security.vaultpwd=goofy Example 3: java -Dborland.enterprise.licenseDir=/opt/BES/var/servers/servername/adm - Dserver.instance.root=/opt/BES/var/servers/servername -Dpartition.name=standard com.borland.enterprise.visiconnect.tools.ResourceVaultGen -rolename OClone ENolco -username darkstar geraldo -password meteor rivera This usage generates a default resource vault (named resource_vault) to /opt/BES/var/ domains/base/configurations//mos//adm/ properties/management_vbroker.properties>, with a role developer associated with a Password Credential with username darkstar and password meteor, and a role host associated with a Password Credential with username geraldo and password rivera. The vault file itself is not password protected. VisiConnect requires no additional parameters to use this vault. Chapter 27: Using VisiConnect 263
Resource Adapter overview Note ResourceVaultGen cannot be used to write vault information to an existing file containing invalid characters. For example, a file generated by 'touch', or a StarOffice or Word document. ResourceVaultGen can only write vault information to a new file that it itself generates, or a valid existing vault file. Resource Adapter overview According to the Connectors 1.0 specification, you must be able to deploy a Resource Archive (RAR) as part of an Enterprise Archive (EAR). With BES AppServer Edition and VisiConnect you can also deploy a standalone RAR. Once the RAR is deployed, you must do the following: ■ ■ ■ ■ Write code to obtain a connection. Create an Interaction object. Create an Interaction Spec. Create record and/or result set instances. ■ Run the execute command so the record objects become populated. In addition to some introductory conceptual information, this chapter provides steps to help you understand the code you must write. The J2EE Connector Architecture enables Enterprise Information System (EIS) vendors and third-party application developers to develop Resource Adapters that can be deployed to any J2EE 1.3 compliant application server. The Resource Adapter is the main component of the J2EE Connector Architecture (Connectors), providing platform-specific integration between J2EE application components and the EIS. When a Resource Adapter is deployed to the Borland Enterprise Server, it enables the development of robust J2EE applications which can access a wide variety of heterogeneous EISs. Resource Adapters encapsulate the Java components and, if necessary, the native components required to interact with the EIS. Development overview See “Developing the Resource Adapter” on page 268 for more information. Developing a Resource Adapter from scratch requires implementing the necessary interfaces and deployment descriptors, packaging these into a Resource Adapter Archive (RAR), and finally deploying the RAR to the Borland Enterprise Server. The following summarizes the main steps for developing a Resource Adapter: 1 Write Java code for the various interfaces and classes required by the Resource Adapter within the scope of the Connectors 1.0 specification. 2 Specify these classes in the ra.xml standard deployment descriptor file. 3 Compile the Java code for the interfaces and implementation into class files. 4 Package the Java classes into a Java Archive (JAR) file. 5 Create the Resource Adapter-specific deployment descriptors: ■ ■ ra.xml: describes the Resource Adapter-related attributes and deployment properties using the Sun standard DTD. ra-borland.xml: add additional Borland Enterprise Server-specific deployment information. This file contains the parameters for connection factories, connection pools, and security mappings. 6 Create the Resource Adapter Archive (RAR) file (that is, package the Resource Adapter) 264 BES Developer’s Guide
- Page 223 and 224: Defining Connection Pool Properties
- Page 225 and 226: Obtaining JMS Connection Factories
- Page 227 and 228: JMS and Transactions and its accomp
- Page 229 and 230: JMS and Transactions For instance:
- Page 231 and 232: 220 BES Developer’s Guide
- Page 233 and 234: Configuring JMS administered object
- Page 235 and 236: Tibco Creating Clustered JMS Servic
- Page 237 and 238: Sonic serverUrl String localhost:72
- Page 239 and 240: Sonic Creating Clustered JMS Servic
- Page 241 and 242: OpenJMS Even though OpenJMS can be
- Page 243 and 244: OpenJMS Important If you use OpenJM
- Page 245 and 246: OpenJMS openjms.clean_messages_on_s
- Page 247 and 248: OpenJMS Table 24.1 Property Name De
- Page 249 and 250: Other JMS providers The following a
- 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: Security management with the Securi
- 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 and 302: Syntax and usage for appclient Tabl
- Page 303 and 304: Building and running the BES exampl
- 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
Security management with the Security Map<br />
The following examples illustrate the use of ResourceVaultGen:<br />
Example 1:<br />
java -Dborland.enterprise.licenseDir=/opt/BES/var<br />
-D<strong>server</strong>.instance.root=/opt/BES/var/<strong>server</strong>s/<strong>server</strong>name -<br />
Dpartition.name=standard<br />
com.borland.enterprise.visiconnect.tools.ResourceVaultGen -rolename<br />
administrator<br />
-username red -password balloon -vaultfile<br />
/opt/BES/var/<strong>server</strong>s/<strong>server</strong>name/adm/properties/partitions/standard/<br />
resourcevault -vpwd<br />
lock<br />
This usage generates a resource vault named resourcevault to /opt/BES/var/<strong>server</strong>s/<br />
<strong>server</strong>name/adm/properties/partitions/standard, with a role administrator associated<br />
with a Password Credential with username red and password balloon. The vault file<br />
itself is password protected, using the password lock. For VisiConnect to use this vault,<br />
the following properties must be set for it:<br />
-Dvisiconnect.resource.security.vaultpwd=lock<br />
-Dvisiconnect.resource.security.login=resourcevault<br />
Example 2:<br />
java -Dborland.enterprise.licenseDir=/opt/BES/var/domains/base/configurations/<br />
/mos//adm/properties/<br />
management_vbroker.properties><br />
-D<strong>server</strong>.instance.root=/opt/BES/var/domains/base/configurations/<br />
/mos//adm/properties/<br />
management_vbroker.properties><br />
-Dpartition.name=petstore<br />
com.borland.enterprise.visiconnect.tools.ResourceVaultGen<br />
-rolename manager accounts -username mickey daffy<br />
-password mouse duck -vpwd goofy<br />
This usage generates a default resource vault (named resource_vault) to /opt/BES/var/<br />
<strong>server</strong>s/<strong>server</strong>name/adm/properties/partitions/petstore, with a role manager associated<br />
with a Password Credential with username mickey and password mouse, and another<br />
role accounts associated with a Password Credential with username daffy and<br />
password duck. The vault file itself is password protected, using the password goofy.<br />
For VisiConnect to use this vault, the following properties must be set for it:<br />
-Dvisiconnect.resource.security.vaultpwd=goofy<br />
Example 3:<br />
java -Dborland.enterprise.licenseDir=/opt/BES/var/<strong>server</strong>s/<strong>server</strong>name/adm -<br />
D<strong>server</strong>.instance.root=/opt/BES/var/<strong>server</strong>s/<strong>server</strong>name<br />
-Dpartition.name=standard<br />
com.borland.enterprise.visiconnect.tools.ResourceVaultGen<br />
-rolename OClone ENolco -username darkstar geraldo -password meteor rivera<br />
This usage generates a default resource vault (named resource_vault) to /opt/BES/var/<br />
domains/base/configurations//mos//adm/<br />
properties/management_vbroker.properties>, with a role developer associated with a<br />
Password Credential with username darkstar and password meteor, and a role host<br />
associated with a Password Credential with username geraldo and password rivera.<br />
The vault file itself is not password protected. VisiConnect requires no additional<br />
parameters to use this vault.<br />
Chapter 27: Using VisiConnect 263
Change language