my system is ASUS X550LA with win8.1 on core i5 with VT and 4GB of RAM. I upgraded to the PRO version for hyper-v but it did not work. the .vhd Microsoft gave only works on hyper-v for Windows 2008.
- download BizTalk developer training kit
http://www.microsoft.com/en-us/download/details.aspx?id=14865
- move all of them to C:\Microsoft BizTalk Server 2010 Training\
- run BizTalkDevCourseVM.part01.exe to create the C:\Microsoft BizTalk Server 2010 Training\VM\common\BizTalk2010Demo.vhd
- download the winimage. I downloaded the 64bit version for my windows 8.1
http://www.winimage.com/download.htm
- use winimage to convert BizTalk2010Demo.vhd to BizTalk2010Demo.vmdk. This conversion take a while. Once complete, you can uninstall winimage.
- download and install vmware workstation
- create a new VM with BizTalk2010Demo.vmdk as the harddisk.
- make sure you select IDE instead of default scsi. scsi will give the BSOD (bluescreen of death)
- activate the windows 2008R2 because the trial version expired a long time ago. You need a valid Win2008r2 Key for this.
Saturday, April 18, 2015
Thursday, June 26, 2014
create a Separate keystore - 12.51
while performing the parallel migration from r6sp5 to r12.51 I gave the steps to separate a key-store in the r6sp5 environment. once that step is complete and migration of all app servers to the new environment are done - it is best to create a separate key-store for the r12.51 environment (reason being clients are already asking for another upgrade to .52).
with this in mind, below are the steps to create a separate key-store for r12.51. CA documentation is pretty straight forward in this case which is an exception.
with this in mind, below are the steps to create a separate key-store for r12.51. CA documentation is pretty straight forward in this case which is an exception.
- create a directory server (I used DSEE11g) on available port (30389/30636)
- create new suffix under it 'DC=Netegrity,DC=DOMAIN,DC=net' - in step 5 make sure to initialize top entry for the suffix while creating it. this is an important step.
- command to register the new key-store in the policy server : smldapsetup reg -hostX.X.X.X -p30389 -d"cn=directory manager" -wPASSWORD -r"DC=Netegrity" -k1
- verify in the console and correct if any mistakes
- command to generate the schema for keystore : smldapsetup ldgen -fJune2014_newkeystoreschema.txt -k1
- command to update the schema into keystore : smldapsetup ldmod -fJune2014_newkeystoreschema.txt -k1
- in policy server management console - keys tab - enable agent key generation
- start policy server and watch the logs.
Friday, September 27, 2013
IBM Heap Analyser - Java.lang.OutofMemoryError: Java heap space
IBM Heap Analyser -
I started getting "Java.lang.OutofMemoryError: Java heap space" when trying to read a heapdump file using the heap analyser. used the below on a windows 2008r2 server where I had 64bit java installed. specified the initial and max heapsize and it started working.
D:\Program Files\Java\jdk1.7.0_25\bin>java -Xms2g -Xmx6g -jar d:\temp\ha450.jar
I started getting "Java.lang.OutofMemoryError: Java heap space" when trying to read a heapdump file using the heap analyser. used the below on a windows 2008r2 server where I had 64bit java installed. specified the initial and max heapsize and it started working.
D:\Program Files\Java\jdk1.7.0_25\bin>java -Xms2g -Xmx6g -jar d:\temp\ha450.jar
Tuesday, February 12, 2013
Siteminder r6 - separate keystore from policy store
We have r6sp5 siteminder environment which we are looking to parallel upgrade to r12sp3 soon. below are some detailed steps how to separate the KeyStore from the policy store in a r6sp5 environment. The siteminder documentation is very vague in its description of how to do this.
***************
1.Take the backup of existing keys for the policy server:
smobjexport.exe -dsiteminder -wP@55word -okey.smdif -x -v
2. Create a new LDAP Key Store instance in your directory server.
3. Now open the Siteminder smconsole and go to the data tab-> Select Key Store, then uncheck the option-Use Policy Store Database. And fill the details for your newly created Keystore (like IP: Port, username, password and root DN) in this Keystore tab. After this click OK.
4. Open Command Prompt, go to/bin and perform the following command :-
smldapsetup ldgen -fnewkeystoreschema.txt -v -k1
This will create a schema file for your new keystore instance
6. Also at the same location run the following command :-
smldapsetup ldmod -fnewkeystoreschema.txt -v -k1
This will create the Schema in your New LDAP keystore from this schema file
7. run
smobjimport.exe -dsiteminder -wP@55word -ikey.smdif -k -v
8. Now we are done with the creation of new keystore. Start the policy server and check the logs.
*****************
***************
1.Take the backup of existing keys for the policy server:
smobjexport.exe -dsiteminder -wP@55word -okey.smdif -x -v
2. Create a new LDAP Key Store instance in your directory server.
3. Now open the Siteminder smconsole and go to the data tab-> Select Key Store, then uncheck the option-Use Policy Store Database. And fill the details for your newly created Keystore (like IP: Port, username, password and root DN) in this Keystore tab. After this click OK.
4. Open Command Prompt, go to
smldapsetup ldgen -fnewkeystoreschema.txt -v -k1
This will create a schema file for your new keystore instance
6. Also at the same location run the following command :-
smldapsetup ldmod -fnewkeystoreschema.txt -v -k1
This will create the Schema in your New LDAP keystore from this schema file
7. run
smobjimport.exe -dsiteminder -wP@55word -ikey.smdif -k -v
8. Now we are done with the creation of new keystore. Start the policy server and check the logs.
*****************
Subscribe to:
Posts (Atom)