Asset Manager & Connect-IT User Discussions

Home

Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

State Verified Answer
Replies replies
2
Subscribers subscribers
4
Views views
300
Users 0 members are here
Locked Locked

Related

Options

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Send attachment for request

Afonso Buarque Gusmao over 1 year ago

Hello friends.

Because of the 2mb limitation of smax for opening calls, I'm trying to configure the CIT to do this function.

I can already open a call with CIT with information from the email, but the email attachment is still having difficulty making it work.

Could someone help me with this configuration? I am using CIT 9.90

Tags:

attachments

SMAX

CIT emails

Top Replies

Mark Cullen over 1 year ago +1 verified

Not sure if this is relevant, however, I have recently discovered a 2mb limit with our web services, so we added the following to our TomCat server.xml file ( see bold below )... <!-- <Connector executor…

Verified Answer

+1 Mark Cullen over 1 year ago

Not sure if this is relevant, however, I have recently discovered a 2mb limit with our web services, so we added the following to our TomCat server.xml file (see bold below)...


Cancel
Vote Up +1 Vote Down

Cancel
0 Afonso Buarque Gusmao over 1 year ago in reply to Mark Cullen

I found the problem and it worked perfectly.

support.microfocus.com/.../kmdoc.php
Cancel
Vote Up 0 Vote Down

Cancel

Resources

Learning Services

Partner Programs

Privacy

Compliance

Help

Company

Privacy Policy
Terms of Use
Cookies Preferences

Accessibility
Anti-Slavery Statement

Support
Contact Us

Careers
Code of Business Conduct and Ethics

The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.