Wednesday, August 24, 2011

How to change date format as your requirement under work Item object

In work Item tab,In displayed table date column have by default english  format,If you want to change in yyyy/MM/dd format.I have posted  the code below----

<Field name='workItems[$(name)].createDate'>
                 <Display class='Label'>
                  <Property name='value'>
                     
       <invoke name='format'>
                    <new class='java.text.SimpleDateFormat'>
                        <s>yyyy/MM/dd</s>
                    </new>
                  <invoke name='getTime'>
                      <ref>workItems[$(name)].createDate</ref>
                    </invoke>
                </invoke>
   
                  </Property>
                </Display>
              </Field>
Posted by Identity Solutions at 2:18 AM 0 comments
Labels:

Tuesday, August 9, 2011

Installing Alfresco on Tomcat

Alfresco Provided the two types of setup
1.Enterprise
2.Community

Community installer,you can easily install just click on next tabs but in case of Enterprise need to configure manaully.

As I am learning this new technology ,today I am have installed the Enterprise Alfresco in my machine.
If you want I will send you doc file with screen shot.

Here is link from which I have taken help
Posted by Identity Solutions at 11:53 PM 0 comments
Labels:

Friday, August 5, 2011

Configuring IdM to redirect to Access Manager logout

QUESTION:
I have configured IdM for SSO with Access Manager. How do I tell IdM to destroy the 
Access Manager Token during logout?
ANSWER:
You need to modify the IdM logout implementation so that it redirects to Access 
Manager logout. For a standard IdM install, this involves three files:

- logout.html (located in IdM base dir)
- userLogout.jsp (end-user interface logout, user/userLogout.jsp)
- logout.jsp (admin interface logout, logout.jsp)

For logout.html, add the following (after <body> tag):

  <!-- logout of AM -->
  <script>
    document.location.href="http://my-appserver-instance:80/amserver/UI/Logout";
  </script>

For userLogout.jsp and logout.jsp, change the redirect so that it goes to your 
Access Manager logout:

response.sendRedirect(p.encodeRedirectURL("http://my-appserver instance:80/amserver/UI/Logout"));
Posted by Identity Solutions at 5:14 AM 0 comments
Labels:

Thursday, August 4, 2011

Enable Gateway Tracing

QUESTION:
How would I enable gateway tracing?
ANSWER:
- Point your browser to debug/Gateway.jsp 
- Click 'Get Trace Parameters' to confirm your current trace settings. Click
  Back when you are done 
- In the File field, provide a complete path to the gateway log file. If it does
  not already exist, it will be created. 
- Set the log level to 4 for maximum tracing 
- Set the File Max Size to any size that makes sense for your environment. 1024
  is usually sufficient. 
- Click on 'Set Trace Parameters'. 

To retrieve the file remotely, click 'Get Trace File'.

There are also flags that can be set either on the command line or in the registry 
for the gateway. Type "gateway -h" for more details.
Posted by Identity Solutions at 12:06 AM 0 comments
Labels:

Tuesday, August 2, 2011

Detail steps for Sun Directory server patch 4 upgrade to patch 6 upgradation

Previous Month I have upgraded the Directory Server for one my client.
Below I posting the steps which I used during the Upgardations.

Pre Implementation steps
===================
1)Login to server through putty
2) In you home directory(/home/ldap) create a folder as below,
sudo mkdir DSUpgrade
3)change the permission of the folder as below,
sudo chmod 777 DSUpgrade
4) using Winscp copy the installer binary file(117665-05.zip) from D:\Pankaj\Softwares\Directory Server - to Solaris under
/home/ldap/DSUpgrade folder
5) change your current directory to DSUpgrade as below
cd DSUpgrade
6) unzip the file(117665-05.zip) as below
unzip 117665-05.zip
7) A folder will be created by named 117665-05
8) change your current directory to 117665-05 as below
cd 117665-05
9) run ls -l and confirm there is an file named patchzip-directory-5.2_Patch_6-us.sparc-sun-solaris2.8.tar.gz
10) extract the file as below
gunzip patchzip-directory-5.2_Patch_6-us.sparc-sun-solaris2.8.tar.gz
11) run tar -xvf patchzip-directory-5.2_Patch_6-us.sparc-sun-solaris2.8.tar
12) run ls and confirm the below files exist
 $ ls
