IntegraciĆ³n con otras aplicaciones > Adaptadores Info*Engine > JNDI Adapter Guide > JNDI Webject Library > Put-Blob-Stream
  
Put-Blob-Stream
Description
Stores Binary Large Object (BLOB) data on a specified database object. BLOBs are used by database administrators to refer to any random large block of bits that needs to be stored in a database, such as a picture or sound file.
Syntax
<ie:webject name="Put-Blob-Stream" type="ACT">
<ie:param name="ATTRIBUTE" data="attribute_name"/>
<ie:param name="CONNECTION_ATTEMPT_INTERVAL" data="interval"/>
<ie:param name="CONNECTION_ATTEMPTS" data="attempts"/>
<ie:param name="DBUSER" data="dbuser_name"/>
<ie:param name="FILENAME" data="filename"/>
<ie:param name="GROUP_OUT" data="group_out"/>
<ie:param name="INSTANCE" data="instance_name"/>
<ie:param name="OBJECT" data="context_name"/>
<ie:param name="PASSWD" data="dbpassword"/>
</ie:webject>
Parameters
Required
Optional
ATTRIBUTE
CONNECTION_ATTEMPTS
INSTANCE
CONNECTION_ATTEMPT_INTERVAL
OBJECT
DBUSER
FILENAME
GROUP_OUT
PASSWD
ATTRIBUTE
Specifies the name of the attribute that will hold the BLOB data. This is a required parameter.
CONNECTION_ATTEMPTS
Defines the maximum number of times to attempt establishing a connection to an adapter before returning an error. The default value is 1. This parameter is optional.
If multiple INSTANCE parameter values are specified, the value of CONNECTION_ATTEMPTS defines the maximum number of times to iterate through the list of adapter instances.
CONNECTION_ATTEMPT_INTERVAL
Defines the amount of time, in seconds, to delay between connection attempts. The default value is 60 seconds. This parameter is optional.
If multiple INSTANCE parameter values are specified, the value of CONNECTION_ATTEMPT_INTERVAL defines the number of seconds to wait between the attempts to iterate through the entire list of adapter instances.
DBUSER
Specifies the name to use when logging in to the data repository. If this parameter is specified in this webject, the webject value takes precedence over any value specified in the credentials mapping settings or in the adapter LDAP entry. If this parameter is not specified here, it must be specified in the credentials mapping settings or in the adapter LDAP entry. For more information about credentials mapping, see the section Credentials Mapping.
FILENAME
Specifies a path to a file on the file system local to the adapter that will be stored in the directory. This parameter is only used if a file has not been uploaded through the web browser. This parameter is optional.
GROUP_OUT
Identifies the name of the object set returned by the action. Currently, GROUP_OUT only returns a status message. This parameter is optional.
INSTANCE
Specifies the name of the adapter that executes the webject. Adapter names are defined when the adapter is configured for use in your Info*Engine environment. This parameter is required.
To connect to other adapters if a specific adapter is not available, this parameter can be multi-valued. Info*Engine attempts to connect to the adapters in the order given. If the first adapter specified in not available, the next adapter listed is tried, and so on, until a connection is made. If a connection cannot be established with any listed adapter, an error is returned.
In conjunction with this parameter, you can include two other parameters, CONNECTION_ATTEMPTS and CONNECTION_ATTEMPT_INTERVAL.
OBJECT
Specifies the context name of the entry. One object may be specified. If more than one is specified, the first will be used and the remainder ignored. This is an optional parameter.
PASSWD
Specifies the password to use when logging in to the data repository. If this parameter is specified in this webject, the webject value takes precedence over any value specified in the credentials mapping settings or in the adapter LDAP entry. If this parameter is not specified here, it must be specified in the credentials mapping settings or in the adapter LDAP entry. For more information about credentials mapping, see the section Credentials Mapping.
Example
The Put-Blob-Stream webject shown in this example instructs Info*Engine to connect to the appropriate adapter instance. Once connected, Info*Engine stores the submitted BLOB data on the object "uid=PPerson,ou=People,o=organization.com" under the attribute "jpegPhoto".
<%@page language="java" session="false"%>
<%@taglib uri="http://www.ptc.com/infoengine/taglib/core"
prefix="ie"%>
<ie:webject name="Put-Blob-Stream" type="ACT">
<ie:param name="INSTANCE" data="jndiAdapter"/>
<ie:param name="OBJECT"
data="uid=PPerson, ou=People, o=organization.com"/>
<ie:param name="ATTRIBUTE" data="jpegPhoto"/>
<ie:param name="GROUP_OUT" data="Create"/>
<ie:param name="FILENAME" data="/usr/file.gif"/>
</ie:webject>