Uploading Large Files with ILINX Capture and IIS

From time to time I receive questions about large file uploads with ILINX Capture. ILINX Capture can upload files of any size. The limitation is within Internet Information Services(IIS) and or the amount of memory installed in the web server. This is not only true for ILINX Capture, but and ASP or ASP.Net application.

Depending on the architecture of the ASP or ASP.Net application files being uploaded to the web server are typically streamed into the web server’s memory during the upload process before being written to disk. Depending on the number of user concurrently uploading files and the size of the files being uploaded will determine how much physical memory should be installed in the server. By default IIS has a 200KB size limit for uploading a single file. This can be increased, but not any higher than necessary or you may risk overconsumption of the web server’s memory.

Configuring File Upload Size in IIS 6

1. Open Internet Information Services Manager by clicking the Windows Start Menu and Run. Type inetmgr and click OK.

2. Once IIS Manger opens navigate the tree and right click the server name and click properties.

3. From the server properties window check the Enable Direct Metabase Edit checkbox and click OK.

4. Browse to the C:\windows\system32\inetsrv directory and edit the Metabase.xml file with a text editor such as Notepad.

5. Search for the attribute AspMaxRequestEntityAllowed and edit the value to the size in bytes that you want to allow for a maximum upload size. Save and close the Metabase.xml file.

AspMaxRequestEntityAllowed=”204800″

6. Open the Registry editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSOAP\30\SOAPISAP.

7. Modify the MaxPostSize key. Set the decimal value to the maximum upload size in bytes and click OK.

8. Reboot the web server to ensure the changes have taken effect.

Configuring File Upload Size in IIS 7

1. Open Internet Information Services Manager by clicking the Windows Start Menu and Run. Type inetmgr and click OK.

2. Navigate the tree to the Virtual Directory that you would like to enable large file uploads.

3. In the Features View pane double click ASP.

4. In the ASP setting pane edit the Maximum Requesting Entity and Response Buffering Limit columns. Set this to the maximum file upload size in bytes and click Apply.

 

5. Open the Windows Command Prompt and enter the following command. Change the maxAllowedContentLength to your maximum file upload size in bytes and hit enter to execute the command.

C:\Windows\System32\inetsrv\appcmd set config “Default Web Site” -section:requestFiltering -requestLimits.maxAllowedContentLength:104857600

9. Open the Registry editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSOAP\30\SOAPISAP.

10. Modify the MaxPostSize key. Set the decimal value to the maximum upload size in bytes and click OK.

11. Reboot the web server to ensure the changes have taken effect.

Bryan Wilhelm
Senior Systems Engineer
ImageSource, Inc.

Oracle BPM 11g Install for a Development Environment

Who is finally ready to get off their laurels and start looking at Oracle BPM 11g? I knew I was, the question I had was: where do I start? I figured the best place to start would be to actually install the software. A special thanks to one of our Systems Engineer, Les Harris who helped in getting me going on installing the software. I installed the entire Oracle BPM 11g stack on my laptop and documented the procedure. The following outline is not for a production install, but rather for getting a development environment up and running. A production install would be different and require different install packages as well as a few more steps. This install is strictly for setting up a development environment which is why I used the versions of the software listed below. Sorry I didn’t take screenshots, but I documented everything I did and using these steps I have been able to install multiple environments without issue.

The first thing I had to do was go and download all of the different install packages that comprise the Oracle BPM stack, those are:

• JRockit (JDK R28.1.4)
• Oracle Database (10G Express Edition – Universal)
• Oracle Repository Creation Utility (version 11.1.1.5.0)
• Oracle Web Logic Server (version 10.3.5)
• Oracle SOA Suite (version 11.1.1.5.0)
• Oracle JDeveloper Studio Edition (version 11.1.1.5)

Next I had to unzip all the packages that came zipped up. I recommend 7-zip or pretty much anything else that isn’t the built in Windows utility, that thing is just too slow for these large files.

Now it’s time to start installing.

1. Install JRockit. Since I’ll need to type the path a lot I installed it to C:\Java.
2. Install the database server. It’s a very typical install, I used all the defaults. Be sure to write down the sys account password.

a. After installed launch SQL plus and run the following commands to up the process count:

i.      Connect
ii.      Enter the credentials (username: sys as sydba, password: whatever you specified during your database install)
iii.      alter system reset sessions scope=spfile sid=’*';
iv.      alter system set processes=400 scope=spfile;
v.      shutdown immediate
vi.      startup
vii.      exit

3. Install the RCU utility. This creates all the necessary components in the database.

a. This must be done from the command line. Install as follows:

i.      Cd:\<path to RCU install>rcuhome\bin
ii.      Set RCU_JDBC_TRIM_BLOCKS=TRUE
iii.      Rcu.bat

b. Use all the defaults, pointing it to the database server that was just installed (hostname = localhost, port = 1521, servicename = xe,)

