I had an email address that was set up for a group of users in my organization. I wanted forward incoming email that was sent to that address to all of the individuals in the group. I initially logged into cPanel (11.30.6), browsed to the Mail section, and chose Forwarders. I chose Add Forwarder, but the Destination only provides a single-line text box for input. Because of that, I assumed that I could only forward from a single address to a single email address. To accomplish the task, I chose to create a mailing list in cPanel, which did the job, but also required all of the issues of maintaining a mailing list.
Recently I needed to create another group email address and I was determined to find a more elegant approach than using a mailing list. I dove back into cPanel and just began adding forwarders using the same Address to Forward, but changing the Destination for all of the individuals in a group. I sent some test emails to ensure that it worked, and it did. The problem was solved, but it sure seemed like an odd implementation in the cPanel interface. Subsequently I Googled this situation, and came across a blog post stating that in the background cPanel actually creates a single forward entry within the operating system. So it doesn’t look pretty, but it is efficient. Maybe in the next version of cPanel they will provide a multi-line text box for the forwarding destination to make forwarding to multiple email addresses more straightforward.
The information in the Key User Action Log can be imported into SAS data sets and presented in reports. To report the data, follow these steps:
Import the WebReportStudio_KeyActions.log data into a SAS data set. Here are the main steps:
Assign a libref to an XML file that contains log data, and specify the XML engine. In the following example, MyFile.xml is a copy of a Key User Action Log file:
libname myxml xml ’C:\My Files\XML\MyFile.xml’;
Use the SAS data sets procedure to import the XML file into a SAS data set. Here is an example:
proc data sets library=myxml;
This code creates a data set named EVENT in the MYXML library. For more information, see SAS online Help and documentation.
In SAS Information Map Studio, create an information map based on the data set that you created in the preceding step. For the information map, you might want to provide the ability to filter based on the event code (<code> tag), the user name (<user> tag), the report name (<report> tag), or the date (<date> tag). For information about using SAS Information Map Studio, see the product Help.
3 In SAS Web Report Studio, define a report based on the information map that you created in the previous step. You can define the report to be refreshed manually, and then schedule the report to run at regular intervals.
I have had to add Group Content Administrators to my SAS 9.2 Intelligence Platform a few times now, and it didn’t work as smoothly the last time due to my inability to read ALL of the steps and accompanying notes. The process of configuring a Group Content Administrator in the Information Delivery Portal is well documented in the SAS 9.2 Intelligence Platform: Web Application Administration Guide, Third Edition and Angela Hall blogged about the process here, so I should have had enough information to correctly make this happen, right? Well, there is a handy tip that I want to point out. I had some developers who have read/write access to much of the metadata in our system. I added some of these users to be Group Content Creators of the Public group following Steps 1-10 below. Since these developers had inherited Read/Write Metadata permissions from higher up the tree in metadata, they already had implicit WriteMetadata ability. When they attempted to add new portal pages for the Public group, Public not not available to share the page to. Why? Well, after Step 9 there is an important note titled “Important Note” that I somehow missed. The note states to ensure the WriteMetadata permission is explicit. To change this permission from implicit to explicit, an administrator merely needs to click the check the WriteMetadata checkbox one more time (it is already checked, but needs to be checked again). In my defense, I was originally working from the First Edition of the Web Application Administration Guide, where “Important” was not in front of the word note and it was also not in bold text!
A group content administrator is a user who has WriteMetadata permission for the respective group, and the group’s Portal permission tree. A group content administrator can share personal content with the group, and can edit or remove content that has been shared with the group. (The SAS administrator and the SAS Trusted User has WriteMetadata permission for all group permission trees that are defined in metadata.)
Prerequisites: Before you can assign a content administrator for a group, all of the following must be true:
The person who will be a content administrator must have a user identity that is defined in SAS metadata.
This user identity must be a member of the group that the person will administer.
A group permission tree folder must exist in metadata for the group. To verify that a permission tree folder exists, or to create one, see Overview of Permission Tree Folders.
To configure a group content administrator for the Portal Application Permissions tree, follow these steps:
Log on to SAS Management Console as the SAS Administrator (sasadm).
On the Plug-ins tab in SAS Management Console, navigate to Environment Management –> Authorization Manager –> Resource Management –> By Type –> Tree.
Right-click on the permissions tree for the group and select Properties.
In the permissions tree properties dialog box, select the Authorization tab.
Select the Add button to display the Add Users and Groups dialog box.
In the Add Users and Groups dialog box, select and move the group content administrator under Available Identities to Selected Identities. Note that the group content administrator must be a person, and not a group.
Click OK to exit the dialog box.
When you return to the Authorization tab, make sure the appropriate user is selected in the Users and Groups list box.
To modify the permissions for the selected user, in the permissions list row for the WriteMetadata permission, select Grant. Important Note: Ensure that the permission is explicit. The check box for a permission that comes from a directly assigned access control entry (ACE) has no added background color. If the check box for a permission has a background color, to remove the background color and designate the permission as a directly assigned permission, click the check box again.
In the properties dialog box, click OK to save your changes.
The user that was configured as a group content administrator can now log on to the portal and share personal content with that group.
WordPress is a great blogging tool and does an adequate job handling comments, but if you want to provide enhanced discussion capability among your sites users, you must install additional software. The WordPress developers have created bbPress to fill this purpose, and in doing so also added the ability to integrate the two tools on one web site. The key components that are integrated include users, cookies, and the back-end database.
Integration the two products was amazing easy – except for three items needed by bbPress installation. bbPress asked for WordPress "auth" cookie salt (AUTH_KEY), WordPress "secure auth" cookie salt (SECURE_AUTH_KEY), and WordPress "logged in" cookie salt (LOGGED_IN_KEY). The scant documentation insisted that these values were located in my wp-config.php file located in the root of my WordPress installation directory. Since my initial WordPress installation was at version 2.6 or so and has been upgraded many times to version 2.91, these values were never added to my wp-config.php file.
My bbPress installation was halted essentially because these values were required to proceed. Fortunately, I found a tool at wordpress.org that generates these values for you: https://api.wordpress.org/secret-key/1.1/. Just use this link, copy the four lines of keys, and paste them into your wp-config.php. Save your updated wp-config.php file, then go back to your bbPress installation page and paste the keys into the appropriate text boxes and the remaining portion of the installation should go smoothly.
More information about this process can be found here.
We are still running Internet Explorer version 6.0 in our organization. When we open our dashboards that we have built in SAS Information Delivery Portal 1.1, the ActiveX graphs do not display detail information when we mouse over them. The dashboards are running stored processes that output the graphs. The easy solution is to left-click on the graph to activate it. This is easy enough if you have one or two graphs on a page, but some of our dashboards include six or seven graphs, which isn’t hard either, it just leaves you thinking that you shouldn’t have to be doing it. The graphs work perfectly when using Mozilla Firefox, which unfortunately is not our organization standard. The problem is caused by one or more security patches that Microsoft has made available for Internet Explorer. SAS Usage Note 17565 explains this in more detail:
Usage Note 17565: ACTIVEX, JAVA, and JAVAMETA graphs may not be active by default when displayed via Internet Explorer
After application of one or more Microsoft security patches/updates, ACTIVEX, JAVA, and JAVAMETA graphs are no longer active by default when displayed via Internet Explorer. This means that the pop-up options menu will not display when you right-mouse button on the graph.
The Microsoft security patches related to this issue include KB912812 and KB912945.
To activate the graph, left-mouse click on the graph. This will activate the current graph and enable use of the right-mouse button. Once the graph is active, flyover data tips will also now display correctly.
We ran into a problem recently in SAS Web Report Studio 3.1 where our web reports that contained graphs produced java errors while our table-only reports did not. Our platform is SAS Enterprise Business Intelligence Server 9.1.3 Service Pack 4 running Solaris 10 on Sun SPARC Servers. Our web server is Apache Tomcat 4.1.18. The error we received looked like this:
Error messages:There is a problem with the current page. Error Rendering the Report
Root Cause: java.lang.NoClassDefFoundError
I contacted SAS tech support and they had the answer instantly. When running in a headless environment (a server that does not have a display (monitor) attached to it), Tomcat requires the following option in its startup script:
Once I added the option to the Tomcat startup script and restarted Tomcat and SAS Remote Services, no more errors and we were getting our graph output in Web Report Studio again.
I received yet another update from Google yesterday regarding the demise of Google Earth Plus. I appreciate that they are going through the trouble of reiterating my options. I’m going with the free route right now, having installed Google Earth 5.0 but that’s it. Here is how Google summarized my options:
As a valued Google Earth customer, we want you to be the first to know that Google will no longer offer Google Earth Plus. With new enhancements to Google Earth released this week, we believe the needs of many Google Earth Plus customers will be met with Google Earth 5.0, which is freely available to all our customers. For those customers who require additional capabilities and faster speeds, we have a special offer to try Google Earth Pro free of charge for two months. If you like it, you can buy it with a limited-time discount only available to our Google Earth Plus customers.
The latest version of Google Earth lets customers import and track global positioning system (GPS) data. Our Google Earth Plus customers told us GPS tracking is one of the main reasons they choose Google Earth Plus. Now, since you can use this feature for free in Google Earth 5.0, there’s little separation between Plus and the free product. In order to simplify the decision of which version of Google Earth best meets our customers’ needs, we decided it no longer made sense to continue Google Earth Plus.
As a current user of Google Earth Plus, you have several options:
Stay with Google Earth Plus. You can continue using Google Earth Plus for the time being, until either your license expires or until we come out with a new version of Google Earth. Learn more
Use the standard version of Google Earth. You can now import and track GPS data in Google Earth 5.0 without having to pay an annual fee. Learn more
Try Google Earth Pro. Google Earth Pro includes additional features to let you to do even more with Google Earth. For example, print and save images with 3x higher resolution for your documents and presentations, import GIS data, and import up to 2,500 rows of spreadsheet data. As a loyal Google Earth customer, we are offering you a two-month free trial of Google Earth Pro and the opportunity to purchase a one-year subscription for $99 (regular price of $400).
For some reason I must have had too much time on my hands, and I decided to download Google Chrome and give it a try. Previously I used Internet Explorer and Firefox about 50/50, depending on which one I saw first in the quick launch toolbar. Chrome installed easily and instantly, and the first web page I browsed to came up so fast I didn’t think I was finished typing the URL. It renders pages FAST! Others have criticized the lack of customization and features. I find it very refreshing, and I’m sure third party plugins will flood the Internet soon.
I like Chrome so much I have made it my default browser. I have grown to like the most visited pages on the home page, but the recent bookmarks box is useless for me, especially when I just imported bookmarks from Firefox and favorites from Internet Explorer.
I’m not a person that lives in a browser, so I haven’t collected a lot of Firefox plugins or tweaked my browsers. I just want a slick, clean, and lean browser to render my pages fast. Chrome does it!