Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide

- Previous: Using External JNDI Repositories and Resources
- Next: To edit an external resource

## To create an external resource

1. In the left pane of the Admin Console, open the Application Server instance for the JNDI configuration to be modified.

2. Open JNDI and select External Resources.

   If any external resources have been created already, they are listed in the right pane.

3. To create a new external resource, click New.

4. In the JNDI Name field, enter the name that is to be used to access the resource.

   This name is registered in the JNDI naming service.

5. In the Resource Type field, enter a fully qualified type definition, as shown in the example above.

   The Resource Type definition follows the format, `xxx.xxx`.

6. In the JNDI Lookup field, enter the JNDI value to look up in the external repository.

   For example, when creating an external resource to connect to an external repository, to test a bean class, the JNDI Lookup can look like this: `cn=`testmybean.

7. In the Factory Class field, enter a JNDI factory class external repository, for example, `com.sun.jndi.ldap`.

   This class implements the `javax.naming.spi.ObjectFactory` interface.

8. In the Description field, enter a description for the resource to be created.

   This description is a string value and can include a maximum of 250 characters.

9. In the Additional Properties section, add the property name and value.

10. Mark the External Resource Enabled checkbox, to enable the external resource.

11. Click OK to save the external resource.

    If the external resource is deployed on a cluster or a stand-alone instance, you can manage targets using the Targets tab. The tab appears after the external resource has been created. Set the target by entering the target name and clicking OK.

##### Equivalent asadmin command

`create-jndi-resource`

- Previous: Using External JNDI Repositories and Resources
- Next: To edit an external resource

- © 2010, Oracle Corporation and/or its affiliates