Put-Blob-Stream
Description
Stores BLOB data in an object attribute or table column.
Definition
BLOB is an acronym for Binary Large Object. This represents a random large block of data, such as a picture or sound file, that must be stored in a database but cannot be interpreted within the database itself.
Syntax
<ie:webject name="Put-Blob-Stream" type="ACT">
<ie:param name="ATTRIBUTE" data="attribute_with_blob_data"/>
<ie:param name="BLOB_COUNT" data="number_of_BLOBs"/>
<ie:param name="CLASS" data="tablename"/>
<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="local_file_name"/>
<ie:param name="GROUP_OUT" data="group"/>
<ie:param name="INSTANCE" data="instance"/>
<ie:param name="PASSWD" data="dbpassword"/>
<ie:param name="WHERE" data="where_clause"/>
</ie:webject>
Parameters
Required
Select
Optional
ATTRIBUTE
FILENAME
BLOB_COUNT
CLASS
CONNECTION_ATTEMPTS
INSTANCE
CONNECTION_ATTEMPT_INTERVAL
WHERE
DBUSER
GROUP_OUT
PASSWD
ATTRIBUTE
Specifies the attribute or column in the database table in which to store the binary data. This parameter is required.
BLOB_COUNT
Specifies how many BLOBs to deliver to the webject. Specifying a value of 0 results in no BLOBs being delivered. Specifying a value of more than 0 results in up to that specified number of BLOBs being delivered. For example, if this parameter is specified with a value of 5, then no more than five BLOBs are delivered to the webject.
The default behavior for this parameter is that all remaining BLOBs are delivered to the webject. This parameter is optional.
CLASS
Identifies the table name in which to store the binary data. This parameter is required.
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 the fully-qualified path to the file with binary data that is to be stored. For additional information on uploading files, see the section Info*Engine User’s Guide. If a file is not uploaded through the browser, then this parameter must be specified.
GROUP_OUT
Identifies the group returned by the webject. 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.
In order to provide the ability 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 is 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.
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.
WHERE
Specifies search criteria for the database object in which to store the binary data. The value for this parameter is specified as an SQL-formatted where clause. This parameter is required.
Example
The following example documents PutBlobStream.jsp located in the Windchill installation directory:
codebase/infoengine/jsp/examples/JDBCAdapter/examples
In this example, the UploadBlob.jsp file, located in the same examples directory, provides the input form necessary for providing the appropriate parameter values for this example and should be run to execute PutBlobStream.jsp.
The input form contains the following fields:
The JDBC Adapter Instance field should specify the INSTANCE parameter value appropriate to your installation.
The Name field specifies the name of the location where the file containing BLOB data will be located.
The File field specifies the full path of the file that contains the BLOB data.
The MIME Type field specifies the MIME type of the file. If the value for this field is uploaded, it can be fetched from the database for the given name while downloading the BLOB content.
When the form is submitted, PutBlobStream.jsp is called. The data specified on the form provides the parameter values for the webjects.
In the PutBlobStream.jsp file that is shown below, note that values are inserted into the BLOBTEST table for the columns FILENAME and MIMETYPE. These would typically be the values input by the user for the fields File and MIME Type while executing UploadBlob.jsp.
<%@page language="java" session="false"
errorPage="IEError.jsp"%>

<%@taglib uri="http://www.ptc.com/infoengine/taglib/core"
prefix="ie"%>
<html>
<head><title>Put-Blob-Stream Webject</title>
<BASE>
</head>
<body>
<h1>Put-Blob-Stream Webject</h1>
<h3>Stores BLOB data in an object attribute or table
column</h3>

<ie:unit>
<ie:webject name="Do-Sql" type="ACT">
<ie:param name="INSTANCE" data="${FORM[]instance[]}"
default="jdbcAdapter" />
<ie:param name="CLASS" data="BLOBTEST"/>
<ie:param name="SQL" data="INSERT INTO BLOBTEST
VALUES('${FORM[]filename[]}',nulls,'${FORM[]file[]}',${F
ORM[]mimetype[]})"/>
<ie:param name="GROUP_OUT" data="temp" />
</ie:webject>
<ie:failure>
<!-- No failure processing -->
</ie:failure>
</ie:unit>

<ie:webject name="Put-Blob-Stream" type="ACT">
<ie:param name="INSTANCE" data="${FORM[]instance[]}"
default="jdbcAdapter"/>
<ie:param name="ATTRIBUTE" data="FILECONTENT"/>
<ie:param name="CLASS" data="BLOBTEST"/>
<ie:param name="WHERE"
data="NAME='${FORM[]filename[]}'"/>
<ie:param name="FILENAME" data="${FORM[]file[]}"/>
<ie:param name="GROUP_OUT" data="PutBlob"/>
</ie:webject>

<%
String file = request.getParameter ("file");
%>

<b><i><%=file %></i> Uploaded to Database</b>
</body>
</html>
Est-ce que cela a été utile ?