Re: Websphere Portal 8 Import Wcm Library
Teodosio Shepperd
I am dealing with a vulnerable jar(jstl-1.2.jar). My application is very old and runs on IBM websphere 5.1. Since jstl-1.2 does not have any non-vulnerable version available, I want to add this jar in the shared library of the websphere.My doubt is, if I remove the har from application package and add it to websphere shared library, will the application work?
You can export the contents of a web content library to disk by creating a copy of the web content library. By working with an exported copy, you can import the copied library into the same web content server multiple times, resulting in a new library after each import without affecting previous copies. This is a quick way of creating new libraries that are fully populated with web content that you can easily adapt for other purposes.
Follow these steps to export or import a copy of a web content library. The server that the data is being exported from is called the source server, and the server that the data is being imported into is called the target server.
The directory path and file name that is used to store the exported library. The export process creates a compressed archive file, so it is recommended that you specify a file extension such as .zip. If you are exporting and importing across a network, this location can be a network drive accessible by both the source and target servers.
The directory path and file name containing the library to be imported. If you are exporting and importing across a network, the value for this property can be the same file path that was used for the LibraryPath property during the export process. Otherwise, you must copy the exported data to a location accessible by the target server before attempting to import.
The name to use for the web content library copy that you are importing. If you are importing multiple libraries, separate each new library name by a semi-colon (;). For example, LibraryName="Web Content Copy;Samples Copy".
This property enables the import process to correctly set the new library names for the imported copies, in conjunction with the LibraryName property specified for the import process. The LibraryExportName property is only required if you are importing multiple libraries at one time.
The title to use for the web content library copy that you are importing. If you are importing multiple libraries, separate each new library title by a semi-colon (;). For example, LibraryTitle="Web Content Title;Samples Title".
The description to use for the web content library copy that you are importing. If you are importing multiple libraries, separate each new library description by a semi-colon (;). For example, LibraryDescription="Copy of Web Content library;Copy of Samples library".
This property specifies the name of the text provider to use to locate the translated title of the library that you are importing. If you are importing multiple libraries with different text providers, separate each provider name by a semi-colon (;). For example, LibraryNameTextProvider=provider1;provider2.
This property specifies the key within the associated text provider that identifies the translated title of the library that you are importing. If you are importing multiple libraries with different translated titles, separate each key by a semi-colon (;). For example, LibraryNameTextProviderKey=key1;key2.
Verify that the imported libraries have been imported by reviewing the list of libraries that are listed in the web content libraries section of the administration portlet on the target server. If any errors occurred, check the portal logs on the target server for extended diagnostic information.
Since this library is just another jython file, you can import it into your own scripts, and call the methods directly. Here's an example for starting an application server, taken from the wsadminlib-blog:
Prefix by which to access the imported custom CFML tags JSP tags. If you import a CFML custom tag directory and specify an empty value, "", for this attribute, you can call the custom tags without using a prefix. Specify and use a prefix for a JSP tag library.
You can import multiple tag libraries using one prefix. If there are duplicate tags in a library, the first one takes precedence.JSP tags have fixed attributes; however, if the tag supports runtime attribute expressions, most tag libraries support the use of the syntax #expressions#. To reference a JSP tag in a CFML page, use the syntax . Set the prefix value in the prefix attribute.
The cfimport tag must be on the page that uses the imported tags. For example, if you use a cfimport tag on a page that you include with the cfinclude call, you cannot use the imported tags on the page that has the cfinclude tag. Similarly, if you have a cfimport tag on your Application.cfm page, the imported tags are available on the Application.cfm page only, not on the other pages in the application. ColdFusion does not throw an error in these situations, but the imported tags do not run. You cannot use the cfimport tag to suppress output from a tag library.
For more information, see the Java Server Page 1.1 specification.