bin                                                         nsclient.zip
directory-5.2_Patch_6-us.sparc-sun-solaris2.8.tar.gz        nsjre.zip
idsktune                                                    nsperl553.zip
install.sh                                                  patchinfo
LEGAL_LICENSE.TXT                                           patchzip-directory-5.2_Patch_6-us.sparc-sun-solaris2.8.tar
lib                                                         README.117665-05
nsadmin.zip                                                 tzupdater
nsadminclient.zip                                           unzip
nsbase.zip                                                  upgrade.pl
Preparation Steps
==============
1) Take a ldif backup by running the below command,
sudo /var/mps/slapd-isntacename/db2ldif -n userRoot
2) take a backup of dse.ldif file
sudo cp /var/mps/slapd-instancename/config/dse.ldif /home/ldap/
3) record the DS version by running th below commands,
cd /var/mps/bin/slapd/server
sudo ./ns-slapd -D /var/mps/slapd-instancename/ -V
4) record the prstat -a output before upgrade
5) Record idsktune output as below,
cd /home/ldap/DSUpgrade/117665-05
sudo ./idsktune > /home/ldap/idsktune.out
Implementation Step
================
Ensure no Directory Server console is opened before running the below command,
1) run the below command,
sudo ./install.sh /var/mps/ admin password
Record the output.
Post Implementation steps
====================
1)Perform a complete health check of the server(including a ldapsearch)
2)Inform other team which are using this ladap for testing.


I hope this article very useful for all.Please give me comment for this.
Posted by Identity Solutions at 11:44 PM 2 comments
Labels:

Solutions whichprovided by identity management.

Management of identities
Access control
Directory services
Other categories
Standards initiatives
Posted by Identity Solutions at 4:46 AM 0 comments
Labels:

Flat file active sync logfile rotation

QUESTION:
Is it possible to configure timing of log rotation of Flat File ActiveSync. I want 
to get the adapter to rotate log files at specific time (e.g. 05:00:00) each day, 
but there seems no regularity in rotation.
ANSWER:
We cannot currently rotate at a specific time.

The logging rotation is an efficient lazy algorithm, performing the size/time 
rotation checks only when a log request occurs. The only way to ensure precise 
rotation times would be to have steady traffic to the logs. Increasing your poll to 
be more frequent would certainly help to keep the log rotation more regular.

The time-based log rotation is based on a special hidden timestamp file maintained 
in the directory of the log files.

The name of the file is:
     .tstamp_<RESOURCENAME>_@@@_<TSTAMP>

where
     RESOURCENAME is the name of the resource
     TSTAMP is the number of milliseconds since Jan 1, 1970 0:00 GMT.

The TSTAMP part of the filename reflects the time at which the logs were last 
rotated.
Posted by Identity Solutions at 1:29 AM 0 comments
Labels:

Monday, August 1, 2011

Cancel active sync processing if incoming data is deemed bad or insufficient

QUESTION:
How would I cancel active sync processing if the incoming data is insufficient?

If canceled, would that cause the workflow to not execute?

How could I create an audit log entry that could be seen in some IdM reports for 
this particular senario?
ANSWER:
To cancel active sync processing, one would set the IAPI.cancel variable to true 
within in the active sync form.

If IAPI.cancel is set to true, then no workflow will be launched as a result.

If you wish to have some type of audit logging, then you would not want to set 
IAPI.cancel to true, but instead let the workflow handle the audit task.

One approach is to use form logic in your active sync form for data validation. You 
can then set a view attribute based on the data validation which will trigger the 
downstream workflow to audit the bad record and then end (i.e., bypassing actual 
provisioning). Because the event is audited you can use IdM reporting to send 
nightly/weekly reports of the invalid feed data.

For example...in your active sync input form you have:

      <Field name='processInputs.IgnoreRecord'>
        <Expansion>
          <cond>
       <isnull>
         <ref>activeSync.givenName</ref>
       </isnull>
       <s>Record rejected due to invalid feed data : givenName was null</s>
            <null/>
     </cond>
        </Expansion>
      </Field>

You then modify the workflow to do something like this....

      <Activity name='start'>
        <Transition to='Audit Rejected Feed Record'>
     <ref>IgnoreRecord</ref>
        </Transition>
   <Transition to='Approve'/>
      </Activity>

          ....

      <Activity name='Audit Rejected Feed Record'>
        <Action application='com.waveset.session.WorkflowServices'>
          <Argument name='op' value='audit'/>
          <Argument name='type' value='User'/>
          <Argument name='action' value='Create'/>
          <Argument name='accountId' value='$(user.activeSync.accountId)'/>
          <Argument name='status' value='failure'/>
          <Argument name='subject' value='$(WF_CASE_OWNER)'/>
          <Argument name='error' value='$(IgnoreRecord)'/>
          <Argument name='resource' value='$(user.activeSync.resourceName)'/>
        </Action>
        <Transition to='end'/>
      </Activity>
Posted by Identity Solutions at 2:22 AM 0 comments
Labels:
Subscribe to: Posts (Atom)