i.      You will see an error message about the database not being supported. Ignore it, this isn’t a production install.When prompted for which components to install select SOA at the top level in order to get all the other necessary requirements.

4. Install Web Logic Server. This is the underlying foundation upon which the application runs.

a. This must be done from the command line. Install as follows:

i.      Cd:\<path to weblogic install>\
ii.      C:\Java\Bin\Java.exe – jar wls1035_generic.jar

b. Select a custom install but choose all the defaults when prompted.

5. Install SOA. This is the meatiest part of the Fusion Middleware stack.

a. This must be done from the command line. Install as follows:

i.      Cd:\ path to RCU install>\Disk1\
ii.      Setup.exe –jreLoc c:\Java

b. Select all the defaults.

6. Create the SOA domain.

a. This must be done from the command line. Install as follows:

i.      Cd:\oracle\middleware\oracle_SOA1\common\bin
ii.      Config.cmd

b. When prompted select the ‘Create domain’ option

i.      Select the BPM Suite for Development and Enterprise Manager option
ii.      Select the Admin Server, Managed Servers, and Deployments options

7. Now it’s time to test the install out (this may take a while, be patient).

a. This must be done from the command line.

i.      Cd:\ oracle\middleware\user_projects\domains\base_domain\
ii.      Startweblogic.cmd

b. When the server is all done with its first start-up the command window should say something like: ‘SOA platform is now running and accepting requests’)
c. You can now close out the WebLogic server (CTRL+C)

8. Install JDeveloper

a. Use all the defaults
b. Once installed, launch JDeveloper Studio from the start menu (it will be under Oracle WebLogic)
c. Go to Help|Check for Updates

i.      Select Next on the Source
ii.      In the search box type in SOA and select the SOA update, then type in BPM and select the BPM update.
iii.      Select Next, then Finish. When it is done, close out of JDeveloper.

9. Now it is time to create your very first BPM 11g project.

a. Launch JDeveloper Studio.

i.      Select File|New
ii.      In the prompt select Applications in the left pane and BPM Application in the right pane.
iii.      Select OK
iv.      Now you’ll be prompted to give your application a name, name it whatever you want or leave it default and select Next.
v.      Now you’ll be prompted to give your Project a name, name it whatever you want or leave it default. Make sure BPM and SOA are selected form the list of available technologies. Select Next.
vi.      Select the Composite with BPMN Process option and select Finish.
vii.      You should now be prompted to create a BPMN process, just select Finish and you can start from there.

You should now be looking at an empty project with a Start and an End event. Here is where the fun begins…

John Linehan

Sr. Systems Engineer
ImageSource Inc.

Installation Hand Off to the Client

As an integrator there are many things we can do as far as making the install a success, but only a very limited amount we can do to guarantee its continuing success. One of the most often seen issues is the handoff of an installation to the client, in particular the maintenance of the database.

I will talk in particular about installations using Microsoft SQL Server. When the database is created it is more often as not left to us as the integrators to create the database (sometimes even the installation of the MSQL Server instance as well). We will choose the path for the database file groups, and allow the defaults for everything else. For operational purposes of our software this will work, but there should be changes made and additional procedures put in place by the clients DBA to guarantee continued optimal performance of the newly implemented system.

When visiting these systems at a later date we find that log files have not been truncated, leaving to question whether any backups have been done at all. Log files are the record of changes which have taken place since the last log truncation; this allows that the database can be restored to a point in time since the last full backup to reverse an adverse action or system failure. These log files are often much larger than the data files. In a maintained system a DBA would have established a normal backup strategy which would have backed up the log file at different intervals through the day and truncated the log file after a full database backup.

The other is often finding the file growth setting for the database to be at a preset auto growth amount. These by default are either 10 mb or 10%. When the database was first established an estimate was made to come up with a number which would be used for the initial file size for the database and log files. For databases which have a need for growth these presets can be very inefficient, as among other things they are likely to do their growth during business hours. Take a 200gb database which started at 150 gb, if it grows by only 10 mb every time it needs to grow there will be a large number of inefficient file space allocations to have made up the 50gb of space. If told to grow by 10 percent, then we will have seen 15 gb file allocations taking place but during business hours which can have an impact upon users. One which the maintenance has been taken up by the DBA will have been monitored and auto growth will have been turned off. The DBA would have scheduled the data file growth based upon measurements taken of the databases past growth rate, and most likely the new space allocation will have taken place in off business hours.

There may be a myriad of reasons why this handoff has failed including the lack of a DBA in the organization. I do not purport to know what the answer is, only that when a follow on visit to a client is made, that inspection of the database for these settings would be worthwhile so that they can be brought the clients attention and hopefully then engagement by the IT department for the maintenance needing to take place.

 

Jeff Doyle
Senior System Architect
ImageSource, Inc.